@noxxville You sure can, and what I would suggest is rather than having them in the same compose file, I would make a completely separate folder with its own compose file and its own copy of all the containers. The main things you would need to change are the port numbers and any duplicate names (services, networks, absolute paths, etc.).
Doing it that way you can easily take one down for maintenance without disturbing the other, or also easily move one to a separate server later if you decide to.
I wanted to take a moment to reply and, firstly, say thank you for this. This walkthrough was incredibly useful and functionally essential to my deployment of my own instance using docker.
I also wanted to commend you on your effort. I saw your posts as far back as 2019 when I was triaging a problem related to Collabora not displaying documents (which had to do with PEBKAC on my end, not yours) and developing your skillset then contributing it back.
Thank you. Glad it was helpful. I actually started working on an update to this over the weekend for Ubuntu Server 20.04 and Nextcloud 21. I want to integrate both of the high performance backends, and Iām debating leaving the Collabora part off since both Collabora and ONLYOFFICE are integrated now.
I think Iāve got the Files HPB working. I need to do some testing on that and then figure out the Talk HPB. My goal is to get both backends integrated in one docker-compose setup.
However, in case anyone is trying to run Nextcloud + Collabora inside Docker on and old Debian machine (8 or older), I banged my head against the wall for hours with Collabora failing to respond until I found my way to this answer:
Can I upgrade my docker image to a later version of NextCloud? How do I do it?
There seems to be an app (music) that interferes with my docker image and now I cannot login to Nextcloud. Do you know why this happens and how I can fix it?
Point taken. I will hope for an answer on those channels. Unfortunately occ app:disable does not work in this case. Do not know why. I just pulled Nextcloud and it seems fine when I am locking at things in terminal in the folder where the docker image is. Unfortunately when I occ upgrade it does not work. There is an error that has got to do with the music app (that I fully regret installing now as I have never ever used it) and I am stuck in maintenance mode. Not very happy about that.
It all started when I tried to update apps in the UI inside Nextcloud. Should not have done it without upgrading Nextcloud first.
If you disable HTTP rather than use a redirect, keep in mind that not all browsers will automatically go to HTTPS. Itās likely to cause confusing among your users when they just type in the FQDN and hit enter.
You have to keep the port open anyway if you use certbot, even if you take away the redirect.
@gas85 did not use exactly the correct word thereā¦ HTTP is of course not really disabled on the web server, if you use a VirtualHost on port 80. But with the permanent redirect he added, all HTTP requests are redirected / rewritten directly to HTTPS. And yes, you are right, port 80 has to be left open for this to work.
Hi Martin, nobody knows how your system is build and you should check if there is some special setting you have now or if itās safe to start from scratch using template providedā¦ I would just compare both files and decide which path to followā¦
First of all, I want to say thank you to @KarlF12 for making this guide. Youāre my saviour because this guide is so thorough. Of course for you guys who joined in this discussion too, thank you. Now I have my nextcloud runs perfectly! (except for svg support)
Okay, now I want to share my experience following this guide. I use Ubuntu 20.04, with split horizon dns using pi hole.
In apache, I only set 001-nextcloud.conf and 999-catchall.conf because I donāt have plan to use collabora.
Somehow 999-catchall.conf that Karl provide didnāt work. I had to add:
I didnāt set COLLABORA_FQDN and NEXTCLOUD_IPADDRESS in .env file. In docker-compose.yml, I removed collabora section and also removed extra_hosts on nextcloud section.
After I ran docker-compose successfully, on host, I changed the data folder ownership to www-data:www-data. Little bit confused at first whether to change ownership on the host or inside the container.
Set alias occ to ~/.bashrc and resolved proxy issue. I also configured default phone region by running this command:
occ config:system:set default_phone_region --value="<Your Country Code>"
You know, Iāve thought about it a few times, but Iām debating whether itās obsolete now with the release of Nextcloud AIO. I havenāt actually tried it yet, but it looks promising.
Something I wanted to do if I ever did a rewrite was add the two high performance backends. They have them in AIO, and it would take me a lot of time to reinvent the wheel.
At the moment AIO is not a complete replacement of self build docker(-compose). It must be the only system running e.g. you canāt add another software behind AIO reverse proxy, you canāt install AIO behind existing reverse proxyā¦ it needs write access to docker-socket (e.g. root on the host). all this points are known but there is no roadmap.
There is a discussion to use AIO as starting point to build fully customizable docker-compose system
If this works we could have a simple āone-clickā AIO and customizable docker-compose for more advanced use casesā¦