Thanks for the drop. Just a quick notice I’m entering a very busy time of the year so if I don’t get back to anybody please don’t take it personally. If there is something that needs clarity and it’s quick I’ll probably get to it. The guide should be thorough enough for you to figure out. I know people who knew nothing about nginx and managed to set things up so I guess that’s a good way to know that your guide is sufficient enough.
I’d say Linux + Podman, or Linux + single-node microk8s. Yeah, docker has more templates, but with podman or microk8s, you learn how to do them (just my $0.02).
Ill expand on it so novasty does not have to. Podman compose is in a very infant state. I appreciate the amazing work Red Hat is doing but even though I know how to convert dockers to podman I refuse to provide any help with it as Podman is the “devs” docker rn. I highly recommend sticking with docker as does novasty. If you want documentation on podman-compose here it is. I provide no support with this statement whatsoever.
If you would like to share that information in your thread or maybe the OP wants to on a journey largely by himself. People would love that but as its a protocol and piece of software currently in largely what is considered unsupported alpha. Its not really useful for production.
Also due to how podman compose is pretty ghetto hacking away at the functions of docker compose its better that IF you move to podman you construct and build your own pods which is well beyond the scope of this thread. (While I have been practicing at this I am in no way capable of giving functional support on the topic)
Yeah, from what I’ve read in the past weeks, podman-compose is basically garbage at this point. I can completely understand the sentiment, as I refuse to offer help on some software (like unraid which came up a few hours ago in another thread).
But docker-compose is docker specific. Kompose may simplify migration to kubernetes configuration, but I haven’t tried it.
Anyway, I’m a hard-headed autist, I don’t like using config files, I’d rather convert the run commands into scripts.
To drop the links to make it easy for @Rogue-agent to find. Quoting myself here. Also all posts contain indexes to each other. If you want my rambles as I did so the blog has it.
Theres a lot of other people in there that might be able to help you more than I. I have a lot of travel coming up and im giving talks at universities and stuff. So im more just on my phone and unable to hand out anything significant. I hope this helps you.
Cool, I recommend Windows + nothing else.
Doesn’t mean I can get anything to work, but at least I’m comfortable working.
We already were able to setup NGINX-SWAG (reverse proxy with ssl) and it works. The titles don’t recommend bein significant to the topic? Reading in, idk if I need this right now…?
The issue I’m having now is that opening the sub domain cc should open the Nextcloud container but it does not.
Yea, I was using Apache with xampp, and that worked like nothing other.
Anyways I’m pretty daft. Bear with me
I guess you mean the external IP. But even with that, nothing changes, well idk. I don’t really do much with docker.
I’m see the page still displaying the main page of top domain.
I tried:
nextcloud:90
0.0.0.0:90
externalip
externalip:90
Also after you sent me that bit I looked a bit closer and I noticed, it was a total bs, that conf file that I had, should’ve noticed it.
All you did was copy my conf file and input one value in it, you didn’t do shit. I’m not familiar with docker, but I’m pretty sure pointing 0.0.0.0:90 is not going to work.
None of those are going to work because line 21 is not made to work that way. Well one of them will work, but you’re still fucking up line 21.
if you’re dockers are running correctly, they should be mapped to ports on your machine, which then you can redirect back to using the local IP of the host device.
Docker creates a private network for container(s) (unless you specify host networking). You could find out what the IPs are with docker inspect on a running container but then your setup is kinda dependent on whatever those might be and it probably will change next time you update the container(s). The way docker solved this is by having container names resolve to their private IPs within the docker network they are in.
His containers should already all be in the same docker network.
So nextcloud should be working for the upstream ip in his setup rn. Lots of nextcloud in there…