Programmatic use of Ghost-CLI #194
Labels
Comments
ErisDS
added a commit
to ErisDS/Ghost-CLI
that referenced
this issue
May 3, 2017
refs TryGhost#194 - If --sslemail is provided, use that instead of prompting - Makes it easier to call ghost programmatically
ErisDS
added a commit
to ErisDS/Ghost-CLI
that referenced
this issue
May 3, 2017
refs TryGhost#194 - If --sslemail is provided, use that instead of prompting - Makes it easier to call ghost programmatically
ErisDS
added a commit
to ErisDS/Ghost-CLI
that referenced
this issue
May 3, 2017
refs TryGhost#194 - if --start is provided, use that instead of prompting - makes it easier to call ghost install/ghost setup programmatically
acburdine
pushed a commit
that referenced
this issue
Jun 9, 2017
refs #194 - if --start is provided, use that instead of prompting - makes it easier to call ghost install/ghost setup programmatically
acburdine
pushed a commit
that referenced
this issue
Jun 13, 2017
) refs #194 - If --sslemail is provided, use that instead of prompting - Makes it easier to call ghost programmatically
|
Going to close this for now as the two merged PRs have fixed this issue for now - Further improvements upon this will happen as a part of #179 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ghost-CLI's interactive UI is super-crazy-awesome for users in the most common use-cases, which is doing a 1 time install on either a new or existing server.
However, in certain cases, it's desirable to be able to call ghost-cli programmatically, rather than manually & interactively. Ordinarily, I'd say it was up to the consumer to figure out how to do this, however the way that ghost-cli's interactive UI works by rewriting the prompt makes it very hard to answer the prompts programatically with something like expect.
Therefore, I'd like to introduce a path-of-least-resistance workaround, which is to make it possible to pass in enough arguments that ghost-cli knows what you want it to do and doesn't output any further prompts.
To achieve this with the current features of Ghost-Cli I propose two additional arguments for the CLI install/setup commands:
sslemail, e.g.--sslemail=me@mine.com, toggle SSL setup with this addressstart, e.g.--startor--start=false, toggles whether or not Ghost should be startedThe text was updated successfully, but these errors were encountered: