skadden

From Summit:

Everything working for me as expected on v0.2.1+13

@[email protected] 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.

How so? The three biggest things I attribute to Google are search, ads, and their mail/calendar/drive/docs suite. The only thing I see Proton doing is the last, which serves as an alternative to more than just Google.

(I ask this as someone that does not use Proton as primary for anything)

They have a similar integration with Bitwarden that I've used a bit. I ended up stopping though because I rely on a catch-all and just give out companyname@ or something generic like work@ or family@. Sure it's easy to guess but I haven't had any spam issues in the ~15 years I've been operating this way.

Nobody actually gets my Fastmail login address though. I picked a random string on one of their domains that's literally only used to sign in. A fun little added obscurity feature.

Yeah I suppose I could be missing email and not know (because it never got delivered) but I get everything I expect to receive and I haven't had anyone reach out asking why I haven't responded to an email I never received. It's good enough for me for now though.

LDAP support isn't something that's ever crossed my mind for mail, definitely a legit reason to stick with the Googs.

Yep. It was a fun ooh look what I can do that I have exactly zero people to communicate with using those features.

In the same vein, not using Google is similarly silly. Most of my personal contacts use Gmail or o365 so they still get a copy of my email anyway. But at least this way my money isn't going to them and nobody's scanning my inbox to advertise to me (☞ﾟヮﾟ)☞

I moved to Fastmail last year and it's been entirely unremarkable which is exactly what I want. Mail in and out works, it's reliable, I have my custom domains.

It really depends on the level of privacy you're going for and what features you want. For me I needed custom domain support with catchalls. The only other requirement I had was to not be Google. I debated between Fastmail and Proton for a while (Fastmail for features/price, Proton for the "better" privacy.) Ultimately I ended up on Fastmail because I would have had to pay for a higher than necessary account at Proton for what I wanted.

Like others have asked, how exactly did you create these containers? If they were through Portainer did you use a compose file in a stack or did you use the GUI the entire way?

This will nuke them assuming you don't have something recreating them.

docker ps -a # find your rogue container, copy the container id, my example is a0ff66a83c73
docker stop a0ff66a83c73
docker rm a0ff66a83c73

My suggestion is to go through the process you did to try to deploy them and clean it up from that direction.

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.