this post was submitted on 01 Jan 2024
914 points (97.4% liked)

Selfhosted

60831 readers
1250 users here now

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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] recapitated@lemmy.world 9 points 2 years ago (1 children)

Always works great for me.

I just run it (behind haproxy on a separate public host) in docker compose w/ a redis container and a hosted postgres instance.

Automatically upgrade minor versions daily by pulling new images. Manually upgrade major versions by updating the compose file.

Literally never had a problem in 4 years.

[–] cyberpunk007@lemmy.world 4 points 2 years ago (2 children)

I'm still too container stupid to understand the right way to do this. I'm running it in docker under kubernetes and sometimes I don't update nextcloud for a long time then I do a container update and it's all fucked because of incompatible php versions of some shit.

[–] recapitated@lemmy.world 3 points 2 years ago

I don't remember much about how to use kubernetes but if you can specify a tag like nextcloud:28 instead of nextcloud:latest you should have a safer time with upgrades. Then make sure you always upgrade all the way before moving to a newer major version, this is crucial.

There are varying degrees of version specificity available: https://hub.docker.com/_/nextcloud/tags

Make sure you're periodically evaluating your site with https://scan.nextcloud.com/ and following all of the recommended best practices.

[–] mosiacmango@lemm.ee 1 points 2 years ago

They have an "all in one" docker installer for the above because you are far from alone here.