-
Notifications
You must be signed in to change notification settings - Fork 41
add a guide for creating custom uenv environments #206
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
Conversation
This comment has been minimized.
This comment has been minimized.
|
preview available: https://docs.tds.cscs.ch/206 |
This comment has been minimized.
This comment has been minimized.
|
preview available: https://docs.tds.cscs.ch/206 |
|
|
||
| ## Custom environments | ||
|
|
||
| It is common practice to add `module` commands to `~.bashrc`, for example |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would add somewhere that this practice of customization of programming environment through .bashrc is discouraged by CSCS. It is better to keep .bashrc "clean" and do all customizations in the separate script like presented below.
This comment has been minimized.
This comment has been minimized.
|
preview available: https://docs.tds.cscs.ch/206 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
preview available: https://docs.tds.cscs.ch/206 |
This comment has been minimized.
This comment has been minimized.
|
preview available: https://docs.tds.cscs.ch/206 |
1 similar comment
|
preview available: https://docs.tds.cscs.ch/206 |
Co-authored-by: Rocco Meli <[email protected]>
|
preview available: https://docs.tds.cscs.ch/206 |
In response to https://jira.cscs.ch/browse/SD-66316
https://docs.tds.cscs.ch/206/software/uenv/#custom-environments