shaked_coffee
ok I checked and you are right, the apache container actually exposes the 11000 port on the host. so i tried following the instructions for “traefik in a docker container on the same machine” and… it still didn’t work (now I was getting a Bad Gateway error)
at this point I think I’ll just stick with my old setup with docker compose. I was interested in AIO because I thought it could have been an easier to maintain way to host NC (also considering it’s official, while the docker compose method is not) but apparently it’s not meant to be inserted in an already existing setup like mine so I’ll stick with what I currently have.
it would be nice though if the NC devs also publish a “recommended docker-compose.yaml file” (in a similar way of what Immich does) so that more advanced users still can have an easy way to set everything up without having to look for the correct containers and settings required all over the internet
thank you! so, wanting to follow your tip and exposing the 11000 port from the apache container to the host (in order to have a setup that is valid even if I move the service to another machine), how should I do that? because the apache container is also created by AIO’s mastercontainer and so I don’t have a place where to specify its port mapping (while usually I would do it adding 11000:11000 to the ports section of the docker compose)…
Thank you! Idk how but I didn’t noticed the paragraph in the docs saying that labels condition is not supported. I’ll try with the file config and see if this way I can make it work.
The only thing I’m still missing is the IP of the Apache container: shouldn’t it be an IP on the traefik_net
network where also the traefik container runs? And if so how can I specify to the mastercontainer to create the Apache container on that network with a specific IP address?
Imho the card view redesign was more than needed, thank you!
Big kudos to the thunderbird team, since the supernova announcement they’ve done a really good job
Huh! I didn’t know about all these happenings around floorp’s source code availability, but from what I can see now it should be back as fully open source under the MPL 2.0… am I wrong?
From the Floorp official website:
Floorp’s source code is entirely open, allowing anyone to view it and contribute to the project. Not only is the browser itself open source, but the build environment is as well.
Nope I didn’t, but the problem doesn’t seem to be the Python version, but instead the fact that now Python is “externally managed” and therefore I cannot install packages using pip install packagename
as it used to be.
I know that this is done for security reasons and that the good practice would be using pipx or conda, but the problem is that howdy istallation still tries to use the “old approach”