cee2b99e37
no issue Problem: - Running `yarn dev` with `--stripe` runs the `stripe listen ...` command in a subprocess to forward webhook events to your local instance of Ghost in development. - Currently, you have to run `stripe login` manually before this will work. If you fail to do so, the `yarn dev` script simply hangs indefinitely without any logging to indicate why. - Running `stripe login` manually is also a non-starter in Docker since you'd have to do this for each new container instance, which isn't practical. Solution: - Luckily the `stripe listen ...` command accepts an `--api-key` argument, which expects your stripe secret key. This change updates the `dev.js` script to read your stripe API key from the `STRIPE_SECRET_KEY` environment variable if it's present. As long as `STRIPE_SECRET_KEY` exists, you won't need to run `stripe login` anymore. - It also adds a timeout of 5 seconds to the initial `stripe listen` command and will exit the process if this step fails, indicating with a clear log message that you need to either set the `STRIPE_SECRET_KEY` variable or run `stripe login` - I also added a bunch of debug statements to the dev script which were useful in debugging this, and may prove useful for similar issues in the future, so I'll leave them in there. |
||
|---|---|---|
| .devcontainer | ||
| .docker | ||
| .github | ||
| .vscode | ||
| apps | ||
| ghost | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| compose.yml | ||
| LICENSE | ||
| nx.json | ||
| package.json | ||
| PRIVACY.md | ||
| README.md | ||
| SECURITY.md | ||
| yarn.lock | ||
Ghost.org •
Forum •
Docs •
Contributing •
Twitter
The easiest way to get a production instance deployed is with our official Ghost(Pro) managed service. It takes about 2 minutes to launch a new site with worldwide CDN, backups, security and maintenance all done for you.
For most people this ends up being the best value option because of how much time it saves — and 100% of revenue goes to the Ghost Foundation; funding the maintenance and further development of the project itself. So you’ll be supporting open source software and getting a great service!
Quickstart install
If you want to run your own instance of Ghost, in most cases the best way is to use our CLI tool
npm install ghost-cli -g
Then, if installing locally add the local flag to get up and running in under a minute - Local install docs
ghost install local
or on a server run the full install, including automatic SSL setup using LetsEncrypt - Production install docs
ghost install
Check out our official documentation for more information about our recommended hosting stack & properly upgrading Ghost, plus everything you need to develop your own Ghost themes or work with our API.
Contributors & advanced developers
For anyone wishing to contribute to Ghost or to hack/customize core files we recommend following our full development setup guides: Contributor guide • Developer setup
Ghost sponsors
A big thanks to our sponsors and partners who make Ghost possible. If you're interested in sponsoring Ghost and supporting the project, please check out our profile on GitHub sponsors ❤️
Getting help
Everyone can get help and support from a large community of developers over on the Ghost forum. Ghost(Pro) customers have access to 24/7 email support.
To stay up to date with all the latest news and product updates, make sure you subscribe to our changelog newsletter — or follow us on Twitter, if you prefer your updates bite-sized and facetious. 🎷🐢
Copyright & license
Copyright (c) 2013-2025 Ghost Foundation - Released under the MIT license. Ghost and the Ghost Logo are trademarks of Ghost Foundation Ltd. Please see our trademark policy for info on acceptable usage.