submitted 7 months ago by flor0@sh.itjust.works to c/selfhosted@lemmy.world

26 comments fedilink hide all child comments

For years I've been running my Nextcloud on bare metal. Now I finally decided to switch it to docker. I looked into Nextcloud All-In-One and it seems easy to deploy but it lacks configuration options like multiple domain names and putting it behind a traefik reverse proxy is kind of a pain to set up.

You can check out my solution on GitHub. I decided on a docker compose setup with nginx, php-fpm and redis(redis is now replaced by KeyDB) in separate containers. Obviously it's for experts but it's a lot more configurable. than AIO. It's also just as easy to migrate to as with any bare metal setup and just as configurable.Yes it's still a pain to set up, but better than the bare metal version lol

What do you guys think about putting the different components (webserver, php, redis, etc.) in separate containers like this, as compared to all in one? Feedback is greatly appreciated!

you are viewing a single comment's thread
view the rest of the comments

[-] gaf@borg.chat 10 points 7 months ago* (last edited 7 months ago)

If you weren't aware, Nextcloud provides non-AIO compose files in their docker repo: https://github.com/nextcloud/docker/blob/master/.examples/docker-compose/with-nginx-proxy/postgres/fpm/docker-compose.yml

[-] flor0@sh.itjust.works 3 points 7 months ago

Seems similar to what I'm doing but it uses the nextcloud:fpm-alpine image, which is community maintained. It's a valid approach but I prefer to tweak my php-fpm config myself. By using their docker image you basically lose a bunch of freedom to configure your setup, but it's easier to set up for sure

this post was submitted on 06 Apr 2024

64 points (92.1% liked)

Selfhosted

39677 readers

390 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:

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!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz