this post was submitted on 06 Apr 2024
63 points (92.0% liked)

Selfhosted

40173 readers
789 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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
[–] [email protected] 16 points 7 months ago* (last edited 7 months ago) (11 children)

People usually come here looking for advice on how to replace their dockerized nextcloud setup with a bare-metal setup. Now you came along presenting a solution to do the reverse! Bravo!

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?

I actually has a similar setup, but with nextcloud apache container instead of php-fpm, and in rke2 instead of docker compose.

[–] [email protected] 2 points 7 months ago (1 children)

Thanks for the kind words! Could you link me to the apache container you use? I would like to replace nginx since it's not officially supported but still need to do some research on apache

[–] [email protected] 3 points 7 months ago* (last edited 7 months ago)

I'm currently using nextcloud:26-apache from here because some nextcloud apps I use is not compatible with v27 and v28 yet. The apache version is actually less hassle to use because nextcloud can generate .htaccess configuration dynamically by itself, unlike php-fpm version where you have to maintain your own nginx configuration. The php-fpm version is supposedly faster and scale better though, but chance that you won't see that benefits unless your server handles a large amount of traffics.

load more comments (9 replies)