Skip to content
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

Open
kcranston opened this issue Jun 1, 2020 · 5 comments
Open

locations of things #5

kcranston opened this issue Jun 1, 2020 · 5 comments

Comments

@kcranston
Copy link
Member

Looking at locations of where things get cloned / downloaded / installed / etc:

Is this the same structure that we want going forward with ansible?

@bredelings
Copy link
Contributor

bredelings commented Jun 1, 2020 via email

@mtholder
Copy link
Member

mtholder commented Jun 1, 2020

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.
On "nexttree" we (read "@mtholder") had a different directory for building the synth tree and a different one for serving the tree. Neither were repo or Applications)

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.

@kcranston
Copy link
Member Author

From conversation on gitter, going to keep everything that we download (+install) from github in repos. The build dir(s) should not be inside the source code repos (either sister to, or in a separate parent, perhaps Applications).

@kcranston
Copy link
Member Author

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, ls $HOME:

cpp_apps - otcetera and restbed, each in their own dir with the subdirectories suggested by @bredelings
repos - all other repos
downloads - destination for various wgets
unpacked - destination for unpacked tarballs

on nexttree, ls $HOME:

synth_dir - everything related to building the synthetic tree
ws_dir - everything related to serving the tree

Directory structures within ws_dir will be same / similar to $HOME on dev/prod.

@bredelings
Copy link
Contributor

Sounds good. If you want to move the git source for cpp apps under repo, so that ls otcetera would show build/ and local/ that seems equally good. Or I guess you could make a symlink from otcetera/git to repos/otcetera....... OK, enough bike-shedding!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants