Recommended practices for version control of config & custom auth #134

rowanhill opened this Issue Nov 18, 2013 · 0 comments


None yet
2 participants

rowanhill commented Nov 18, 2013


I'd like to do a few things with IODocs:

  1. Keep my json config files in source control
  2. Extend IODocs with a custom authentication mechanism (although I haven't written this yet)
  3. Easily keep up to date with improvements to this repo

At the moment, I have a repo with my config files in, with this repo as a submodule, and a small script to copy the files into the submodule when we run the IODocs app. This way we can easily update the submodule to pull in upstream changes without any messy merges. I don't think this will work very well when I come to write the custom auth mechanism, though.

So, I have two questions:

  1. Is there a recommended way of adding new auth mechanisms?
  2. Is there a better way of keeping my config whilst also receiving upstream changes?

Perhaps I should just clone this repo, make my changes, and merge from upstream? I'd rather not have to make changes to a repository just to use it, though.

Any advice appreciated!

@mtougeron mtougeron added auth labels Mar 26, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment