refs TryGhost/Team#535 We want to ensure that a site will always have a default value of `'#15171A'` for the accent_color setting. Since the boot process changed we have three cases to account for: 1. Setting does not exist 2. Setting exists with no value 3. Setting exists with a value It is only in the case of 2. that we want the migration to update the database with a default value. In the case of 3. the site owner has already set a value, which we do not want to override. In the case of 1. the setting will be created (and populated with default value) from the default-settings.json file, by the populateDefaults method called from the settings service We also update the accent_color setting to include a non-empty validation, to ensure that the setting will always have a value, as sites before 4.x may have an empty accent_color, we must update the importer to set the default value if one is not present. Otherwise we would run into validation errors and even if we didn't would have an invalid database state. |
||
---|---|---|
.github | ||
content | ||
core | ||
test | ||
.editorconfig | ||
.eslintignore | ||
.eslintrc.json | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
.npmignore | ||
config.development.json | ||
ghost.js | ||
Gruntfile.js | ||
index.js | ||
LICENSE | ||
MigratorConfig.js | ||
package.json | ||
PRIVACY.md | ||
README.md | ||
renovate.json | ||
SECURITY.md | ||
yarn.lock |
Ghost.org |
Features |
Showcase |
Forum |
Docs |
Contributing |
Twitter
Love open source? We're hiring Node.js Engineers to work on Ghost full-time
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 cause 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!
If you prefer to run on your own infrastructure, we also offer official 1-off installs and managed support and maintenance plans via Ghost(Valet) - which can save a substantial amount of developer time and resources.
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/customise core files we recommend following our full development setup guides: Contributor Guide | Developer Setup | Admin Client Dev Guide
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-2021 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.