From 06476f7ad2e18ff43ae2f925987e908464096f06 Mon Sep 17 00:00:00 2001 From: muxator Date: Fri, 24 Aug 2018 01:26:05 +0200 Subject: [PATCH] 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. --- settings.json.template | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/settings.json.template b/settings.json.template index 684e9d598..11d1debc9 100644 --- a/settings.json.template +++ b/settings.json.template @@ -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" },