#git bot interface

History of !configfiles

• It is recommended to store local configuration data in a file which is not tracked by git, but certain deployment scenarios(such as Heroku) may require otherwise. See https://gist.github.com/1423106 for some ideas
  By EugeneKay at 2012-08-26 08:41:13
• the recommended way is to modify your application so that tracked/untracked config are stored in different files. See https://gist.github.com/1423106 for some approaches
  By canton7 at 2012-08-24 16:10:57
• Best practice is to store an example config file and then copy+modify it when you install your app. If your config file must be tracked by git to deploy(eg, Heroku), see https://gist.github.com/1423106 for some workarounds
  By EugeneKay at 2012-08-14 21:48:24
• the recommended way is to change your application so that you can (perhaps optionally) store site-specific configuration/data in separate files, then keep those files out of version control. Still, see https://gist.github.com/1423106 for ways people have worked around the problem.
  By SethRobertson at 2011-12-13 02:11:28
• the recommended way is to change your application so that you can (perhaps optionally) store site-specific configuration/data in separate files, then keep those files out of version control.
  By jast at 2011-12-09 00:35:50