I like where your head’s at. I’m gonna go with the expecting more indictments angle paired with not being as rich/liquid as he’d like everyone to believe. What an unavoidable situation he’s found himself in.

That’s a valid point I hadn’t considered. Based on a cursory look at how bail bond works, if you go with a bondsman you’re out a certain amount regardless if you show up to court or not.

So if he paid the 200k he’d get almost all of it back after court, minus whatever processing fees the court has. If he goes with the bondsman he forks over 10% and the bondsman covers the other 90%, but he would get nothing back after court. The bondsman gets the full refund and keeps it all.

I can’t imagine the return on that would move the needle much for someone as “rich” as he is. I don’t know though, and I’ll fully admit this is pure speculation.

Doesn’t this make her point even more? Had to use a bondsman for 20k but he’s super rich? Yiiikes

Agreed. I haven’t come across any instances I care to participate in that have that enabled though.

This is ultimately why I decided to roll my own instance. I’m keeping my backup here though in case I mess something up, but full control is nice to have.

@synae@lemmy.sdf.org is correct, you can pass the values through that part of the UI. I used to do it that way and had Portainer watching my main branch to auto pull/deploy updates but recently moved away from it because I don’t deploy everything to 1 server and linking Portainer instances together was hit or miss for me.

Edit: I just deployed it like this (I hit deploy after taking the screenshot) and confirmed both inside the container that it sees everything as well as checking where Portainer drops the files on disk (it uses stack.env)

Stack settings

Environment vars in container

Portainer stack on disk

I don’t know why I did all that, but do with it what you will lol

This looks great. Gonna give it a whirl this weekend

You can already do this. You can specify an env file or use the default .env file.

The compose file would look like this:

environment:
      PUBLIC_RADARR_API_KEY: ${PUBLIC_RADARR_API_KEY}
      PUBLIC_RADARR_BASE_URL: ${PUBLIC_RADARR_BASE_URL}
      PUBLIC_SONARR_API_KEY: ${PUBLIC_SONARR_API_KEY}
      PUBLIC_SONARR_BASE_URL: ${PUBLIC_SONARR_BASE_URL}
      PUBLIC_JELLYFIN_API_KEY: ${PUBLIC_JELLYFIN_API_KEY}
      PUBLIC_JELLYFIN_URL: ${PUBLIC_JELLYFIN_URL}

And your .env file would look like this:

PUBLIC_RADARR_API_KEY=yourapikeyhere
PUBLIC_RADARR_BASE_URL=http://127.0.0.1:7878
PUBLIC_SONARR_API_KEY=yourapikeyhere
PUBLIC_SONARR_BASE_URL=http://127.0.0.1:8989
PUBLIC_JELLYFIN_API_KEY=yourapikeyhere
PUBLIC_JELLYFIN_URL=http://127.0.0.1:8096

This is how I do all of my compose files and then I throw .env in .gitignore and throw it into a local forgejo instance.

I don’t do it all in one compose file out of preference, but as others have said Gluetun + your preferred torrent client with all networking going to Gluetun. I’ve been running this way with deluge for a while now and it’s been solid as a rock.

I pretty much always leave stuff seeding once I get it these days. Ever since I bumped the disk space on my NAS it made it a lot easier to leave stuff instead of jockeying for space on disk.

My higher ratio items are all old shits like You Got Served lmao