Settle on a package description format for apps #33

New Issue

decentral1se · 2020-10-26T17:54:32Z

decentral1se commented

2020-10-26 17:54:32 +00:00

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:

---
name: wordpress
  description: Open source software you can use to create a beautiful website, blog, or app
arguments:
  name:
    description: name of the deployed app (e.g. fashion revolution)
secrets:
  admin_passwd:
    description: The administrator password

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.

`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: ```yaml --- name: wordpress description: Open source software you can use to create a beautiful website, blog, or app arguments: name: description: name of the deployed app (e.g. fashion revolution) secrets: admin_passwd: description: The administrator password ``` 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.

decentral1se changed title from ~~Settle on a YAML package.yml format for apps~~ to Settle on a package description format for apps

2020-10-26 17:54:44 +00:00

decentral1se referenced this issue

2020-10-26 17:59:31 +00:00

How do we manage versions of apps? #34

decentral1se added this to the Public mini-launch milestone 2020-10-27 08:04:48 +00:00

decentral1se added the

design

label 2020-10-27 08:09:14 +00:00

decentral1se commented

2020-10-30 01:17:19 +00:00

We'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 using abra app <domain> config.

We'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 using `abra app <domain> config`.

decentral1se closed this issue

2020-10-30 01:17:19 +00:00

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#33