Add file_envs for secrets and allow passing database url via separate envs #246
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
question
S
UX research
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: local-it/mitgliederverwaltung#246
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "add-file-envs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description of the implemented changes
The changes were:
What has been changed?
changed runtime.exs to support file_envs
update docker-compose.prod.yml to reflect these changes in said environment, added just commands to generate secrets on first start
Definition of Done
Code Quality
Accessibility
Testing
Additional Notes
Great work!
One thing that would be great is updating README.md to list the new
_FILEvars in the configuration guide.@ -88,0 +90,4 @@# ================================# Initialize secrets directory with generated secrets (only if not exists)init-secrets:Should we name this action
init-prod-secretsto communicate its scope?@ -10,0 +21,4 @@file_path ->case File.read(file_path) do{:ok, content} ->String.trim(content)Is this
trimspecifically needed? Seems like it could lead to some surprising behavior in some edge cases.replaced by trim_trailing
@ -58,3 +123,3 @@client_id: System.get_env("OIDC_CLIENT_ID") || "mv",base_url: System.get_env("OIDC_BASE_URL") || "http://localhost:8080/auth/v1",client_secret: System.get_env("OIDC_CLIENT_SECRET"),client_secret: get_env_or_file.("OIDC_CLIENT_SECRET", nil),Let's add an error message here, similar to the other calls
@ -1,22 +1,33 @@services:app:image: git.local-it.org/local-it/mitgliederverwaltung:latestimage: mitgliederverwaltung:latestShould we change this back? Or is there a way we can support dev environments and "real" prod deployments with the same file?
was just for testing, whoopsie