Rclone is a widely used open source CLI tool written in Go which allows for transferring, storing and syncing content between local file systems and cloud storage backends such as S3 buckets. It is oftentimes referred to as the Rsync for Cloud Storage. I have used Rclone on numerous occasions in conjunction with a wide variety of cloud storage solutions including Google Cloud Storage, Ceph and multiple S3-compatible services. Since I have found setting up Rclone to work properly with Linode’s Object Storage service a bit tricky, I have decided to share the setup instructions.
Category: DevOps
Storing backend application configuration values in environment variables is a common practice that makes most DevOps works easier. In a recent project, my task was to setup a CI/CD pipeline for a Java Spring application. In order to do that, I had to configure the application so that it would read the database connection values from env variables in both staging and production environment while falling back to default values if the desired variables were not provided.
When setting up CI/CD pipeline in one of my projects I decided to give Azure App Service a try. I was using GitHub Actions for building and testing the app written in ASP.NET Core. While there were a plenty of resources about how to configure actions with a basic project structure, I couldn’t find any YAML that could be used when you have your project split into two for testing (as required by .NET) and hence decided to share.
Recently I had a task to install Nextcloud with OnlyOffice integration on a client’s server. In order to save some time, I’ve decided to use the official repository that allows for OnlyOffice and Nextcloud installation via Docker compose. It’s container structure looks like this:
app-server
which is basically a Nextcloud instanceonlyoffice-document-server
self-explanatorynginx-server
which acts as a reverse proxy for Nextcloud and OnlyOffice
Everything was fine up until the point in when I decided to edit the nginx config file (/docker-onlyoffice-nextcloud/nginx.conf) in order to enforce SSL usage by redirecting HTTP to HTTPS. After restarting the nginx server container, OnlyOffice would no longer load the documents inside Nextcloud’s UI (“Download failed.” was all the info it gave me).