Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mantil deploy should create first project stage #104

Closed
ksokolic opened this issue Dec 16, 2021 · 0 comments
Closed

mantil deploy should create first project stage #104

ksokolic opened this issue Dec 16, 2021 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@ksokolic
Copy link
Contributor

While preparing a draft for template texts (currently working on GitHub to Slack) I got to following (simplified) onboarding flow for all new Mantil users: brew install mantil, mantil new --from, mantil aws install, mantil stage new, mantil deploy.
The idea with templates is to serve as landing pages for Mantil where developers will firstly find the template and get to know Mantil through them. That's why it is important to get developers as quickly as possible to that AHA moment Marko is often talking about, to get them developing in the cloud.

With the current flow I need to explain the idea of stages and introduce two commands (stage and deploy). To simply onboarding experience we should expand mantil deploy command to create the first stage for the selected project if stage doesn't already exist.
On mantil deploy:

  • if there is more than one node user is first asked to choose on which node he wants to deploy that project, if only one node exist it is taken as default (no need to write anything in second case as it is part of further output)
  • user is asked to choose a stage name, but default name development is proposed (it is taken on Enter)

Further output is the same as in stage new command.

Currently if I try to run mantil deploy without existing stage I get:

Screenshot 2021-12-16 at 14 19 04

Note: This doesn't require any change in stage command as it is still needed in current form for all future stage management.

@ksokolic ksokolic added the enhancement New feature or request label Dec 16, 2021
@ksokolic ksokolic added this to the single developer 0.3 milestone Dec 16, 2021
@djelusic djelusic self-assigned this Dec 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants