Initializing

[stuartpb]

Right now, every command fails if an app doesn't exist, yet checks before doing a release (even though the only way to create an app, currently, is to do a build of it).

Also, every command (once it's shown that the app exists) touches the config.env file to initialize it.

These are both maybe kind of stupid.

Thoughts:

• It's worth failing if the app doesn't exist- otherwise, you'd be "creating" empty apps by making a typo in the app name, and then you wouldn't get an error telling you you made a typo.
• You should be able to create an app, configure it, then push its code so it starts fully configured with its first deploy.
  • re: app creation - see also Implement Heroku-equivalent commands plushu-apps#2, Refactoring plushu-git#5
• Less boilerplate is better (although not essential).

[stuartpb]

plushu/plushu-git#5 lays out the app creation flow and responsibilities - yes, it permits for create->config->push.

Commands checking before release is still the right behavior.

[stuartpb]

Commands checking before release is no longer the correct behavior: see plushu/plusku#2.

[stuartpb]

Pretty sure this has been long since resolved.