this post was submitted on 11 Aug 2023
930 points (98.3% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54609 readers
444 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Beautiful project! One feature request/ question: Would it be possible to have a config file/gui with the api keys instead of having them in the compose file?
You can already do this. You can specify an env file or use the default
.env
file.The compose file would look like this:
And your
.env
file would look like this: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.Yeah, but I’m using a gitops approach with portainer stacks. I’ve not been able to do .env files with that setup thus far.
@[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