Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
My gripe with NC has always been that keeping it up to date is a pain, I love the actual functionality. I'm in the process of migrating my install from a normal install in a TrueNAS Core jail to the containerized version in the Linux version of TrueNAS and that too is a struggle. I'm hoping that the containerized version will be easier to keep up to date, as that seemed to go wrong constantly.
I have a Nextcloud running in docker for years, the update has always been just docker pull. After years of suffering with the native installation, and upgrade processes that never worked, I migrated to docker and it couldn't be simpler.
This is one of the reasons every time someone says "you don't need docker to run your server" I'm like "yes, but that's like saying you don't need a vehicle to travel 100km".
The issue for me is that the docker update alone doesnt do it. I have no idea why and at this point I‘m to tired to care.
If the docker update doesn't update things you might not be using docker at all. Docker is like having a VM that you destroy after every run, so it's not that it updates the version, it is as if you were spinning up a new machine with the new version, a machine running the new version can't be running the old version by definition, unless you did something like telling that machine to overwrite the installation folder with a local one, e.g. by having something like
- /var/www/nextcloud:/var/www/nextcloud(or whatever the path is where you have next cloud installed locally) in your volumes for the docker, which would be akin to buying a new PC because your GPU is old, immediately swapping out the new GPU for the old one, and wondering why the new GPU is so slow.Thanks for explaining. I know how docker works but I have the suspicion that l I might in fact have one persistent volume too many. I‘ll check that again if I have time. Thanks again.
Yeah, if you have a volume mounted on the folder where next cloud is installed it would be the same as what I mentioned. Look for anything mounting on
/appthat should be used from the image.That being said be careful, if you haven't upgraded in a long time it's possible the automatic upgrade won't work or might break stuff.
I am updating regularly. Its just not automatic, which kinda sucks. Thanks for explaining. I'll check it out.
I wrote a custom script to update it so I can very much understand that sentiment. I‘m also not the largest fan of the service just randomly breaking every couple of weeks and then having to run my update script. I‘m running the linuxserver docker compose version iirc.