ellisonbg
commented
7 years ago What I found in using this repo was that I needed some things to be outside the repo and not version controlled:
- My server config
- Security stuff
- The Makefile that I customized for my deployment.
Because of this I have found it most useful to have an outer repo (separate from this one) that includes this repo as a submodule. That outer repo has the host config, host vars, security stuff and a Makefile that copies those things into place into the ansible setup and then runs ansible.
Part of this is that I need an easy way to completely update and reset the ansible config separately from my deployment specific details. Because of that I think it is best for us to keep the Makefile out of this repo. Some options:
- Create a cookiecutter that has that outer stuff and includes the ansible deployment stuff as a git clone or submodule
- Create a separate repo that does the same thing.
I almost think that the cookie cutter idea would work well in this case though...
Thoughts?
On Sat, Jan 14, 2017 at 11:17 AM, Carol Willing notifications@github.com wrote:
@ellisonbg https://github.com/ellisonbg's enhancements with Makefile and consolidating the configuration parameters to essentially one file greatly simplifies the installation process.
- Migrate Makefile
- Migrate example configuration file for testing
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jupyterhub/jupyterhub-deploy-teaching/issues/70, or mute the thread https://github.com/notifications/unsubscribe-auth/AABr0LNcHkwvA_H8NYSzgd70WvjDTG7Pks5rSR9ngaJpZM4Ljtve .
-- Brian E. Granger Associate Professor of Physics and Data Science Cal Poly State University, San Luis Obispo @ellisonbg on Twitter and GitHub bgranger@calpoly.edu and ellisonbg@gmail.com
willingc
zonca
@ellisonbg's enhancements with Makefile and consolidating the configuration parameters to essentially one file greatly simplifies the installation process.
Makefile