r-freeman/workflow-with-secrets
1
0
Fork 0
mirror of https://github.com/r-freeman/workflow-with-secrets.git synced 2024-11-14 12:25:41 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Compare commits

base: r-freeman:f6ca46ff6419eb7cd094c3e188c0ae8750eb9af5
Branches Tags
r-freeman:main
...
compare: r-freeman:973e2f37bb2015dd7b3590893a4a6c9ff0da6112
Branches Tags
r-freeman:main

2 Commits
f6ca46ff64 ... 973e2f37bb

Author SHA1 Message Date
Ryan Freeman
973e2f37bb update README
All checks were successful
Decrypt Secrets / DecryptSecrets (push) Successful in 3s
Details
2024-08-20 22:46:52 +01:00
Ryan Freeman
ed014c671f add readme 2024-08-20 22:33:58 +01:00
1 changed files with 14 additions and 0 deletions
Show Stats Expand all files Collapse all files

14
README.md Normal file
View File

@ -0,0 +1,14 @@
## Workflow with secrets
Useful Gitea workflow for safe decryption of secrets in a .env which might contain sensitive data such usernames,
passwords, API keys, database connection strings and so on. A good use case for this workflow is to use it to provide decrypted
environment variables at runtime to a docker container. For example, `docker run --env-file ./.env ubuntu bash`.
### How to use
Clone or fork the repo and create a .env file containing key/value pairs of environment variables. For
example, `SUPER_SECRET_PASSWORD=bzdBkRzh4F7UYWx5KXjw3TBm`. Then encrypt the .env with `gpg --symmetric --cipher-algo AES256 .env`
choose a passphrase and keep note of it. Make sure to commit and push the encrypted .env.gpg file.
On the Gitea side, go to Settings > Actions > Secrets and create a new secret called SECRET_PASSPHRASE and set it to your
passphrase.