TryGhost/Ghost
1
0
Fork 0
mirror of https://github.com/TryGhost/Ghost.git synced 2024-12-23 02:41:50 +03:00
Code Issues Projects Releases Wiki Activity
c09a81aabe
Ghost/core/shared/config/env/config.testing.json

58 lines
1.3 KiB
JSON
Raw Normal View History

✨ 🔦 add nconf files refs #6982 - add defaults.json - add overrides.json - add env specific default values - add nconf wrapper in /config - add config utils in /config/utils.js [ci skip]
2016-09-13 18:20:44 +03:00
{
"url": "http://127.0.0.1:2369",
"database": {
🎨 updates for database configuration (#7975) * 🎨 update configuration files: database refs #7488 - no default database configuration - production: default is MySQL * 🎨 add transport stdout to production for now refs #7488 - production will log to stdout and file for now - to reduce the risk of confusing users - users would not see any stdout and they don't know that Ghost logs into file only in production * 🎨 sanitize database properties refs #7488
2017-02-11 21:02:12 +03:00
"client": "sqlite3",
✨ 🔦 add nconf files refs #6982 - add defaults.json - add overrides.json - add env specific default values - add nconf wrapper in /config - add config utils in /config/utils.js [ci skip]
2016-09-13 18:20:44 +03:00
"connection": {
Changed DB path for SQLite tests no issue - previously for SQLite tests we were pointing to a DB file within the content/data folder, which would be stored on the filesystem - by pointing this file to be under `/tmp`, the file is stored in memory and should be a lot quicker to access - this works great for me! - 2x faster test suite for SQLite - however, Windows doesn't have a `/tmp` folder so we need to rewrite that part to replace with `os.tmpdir()`
2021-02-19 10:53:42 +03:00
"filename": "/tmp/ghost-test.db"
✨ 🔦 add nconf files refs #6982 - add defaults.json - add overrides.json - add env specific default values - add nconf wrapper in /config - add config utils in /config/utils.js [ci skip]
2016-09-13 18:20:44 +03:00
},
🎨 updates for database configuration (#7975) * 🎨 update configuration files: database refs #7488 - no default database configuration - production: default is MySQL * 🎨 add transport stdout to production for now refs #7488 - production will log to stdout and file for now - to reduce the risk of confusing users - users would not see any stdout and they don't know that Ghost logs into file only in production * 🎨 sanitize database properties refs #7488
2017-02-11 21:02:12 +03:00
"useNullAsDefault": true,
"debug": false
✨ 🔦 add nconf files refs #6982 - add defaults.json - add overrides.json - add env specific default values - add nconf wrapper in /config - add config utils in /config/utils.js [ci skip]
2016-09-13 18:20:44 +03:00
},
"server": {
"port": 2369
},
🎨 configurable logging with bunyan (#7431) - 🛠 add bunyan and prettyjson, remove morgan - ✨ add logging module - GhostLogger class that handles setup of bunyan - PrettyStream for stdout - ✨ config for logging - @TODO: testing level fatal? - ✨ log each request via GhostLogger (express middleware) - @TODO: add errors to output - 🔥 remove errors.updateActiveTheme - we can read the value from config - 🔥 remove 15 helper functions in core/server/errors/index.js - all these functions get replaced by modules: 1. logging 2. error middleware handling for html/json 3. error creation (which will be part of PR #7477) - ✨ add express error handler for html/json - one true error handler for express responses - contains still some TODO's, but they are not high priority for first implementation/integration - this middleware only takes responsibility of either rendering html responses or return json error responses - 🎨 use new express error handler in middleware/index - 404 and 500 handling - 🎨 return error instead of error message in permissions/index.js - the rule for error handling should be: if you call a unit, this unit should return a custom Ghost error - 🎨 wrap serve static module - rule: if you call a module/unit, you should always wrap this error - it's always the same rule - so the caller never has to worry about what comes back - it's always a clear error instance - in this case: we return our notfounderror if serve static does not find the resource - this avoid having checks everywhere - 🎨 replace usages of errors/index.js functions and adapt tests - use logging.error, logging.warn - make tests green - remove some usages of logging and throwing api errors -> because when a request is involved, logging happens automatically - 🐛 return errorDetails to Ghost-Admin - errorDetails is used for Theme error handling - 🎨 use 500er error for theme is missing error in theme-handler - 🎨 extend file rotation to 1w
2016-10-04 18:33:43 +03:00
"logging": {
"level": "fatal"
Replace memory spam prevention with brute-express (#7579) no issue - removes count from user checks model - uses brute express brute with brute-knex adaptor to store persisted data on spam prevention - implement brute force protection for password/token exchange, password resets and private blogging
2016-11-08 14:33:19 +03:00
},
"spam": {
"user_login": {
"minWait": 600000,
"maxWait": 604800000,
"freeRetries": 3
},
"user_reset": {
"minWait": 3600000,
"maxWait": 3600000,
"lifetime": 3600,
"freeRetries": 4
},
"global_reset": {
"minWait": 3600000,
"maxWait": 3600000,
"lifetime": 3600,
"freeRetries":4
},
"global_block": {
"minWait": 3600000,
"maxWait": 3600000,
"lifetime": 3600,
"freeRetries":4
},
"private_block": {
"minWait": 3600000,
"maxWait": 3600000,
"lifetime": 3600,
"freeRetries":99
}
🎨 😎 config env usages (#7929) refs #7488 - remove all ugly env checks - rather use config properties - replace process.env.NODE_ENV by config.get('env')
2017-02-03 21:25:39 +03:00
},
"privacy": {
"useTinfoil": true,
"useStructuredData": true
},
Changed to use different fixtures during testing - this keeps production and test fixtures separate, so that changing the prod fixtures doesn't change the shape of our tests. - we may still want to test that the production fixtures do what we expect, but that can be handled in a separate integration test, by specifically setting the fixture path
2021-11-16 16:03:20 +03:00
"useMinFiles": false,
"paths": {
Introduced booting from fixture url cache in test environment refs https://github.com/TryGhost/Toolbox/issues/135 - To be able to reliably start ghost instance without a frontend the process needs access to urls/resources caches - Storing the configuration in "paths" for now as there's no better place for it untill we are able to mock the content folder in pre-boot
2021-11-17 19:05:17 +03:00
"fixtures": "test/utils/fixtures/fixtures",
"urlCache": "test/utils/fixtures/urls"
Changed to use different fixtures during testing - this keeps production and test fixtures separate, so that changing the prod fixtures doesn't change the shape of our tests. - we may still want to test that the production fixtures do what we expect, but that can be handled in a separate integration test, by specifically setting the fixture path
2021-11-16 16:03:20 +03:00
}
✨ 🔦 add nconf files refs #6982 - add defaults.json - add overrides.json - add env specific default values - add nconf wrapper in /config - add config utils in /config/utils.js [ci skip]
2016-09-13 18:20:44 +03:00
}
Reference in New Issue Copy Permalink