if you continue to try { thisBullshit(); } you are going to catch (theseHands)
This is the most beautiful thing I’ve read all year
if you continue to try { thisBullshit(); } you are going to catch (theseHands)
This is the most beautiful thing I’ve read all year
There’s maybe two problems with this:
It’s a common attitude, so don’t feel like i’m picking you out personally to scold. More people should be aware of how that attitude dehumanizes people experiencing shelter insecurity.
I’m so curious about those two downvotes
This is… this is really antisemitic… right? And Islamophobic…?
This is definitely some nazi shit
This is the entire issue for me.
Privatizing what is otherwise public content, and then privatizing the models that are trained on that content and making me pay for having it regurgitated back at me.
I think AI would be really cool, IF:
-it wasn’t being shoved into every goddamn thing -it wasn’t being used as justification to cut jobs -it was a open source project and wasn’t being gatekept by capitalist interests
No matter how many Palestians get killed or schools and hospitals get bombed, when it finally stops, the US will parade around that brief moment of peace as some great, masterful example of diplomacy.
There will be no retribution or justice for the Palestinian people.
Tinytina coyly laughing behind her hand actually made me angry
This article was about what strategies and campaign messaging the opposition used to sway voters, and your takeaway from the article was ‘they voted’?
I’m not convinced you read it.
Reminds me of this scene in the big short:
Yup, I was only pointing out that i was having trouble doing the same thing in my docker compose (using the webui_port env variable did not avoid port collisions at deployment)
I haven’t tried this particular compose outline though. It could also be the pirate_network they’re initiating or the depends_on variables they’re using, I just haven’t played around with it yet.
Question: how are you deploying your arr apps? do you do that in a separate compose file?
AFAIK the thing that complicates this is trying to run it behind gluetun
docker makes it really easy to specify a unique port on deployment, but when you’re using a network bridge (as in the case of gluetun) the networking settings are controlled there instead, so you can’t use the normal port declarations. It’s apparently not impossible to do it with gluetun but it seems it’s not as straightforward.
lmao. I’m starting to really wonder what the WEBGUI_PORT variable does if not exactly what you’re changing in the GUI… someone else mentioned they got multiple instances to deploy from the same compose file by placing the gluetun service at the end of the file. I wonder if the order in which the containers are deployed is the thing that makes this work. i’ll test more when I have the time
I might need to try this… I wonder if it makes a difference that the gluetun service is listed last. I noticed that trying to start the containers in the wrong order results in port collision errors, maybe this is why it works for you?
This worked!!
Shame that it’s a little bit of a runaround, but not only did this work, it also persists after restarts and updates.
I’ll be editing my post and offering it as a solution to the other places I have seen this question asked, thank you a ton!
I’m looking at hotio now.
their documentation isn’t as comprehensive as linuxserver.io, i’ll probably have to just try it out and see if it works. looks like they also have one that has wireguard bundled but it’s really unclear how that works
Can I ask what your compose file looks like? Or how you deployed?
yea, i just tried a couple things to no avail:
publish a new port in gluetun, e.g.
- 8082:8082
then set webui port in the new instance:
- environment:
- WEBUI_PORT: 8082
error on deployment
Then I tried spinning up the new container separately, declaring the pots eg:
- ports:
- 8082:8082
and then manually switching the network to gluetun and turning off the port declaration, and it still ends up on the default port. Bummer.
Yup, I ended up frankensteining a nas from various craigslist parts (i actually found a low-power business-class server motherboard that has worked out well for the purpose). Had to get a SAS HBA card and a couple SFF-8087 cables to do the job right, and I grabbed an old gaming case from the 2010’s to hold it all, but it was relatively seamless. I had one of the drives go out already, but luckily I had it in a raid configuration with parity so it was just a matter of swapping out the drives and rebuilding.
It’s been fun and rewarding, for sure! I’m glad I didn’t sell them like these other dweebs told me to lol