Choosing non-default app names breaks reporting #203
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#203
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Describe the current behavior
I haven't verified this but it occurred to me that if you choose "mycoolapp" vs. the default "my_cool_app_name" (which is generated off the domain name) and you do not add
STACK_NAME=mycoolapp
into the.env
then we can not find that app again when it is deployed.I think this is the case.
Steps to reproduce
Choose non-default app name on creation.
Describe the expected behavior
abra
knows what is deployed.Solution might be to insert
STACK_NAME=...
into the.env
when writing it? Theabra
logic internally always does a "is there aSTACK_NAME=...
present? Then use that" check.Additional information
Oh I'm tripping, it saves it as the filename!