AS a developer, I want the docker compose files to use .env when composing up #288
Labels
No labels
blocked
duplicate
enhancement
good first issue
help wanted
invalid
needs criteria
needs estimate
needs testing
question
type
admin
type
bug
type
change
type
defect
type
dependencies
type
documentation
type
epic
type
incident
type
investigation
type
spike
type
story
type
subtask
wontfix
blocked
duplicate
needs criteria
needs designs
needs estimate
needs testing
question
type
admin
type
alert
type
bug
type
defect
type
dependencies
type
design
type
documentation
type
epic
type
incident
type
investigation
type
spike
type
story
won't fix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: RabbitLabs/vylbot-app#288
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Story Points: 3
AS a developer, I want the docker compose files to use the .env when composing up
SO THAT I can keep the passwords secret out of source control
Acceptance Criteria
AS a developer
GIVEN I want to compose up the docker containers
WHEN I run
docker compose up -d
THEN the command should use the variables from the
.env
fileSubtasks
.env
variablesNotes
Use docker secrets for docker compose filesto AS a developer, I want the docker compose files to use .env when composing upThis was done as part of the migration to forgejo actions