Jira is great software if you ignore all the insufferable bugs in it that Atlassian ignores just to make their on-prem option so clunky you have no choice but to use their SAAS offering. I know, I know, "ThEy DrOpPeD sUpPoRt AlReAdY!"

ever had to rebuild a sprint because Jira failed to properly migrate the old cards over to the new one, but instead throws them all into the backlog randomly and now you have to hunt them down over the next hour?

how about when you're writing an update to a card and you're two paragraphs in with log examples and the UI decides to dump your entire content when you accidentally click outside the wysisyg?

But how can I forget the worst one! have you ever had your session timeout while you're writing a detailed bug report with screenshots, logs, and example data, and when you finally submit it you lose EVERYTHING because you need to login again and you can't go back?

I have, and you know what, I'll still use Jira because even the best trash can be better than the worst trash.

yeah, I'll take a fat dump on shitty products all day long because the negligence of Atlassian product development is abhorrent and deserves to be called out.

is this this same repair manual they follow in the store?

you know, the one where they break something else and/or claim it was your fault and refuse to repair it and only give it back to you in pieces.

I absolutely love how this implies that the team is happy before going to Jira.

so not only can Atlassian not write software, they can't develop a usable product, and they can't even market it without insinuating how shitty it is.

I would recommend it. Speaking from personal experience, I trusted my VPN connection to remain on and self-heal. Thinking that cost me a strike against my ISP.

Now I know for a fact that if anything goes wrong with the VPN connection, all the containers that need it will need to restart before they have connectivity again and that can only happen after the VPN container restarts and passes healthcheck.

IMO this is the best OS way, but without nix it's a pita to maintain through restores/rebuilds. personally I never fully comprehended how to properly configure iptables/routes (I did try though, so nobody can blame me lol).

however, a major benefit to using a contained VPN or gluetun is that you can be selective on what apps use the VPN.

I host 12 other containers (with nas mounts) on the same host outside of the three that need to use a VPN, so this is why the solution I described works for me. and should I ever need to use routes for more advanced network filtering I still have it available without adding the complexity of splitting normal traffic vs VPN traffic.

I'll ask this question because it might be something you didn't think of.

What happens to your network connection if the VPN fails? will it continue to connect without a VPN?

I had a similar case of that happening, and ended up causing me to get some shame mail from my ISP.

now I run my VPN inside docker, and any containers that need access to it are configured as network slaves to it. VPN goes down? container reboots, all the others reboot after connection is restored, but will have no connection while it's down.

it's all in a well designed system of healthchecks and container configuration.