settings.json.template: reorganized dbSetting section to be more comment-friendly
It is better to keep the dirtyDB settings together, so they can be commented out via a /* ... */. Nested comments blocks would crash the application on start, because they are syntactically incorrect. Let's reduce this possibility, promoting an easier standard.pull/3473/head
parent
d1481041c2
commit
06476f7ad2
|
@ -56,18 +56,16 @@
|
|||
* You shouldn't use "dirty" for for anything else than testing or
|
||||
* development.
|
||||
*
|
||||
* For a complete list of the supported drivers, please consult:
|
||||
*
|
||||
* Database specific settings are dependent on dbType, and go in dbSettings.
|
||||
* Remember that since Etherpad 1.6.0 you can also store these informations in
|
||||
* credentials.json.
|
||||
*
|
||||
* For a complete list of the supported drivers, please refer to:
|
||||
* https://www.npmjs.com/package/ueberdb2
|
||||
*/
|
||||
|
||||
"dbType" : "dirty",
|
||||
|
||||
/*
|
||||
* Database specific settings (dependent on dbType).
|
||||
*
|
||||
* Remember that since Etherpad 1.6.0 you can also store these informations in
|
||||
* credentials.json.
|
||||
*/
|
||||
"dbSettings" : {
|
||||
"filename" : "var/dirty.db"
|
||||
},
|
||||
|
|
Loading…
Reference in New Issue