What problem does this solve?
Proposed Solution
Current:
$ cat /opt/shpc/singularity-hpc/shpc/settings.yml | grep HOME
module_base: $HOME/shpc/modules
container_base: $HOME/shpc/containers
wrapper_base: $HOME/shpc/wrappers
views_base: $HOME/shpc/views
Suggest the following updates to /opt/shpc/singularity-hpc/shpc/settings.yml:
module_base: apps/shpc/modules
container_base: apps/shpc/containers
wrapper_base: apps/shpc/wrappers
views_base: apps/shpc/views
Area of BioShell
VM / cloud environment setup
Alternatives Considered
Within shelley, adding a check that the paths are accessible by all users, and running shpc config set key value, where for example, key = module_base and value = apps/shpc/modules
What problem does this solve?
$HOME/shpcby defaultshelley) and shpc artefacts will be accessible by all users/apps/Modules/modulefileswill resolve correctly across users~/shpcafter module removal Sydney-Informatics-Hub/shelley#37Proposed Solution
Current:
$ cat /opt/shpc/singularity-hpc/shpc/settings.yml | grep HOMESuggest the following updates to
/opt/shpc/singularity-hpc/shpc/settings.yml:Area of BioShell
VM / cloud environment setup
Alternatives Considered
Within
shelley, adding a check that the paths are accessible by all users, and runningshpc config set key value, where for example, key = module_base and value = apps/shpc/modules