Settle on a package description format for apps #33
Labels
No Label
automation
bug
community organising
democracy
design
documentation
duplicate
enhancement
finance
funding
help wanted
invalid
publishing
question
security
wontfix
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#33
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?
package.yml
(or whatever we call it, YAML has been discussed so far but it is open) will be a file which sits inside the app repository and describes a bunch of things like the version, app name, description of the app and inputs required from the user to do a successful deployment like admin password. We need to decide on a format for that.First stab:
Then when you
abra create
or whatever, it will read this file and ask the user stuff and show other stuff to help the deployment experience go along smoothly.Settle on a YAML package.yml format for appsto Settle on a package description format for appsWe're using the
.envrc.sample
files for this for now. When a new app is created, the.envrc
is created using some sane defaults and people can just simply edit them there in-place usingabra app <domain> config
.