Offer to run config and deploy at the end of app new? #114

New Issue

3wordchant · 2021-03-21T13:32:28Z

3wordchant commented

2021-03-21 13:32:28 +00:00

Currently, abra offers config and deploy commands after running abra app new, but a) they are hard to copy/paste (see #106) and b) we're missing a trick! We could offer to run them straight from app new:

$ abra app new custom-html --server swarm.example.com --domain website.example.com --app-name website_example_com
...
Your new 'custom-html' app has been created!

You can configure the app by running:

    abra app website_example_com config

Would you like to run that now? [Y/n]: y
# Runs the `app config` command

You can deploy the app by running:

    abra app website_example_com deploy

Would you like to run that now? [Y/n]: y
# Runs the `app deploy` command

Thoughts?

Currently, abra offers `config` and `deploy` commands after running `abra app new`, but a) they are hard to copy/paste (see #106) and b) we're missing a trick! We could offer to run them straight from `app new`: ``` $ abra app new custom-html --server swarm.example.com --domain website.example.com --app-name website_example_com ... Your new 'custom-html' app has been created! You can configure the app by running: abra app website_example_com config Would you like to run that now? [Y/n]: y # Runs the `app config` command You can deploy the app by running: abra app website_example_com deploy Would you like to run that now? [Y/n]: y # Runs the `app deploy` command ``` Thoughts?

3wordchant added the

enhancement

question

design

labels 2021-03-21 13:32:28 +00:00

3wordchant referenced this issue

2021-03-21 13:34:11 +00:00

.env.sample contain hard-coded domains which we could search/replace #111

decentral1se commented

2021-03-21 18:40:18 +00:00

Yes, so down! Maybe adding a --force to the command to skip it all if you're moving fast (like in 36dd6b5eff/abra (L1080-L1082) ?)

Yes, so down! Maybe adding a `--force` to the command to skip it all if you're moving fast (like in https://git.autonomic.zone/coop-cloud/abra/src/commit/36dd6b5effa734f4ff77ccad3716fa25b7995d0a/abra#L1080-L1082 ?)

3wordchant commented

2021-03-21 18:45:01 +00:00

Nice nice nice. Wondering about --config and --deploy options (maybe even --no-config and --no-deploy to disable the prompts?) to split the "force", unless you think it's obvious how --force would answer both questions (my guess is "no config, yes deploy"?), and make sure there's a fully non-interactive option for both of the deploy / don't deploy cases.

Nice nice nice. Wondering about `--config` and `--deploy` options (maybe even `--no-config` and `--no-deploy` to disable the prompts?) to split the "force", unless you think it's obvious how `--force` would answer both questions (my guess is "no config, yes deploy"?), and make sure there's a fully non-interactive option for both of the deploy / don't deploy cases.

decentral1se commented

2021-03-21 19:34:05 +00:00

Hmmm good points. Maybe we need a global --no-interative option? Because passing a slightly generic --force around doesn't seem fit in all cases. Then you can do --config and --deploy which are nice and put an interactive check on the prompts and you're sorted.

Hmmm good points. Maybe we need a global `--no-interative` option? Because passing a slightly generic `--force` around doesn't seem fit in all cases. Then you can do `--config` and `--deploy` which are nice and put an interactive check on the prompts and you're sorted.

decentral1se added this to the Beta release milestone 2021-03-21 20:00:42 +00:00

decentral1se removed the

question

design

labels 2021-03-21 20:01:21 +00:00

decentral1se referenced this issue

2021-03-22 11:42:45 +00:00

Add global --no-interactive flag to high-level parser options #118

This repo is archived. You cannot comment on issues.