Yeah I learned my lesson after trying to rip out and replace some moldy drywall and ran into asbesdos backing panels. Never again lol.

Oh no! I’m so sorry, that sounds stressful. I’m glad you managed to balance it though.

Needs more garlic.

You’re going god’s work

Well first off swarm doesn’t work with environment variables, so if you pass any in you’re going to need to pipe the output of docker compose read into docker swarm service create.

Your port settings are gonna give it a problem too, swarm doesn’t support that new syntax, and as a result you can only assign a single network interface to a service.

Regarding networking, since the whole paradigm is that you’re not defining a single container but a service that can live/move across multiple nodes; any traffic to any node in your swarm will be routed (round robin style) across the copies of that service. (This makes logging setup a PITA, ask me how I know!)

Bind mounts aren’t recommended, volumes are preferred. Otherwise everything needs to be mirrored across all nodes, depends on the use case.

That being said I’m not convinced that swarm is the right answer here, I concur with @talentedkiwi@sh.itjust.works. You should just install pangolin on your second machine.

Wow fuck those readium guys

We need an RSS feed for saved posts, but the Devs seem to think it would be a privacy issue. Now idk what kinda Fucked up porn They’re saving on Lemmy but I just want to read the articles I save on here in my RSS reader.

Former hotel bartender here, can confirm.