ghost-cli log destination option (and/or option to suppress logging to file)

I’d like to be able to install ghost into a location where the user account ghost is running under doesn’t have write access to.

I’ve configured ghost such that it never writes to this directory (i.e. content directory is at a writable location), but running ghost-cli as that user causes errors because it doesn’t have permission to write the ghost-cli-debug-$date.log file.

It would be nice if there was an option for the log file path so that it doesn’t write to CWD (i.e. where ghost is installed). It would also be nice if there was an option to suppress file logging from ghost-cli entirely.

[acburdine]

Closed by #237 - error logs are now put in the home directory (under ~/.ghost/logs)

[acburdine]

Apologies for the lack of clarification. The logs in question are debug logs, which are only generated if something goes wrong and is not a user error (e.g. ran a command not in a ghost instance, missing/invalid config value, etc.). Any logs generated by Ghost (not the CLI) are stored in /path/to/ghost/content/logs, the same as they would be normally. So to answer your question, the debug logs are under the home folder of the user that ran the ghost-cli command, not the user that actually runs Ghost.

It’s exactly the same use-case as yarn/npm. Npm, however, no longer stores a debug log locally - it’s stored in ~/.npm/_logs, so essentially we’re following the same behavior as NPM. It does clean up the instance folder a bit, so you don’t end up with a bunch of debug logs in the same folder. Thinking about it, npm’s reason for change is probably more that npm-debug.log files were being committed to git repos (a use-case which we don’t really have to worry about), but it still makes it cleaner.

Also, whenever a debug file is generated, a line is printed after the “debug info” that says “Additional Info can be found in <debug file in ~/.ghost/logs>”.