Home → Suggestions →

Allow to split config file ( config.user.d/*.json )

• Edit

Lionel

03 Apr, 2014 09:16 AM

Thanks again for the software.

My config.user.json becomes quite big on a dev server hosting many web apps. What's about having the possibility, for the [files] section, to read individual .json files which would we located in a subdir config.user.d/ (ie the debian way for complex conf). In that scenario, the globals and badges section would remain in config.user.json, and users could add their file entry either in config.user.json or in config.user.d/

1. Support Staff 1 Posted by potsky on 03 Apr, 2014 10:07 AM

   

   Nice idea!

   Then you could define includes in the main config.user.json.

   I create a ticket for this feature in the next release !

   • Edit

2. Support Staff 2 Posted by potsky on 11 Oct, 2014 06:46 PM

   

   Hi Lionel,

   sorry for the long delay... This feature will be released in version 1.3 in a few days...

   Keep in touch!

   • Edit

3. 3 Posted by Lionel on 13 Oct, 2014 12:41 PM

   

   Glad to see it! This new feature will be really welcome.

   One (dumb) question: why do you use the message "prepare to publish on master or beta" for nearly all your commits? It doesn't sound very meaningful...

   Cheez'

   • Edit

4. Support Staff 4 Posted by potsky on 13 Oct, 2014 12:51 PM

   

   Hi Lionel,

   in fact, this feature will be published this afternoon I think in version 1.2.2 :-)

   My workflow is automated with Grunt. If you take a look on the branches in GitHub :

   • master : the Pimp My Log tool
   • beta : the Pimp My Log tool in beta version. I test this version on several installations before releasing in master
   • dev : the Pimp My Log tool run development
   • jekyll : the Pimp My Log website in dev
   • gh-pages : the Pimp My Log website in production hosted on GitHub

   I never work in master or beta, only in dev.

   I never work in gh-pages, only in jekyll.

   When I want to publish in beta for staging, I just have to execute from the dev branch : grunt build install

   When I want to publish in master for production, I just have to execute from the dev branch : grunt build install-production

   And I have nothing else to do. My grunt tasks will check a lot of thing to avoid bugs in production and they automatically push on Github all modifications.

   I really like to work with Grunt because I permanently work in a week on about 20 distinct projects and it is important to automate a lot of thing to save time and avoid bugs.

   But you are right... commit messages are absolutely awful !

   • Edit

5. 5 Posted by Lionel on 15 Oct, 2014 01:14 PM

   

   Excellent!

   A little suggestion (or question): how are the items ordered in the final list (between those defined by the various files)? I couldn't manage to find the logic behind it (and I recognize I was too lazy to look at your code........)

   • Edit

6. Support Staff 6 Posted by potsky on 15 Oct, 2014 02:16 PM

   

   Hi Lionel,

   items are ordered as they appear :

   1. You have first files defined in your user configuration file
      
   2. Then the directory is parsed recursively and files are added when they are found

   Do you want me to add an option SORT_LOG_FILES with 2 possible values :

   • default : today behaviour
   • byname : order files by their name so the displayed list will be alpha sorted

   ?

   • Edit

7. Support Staff 7 Posted by potsky on 15 Oct, 2014 03:13 PM

   

   Ok, done with these 5 values for the next release :

   • default
   • display-asc
   • display-insensitive
   • display-desc
   • display-insensitive-desc
   • Edit

8. 8 Posted by Lionel on 16 Oct, 2014 02:34 PM

   

   Terrible.
   If PimpMyLog (and its author) could also make coffee and solve my bugs, that would be terrific.
   ....sorry for the spam on your website.... :)

   • Edit

9. potsky closed this discussion on 13 Nov, 2014 03:53 PM.