Configuration: audit, clean, extend & improve
See original GitHub issueAs the refactor of config is done, and we’ve had a chance to use it for a little while, it would be good to revisit it again before the end of alpha. There are a couple of outstanding todos from #6982 plus I’d like to look at what config options we provide. Do they make sense? Are there some things which should not be config? Some things which should be and aren’t?
Things that definitely need review/audit:
- IMPORTANT: reconsider new config options from https://github.com/TryGhost/Ghost/pull/7929⭐️ ⭐️ ⭐️ ⭐️ ⭐️
- [ ] our use of paths in overrides.jsonneed’s more context- [ ] revisit paths likeneed’s more context/ghost/
and/ghost/api/<verison>
- our use of the
url
and related config options likeforceAdminSSL
(+ redirect option).- Required: support for adminUrl like we use on Ghost(Pro)
- Drop handling on Ghost(Pro)
- should route keywords be configuration? See https://github.com/TryGhost/Ghost/issues/8492
- configuration options for caching (raised in #7273)
- documentation & implementation of
compress
config differs (docs saycompress
implementation looks forserver.compress
). - imageRelPath https://github.com/TryGhost/Ghost/blob/master/core/server/config/utils.js#L19
- revisit all checks against config.get(‘env’) and see if they can be moved to configuration E.g. https://github.com/TryGhost/Ghost/pull/7544/files
~- [ ] catch the error thrown from nconf, and rethrow it in a prettyier, clearer, more Ghost-like~ fashion (see https://github.com/TryGhost/Ghost/issues/7488#issuecomment-276090407):
/Users/hannah/Ghost/node_modules/nconf/lib/nconf/stores/file.js:160
throw new Error("Error parsing your configuration file: [" + this.file + ']: ' + ex.message);
^
Error: Error parsing your configuration file: [/Users/hannah/Ghost/config.development.json]: Unexpected token d
...
Anyone who has something else they’d like reconsidered, please add a comment!
TODOs from #6982:
- revisit the use of keys with nconf’s
.file()
- remove the default database config, add
client
to theconfig.development.json
file
TODO’s from #7692
- remove config.set('theme:…`), look at the TODO written in the PR
Issue fixes
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Perform Configuration Audit - VMware Docs
The configuration audit API performs licensing checks on all the objects in the system and reports various violations. It ignores the violations ...
Read more >Adjusting Event Log Size and Retention Settings
To prevent overwrites, you can increase the maximum size of the event logs and set retention method for these logs to “Overwrite events...
Read more >Configure Audit Logs using the Properties File
Use the properties file to configure your Confluent Platform audit logs. ... For improved security, send audit logs to a different cluster.
Read more >Oracle Database Auditing: Performance Guidelines
This paper helps you estimate impact on application throughput and CPU usage when enabling auditing policies in the Oracle database. To understand the...
Read more >Auditing - Product Documentation | ServiceNow
Track record changes on auditing-enabled tables. By default, the system tracks changes to the incident, change, and problem tables, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Couple of notes / thoughts as I’m moving around:
times
key needs to be changed to something likescheduling
as it is part of that aspect of Ghost.minifyAssets
needs revisiting as it is doesn’t do anything reallyinternalApps
should possibly be apps.internal?I would like to make it possible at some point soon (not necessarily for 1.0) to change the path for where themes are stored - this would be the only available customisation, no adapters.we will keep it in mind👍 Thank you!
I agree to the custom theme and image paths. We can add this later as a none breaking change and support both notations. You either specify a
contentPath
or override the content path by e.g.contentImagePath
- if only one option is specified, it’s possible to detect that.