Unable to specify stacks that don't have `app-` prefix
ChrisBAshton opened this issue · 3 comments
E.g. govuk-content-schemas:
$govuk-docker startup
Unknown stack: app.
Available stacks:
lite
$govuk-docker startup lite
Unknown stack: app-lite.
Available stacks:
lite
Have tried passing --stack=lite
which used to work but has now been removed from govuk-docker.
This is intentional, albeit slightly confusing. If the service doesn't have an app-
prefixed stack, then it can't be run using the startup
command. Instead you would use the normal run
command.
This is to make a distinction between apps where "starting up" is meaningful (such as a web application) and apps where this makes less sense (such as the content schemas).
The error message could definitely be improved though...
Cool, thanks for explaining 👍 perhaps we can check if an app has no app-
prefixed stacks, and throw a more helpful error message if the dev tries running startup
.
I think we can close this issue, now that #216 is merged. The original problem was the CLI output is misleading, but we no longer have a CLI!
@ChrisBAshton that OK with you?