Again, please take a moment to read the CoC linked in my previous thread.
You’re right that I didn’t tell you how, and that’s because I forgot that the CLI handles the issue you mentioned
by running sudo chown -R ghost:ghost /path/to/install/content because that’s the only folder the system user needs access to (everything else needs to be read-only). I was expecting that saying no to systemd and nginx would be enough to have the CLI not ask for sudo access
You can bypass all sudo requirements by adding the --no-setup-linux-user flag to the installation and saying no to systemd and nginx. (e.g. ghost install --no-setup-linux-user)
Just so you understand, the CLI has a happy path that works for most users. It’s possible to use the CLI outside of the happy path, but there’s a lot less documentation and hand-holding because functionality is a “best-effort” guarantee.