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

Shared collections #155

Open
ars-vita opened this issue Feb 21, 2018 · 1 comment
Open

Shared collections #155

ars-vita opened this issue Feb 21, 2018 · 1 comment

Comments

@ars-vita
Copy link

It could be a good idea to have shared collections (along with the private ones) in order to enable users having standard tool chains.

I have in mind the following setup. When user just starts his/her terminal, a default (shared) collection is getting loaded, which consists only of the shared modules. In this way, a user can do whatever he/she wants with the environment being confident that anytime he/she can restore it to the initial state using:

$ module restore

Along with the default (shared) collection an administrator creates other shared collections that represent standard tool chains that user can always rely on.

For now I am using the following workaround. I create collections and move them to the shared modulefiles folder under superuser ownership. Each user can create a link in his own .module directory pointing to the shared collection. This is maybe not the best way to manage shared collections but as a workaround it works.

@xdelaruelle xdelaruelle added this to the 4.3 milestone Feb 23, 2018
@cmarqu
Copy link
Contributor

cmarqu commented Apr 25, 2018

Nice idea, I would use this feature. Let me just suggest the term "baseline" for it (as in https://en.wikipedia.org/wiki/Baseline_(configuration_management)).

@xdelaruelle xdelaruelle removed this from the 4.3 milestone Jan 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants