Improve logging output about ghost-cli

[acburdine]

So the design of the CLI is that each process manager is responsible for starting and spawning its own ghost process, which includes managing logs and other things. (kind of works similar to the storage adapters in ghost itself).

My thought here is to add better logging output to the local process manager and then possibly a ghost log command that also integrates with the process manager to return the log.

As far as logging directly to stdout/stderr in development mode, that's probably best left to the process managers themselves - might be willing to add that to the local process manager but thinking about it it might not be within the scope of the CLI. IMO Ghost-CLI should be used to install ghost for production or locally for development of themes/apps/adapters/etc, but if Ghost core itself is actuallly being worked on the CLI shouldn't be used to install it.

[ErisDS]

IMO ghost install will always use production mode, and ghost install local will do a simpler install for development mode using the local process manager.

The intended use for ghost install local is theme & app development, so whatever logging solution is designed should consider this usecase - what to theme / app developers need?

I think they will want to be able to view any error output they generate whilst developing?

[acburdine]

This will also likely be addressed by #66