abra app new [<recipe>] [<version>]
#519
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#519
Loading…
Reference in New Issue
Block a user
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?
The version tag should also be provided for creating new apps, else it could produce inconsistency between the generated .env file and the app version that should be deployed.
A
--force
flag to overwrite the current .env file would also be nice.Nice. Should the interactive prompt also for version number? This reminds me to get a test in place to check that
app new
does indeed check out the lastest version before copy/pasta'ing the.env
files.