Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fill in sample.env instead of local .env copy #479

Open
SilasPeters opened this issue Nov 24, 2024 · 0 comments
Open

Fill in sample.env instead of local .env copy #479

SilasPeters opened this issue Nov 24, 2024 · 0 comments

Comments

@SilasPeters
Copy link
Member

SilasPeters commented Nov 24, 2024

Currently we store templates for every .env file, so that bitwarden secrets are filled in when setting up the service.
However, this requires us to maintain an up-to-date copy for every service. If a sample.env is expanded, our copy becomes outdated.

Solution

Remove all templates of .env files, and create a playbook (bunch of tasks) which copy a sample.env to .env and fill in all empty values, as defined in a variables file within Ansible. This variables file has key-value pairs which read the bitwarden secrets.

The result is not having to adjust anything to the .env, unless a new type of credential needs to be inserted - for which you need to update bitwarden anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant