desktop VS watchtower

Also forget about the automatic upload feature in the Android client, I switched to FolderSync for a reliable experience.

I've managed to get OnlyOffice working, Collabora Office previously broke for some reason. However latest upgrade also broke OnlyOffice. The solution for this is to put the secret and authorization headers into config.php in addition to the OnlyOffice plugin settings. [2] No idea why, but that is a thing.

My Nextcloud runs as a normal PHP application and I haven't had any issues with upgrading yet. Going from, I think, version 23 on Debian 11 to 27.1 now on a different machine running Debian 12 since I started using it.

Maybe I should find something more focused on file syncing, but the all-in-one approach of Nextcloud and its various plugins makes trying some new services very easy.

[1] https://github.com/nextcloud/desktop/issues/5031

[2] https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues/60...

While reading this article, they were suggesting to modify the maxChunkSize in the Desktop client app configs, problem is, I've had this problem also on mobile... so that's not the solution I need.

I've added a link to this at https://github.com/nextcloud/desktop/issues/3912 which appears to be the right ID tracking it, and from what others have said this appears to be isolated to using the Virtual Files feature.

I know about this thread. If you look at the pull request that closes this, you see that this implements support in the clients for manual locking using the file_lock app. File locking like in a remote file system is probably not possible using a sync client (see this comment for example).

Nextcloud has had too many longstanding bugs like the one that mangles metadata, breaks sync, and requires server side intervention to fix [1]. I don’t trust them to do normal sync anymore. There’s no way I’d take the risk of letting them encrypt my data.

They need to slow down on features before tech debt ruins their product (if it hasn’t already).

1. https://github.com/nextcloud/desktop/issues/4378

Very regularly I get conflicts, right after editing a file. I found others having issues such as this Github issue and I tried some of the suggestions but so far none of them helped.

Related: https://github.com/containrrr/watchtower

> if you're using the docker image, upgrades are a breeze. Just bump the tag on the image, redeploy, and you're done.

Or you could just run Watchtower beside it and it will automatically update your docker containers. https://github.com/containrrr/watchtower If you are OK with automated updates.

So i primarily use containers on my local machine walled off from the internet, so it's not a big concern for me. Watchtower [1] is popular among home server users too which automatically updates containers to the latest image.

For production uses I think companies generally build their own containers. They would have a common base linux container and build the other containers based off that with a typical CI/CD pipeline. So if glibc is patched, it's probably patched in the base container and the others are then rebuilt. You don't have to patch each container individually, just the base. Production also minimizes the scope of containers with nothing installed except what's necessary so they have few dependencies.

[1] https://github.com/containrrr/watchtower

You can use Watchtower (https://containrrr.dev/watchtower/) that solves problem of manual pulling on VPS.

I checked https://containrrr.dev/watchtower/ and Arguments, but I don't understand where to attach that using portainer.

Again, there are options to automate some of the burden here by using tools such as Watchtower.

Have you ever deployed a Docker app on a server, but everytime you push a new version of your image to a Docker registry you need to manually restart your app? If you want to automate this restarting, this blog post is for you! I am now going to show you how you can do this with literally 1 simple command using Watchtower!