-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
locations of things #5
Comments
I think we can go with either. Having both was (I think) an attempt to make sure that experiments with ansible not over-writing germinator deployments. I think that was @bredelings . So, I don't think we need both. We might want to maintain the convention of having a dir for synth and another dir for serving the tree. but i don't care what the names are. EDIT: just noting that I wrote this before seeing Ben's post. so it is a response to Karen. |
From conversation on gitter, going to keep everything that we download (+install) from github in |
I think I left my comment without refreshing this page. I like both @bredelings suggestion about separating the c++ apps and also @mtholder structure on nexttree. On dev / production,
on nexttree,
Directory structures within |
Sounds good. If you want to move the git source for cpp apps under |
Looking at locations of where things get cloned / downloaded / installed / etc:
$HOME/repo
directory where we clone + install peyotl, ws-wrapper, opentree, phylesystem, amendments, collections; created in functions.sh and used in install-api.sh and install-common.sh$HOME/Applications
directory where we clone and install otcetera, restbed in install-otcetera.shIs this the same structure that we want going forward with ansible?
The text was updated successfully, but these errors were encountered: