Cannot read property 'connection' of undefined

I tried to install Ghost locally, but it kept giving me an error.

Debug Information:
    OS: Ubuntu, v20.04 LTS
    Node Version: v12.18.0
    Ghost Version: 3.19.0
    Ghost-CLI Version: 1.14.1
    Environment: development
    Command: 'ghost install local'
Message: Ghost process exited with code: null
Stack: Error: Ghost process exited with code: null
    at ChildProcess.<anonymous> (/usr/local/share/.config/yarn/global/node_modules/ghost-cli/lib/utils/local-process.js:68:24)
    at ChildProcess.emit (events.js:315:20)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)

ghost doctor found nothing.

Here is the output of ghost run.

/home/joseph/Documents/ghost-dev/versions/3.19.0/core/shared/config/utils.js:103
        delete database.connection.host;
                        ^

TypeError: Cannot read property 'connection' of undefined
    at exports.Provider.sanitizeDatabaseProperties (/home/joseph/Documents/ghost-dev/versions/3.18.0/core/shared/config/utils.js:103:25)
    at Object.loadNconf (/home/joseph/Documents/ghost-dev/versions/3.18.0/core/shared/config/index.js:52:11)
    at Object.<anonymous> (/home/joseph/Documents/ghost-dev/versions/3.18.0/core/shared/config/index.js:83:27)
    at Module._compile (internal/modules/cjs/loader.js:1138:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
    at Module.load (internal/modules/cjs/loader.js:986:32)
    at Function.Module._load (internal/modules/cjs/loader.js:879:14)
    at Module.require (internal/modules/cjs/loader.js:1026:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at Object.<anonymous> (/home/joseph/Documents/ghost-dev/versions/3.18.0/core/shared/sentry.js:1:16)

[acburdine]

@juniorRubyist what happens if you run ghost run -D…ghost run will default to trying to load a production config, adding -D will tell it to load the development one

[github-actions[bot]]

Our bot has automatically marked this issue as stale because there has not been any activity here in some time. The issue will be closed soon if there are no further updates, however we ask that you do not post comments to keep the issue open if you are not actively working on a PR. We keep the issue list minimal so we can keep focus on the most pressing issues. Closed issues can always be reopened if a new contributor is found. Thank you for understanding 🙂