d34884fc6d
ref https://linear.app/tryghost/issue/MOM-48 This required some structural changes to our NestJS setup so that we can mount it on multiple parts of the Ghost express app. We've used the RouterModule to allow adding submodules that are mounted on different paths, and we've had to be explicit about the base path for each module. We've also had to switch back to using the Module decorator, because RouterModule doesn't work with DynamicModule definitions. Now that the NestJS app has knowledge of the full path, we need to "reset" the url & baseUrl when passing the request into NestJS so that it can correctly match the path. This is probably needed for the frontend too, for subdirs, but that causes further issues - as this in prototype stage, we'll look later Another issue is that NestJS replaces the express app instance with its own, which isn't an issue for the Admin API (though we've fixed it anyway for consistency), but did cause problems for the frontend, because the express app is where view engine and directory information is stored. The fix for this is to save a reference to the original ghost express application, and reattach it to the request if it is not handled by Nest Now that we have the Nest app mounted on the frontend, we're able to have it handle the /.well-known/webfinger route with a proper controller, which is nice! |
||
|---|---|---|
| .github | ||
| .vscode | ||
| apps | ||
| ghost | ||
| .editorconfig | ||
| .envrc | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| flake.lock | ||
| flake.nix | ||
| 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
We'd like to extend 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
You can find answers to a huge variety of questions, along with a large community of helpful developers over on the Ghost forum - replies are generally very quick. Ghost(Pro) customers also 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 blog — or you can always follow us on Twitter, if you prefer your updates bite-sized and facetious. 🎷🐢
Copyright & license
Copyright (c) 2013-2023 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.