@@ -40,8 +40,8 @@ default).
4040
4141.. code-block :: console
4242
43- $ shpc config set module_sys: tcl
44- $ shpc config set module_sys: lmod # default
43+ $ shpc config set module_sys tcl
44+ $ shpc config set module_sys lmod # default
4545
4646
4747 You can then easily install, load, and use modules:
@@ -81,8 +81,8 @@ software, which is typicall lmod or tcl. Here is how to change from the default
8181
8282.. code-block :: console
8383
84- $ shpc config set module_sys: tcl
85- $ shpc config set module_sys: lmod # this is the default, which we change back to!
84+ $ shpc config set module_sys tcl
85+ $ shpc config set module_sys lmod # this is the default, which we change back to!
8686
8787
8888 Once you have the correct module software indicated, try installing a container:
@@ -315,10 +315,10 @@ your install:
315315.. code-block :: console
316316
317317 # an absolute path
318- $ shpc config set module_base: /opt/lmod/modules
318+ $ shpc config set module_base /opt/lmod/modules
319319
320320 # or a path relative to a variable location remember to escape the "$"
321- $ shpc config set module_base: \$root_dir/modules
321+ $ shpc config set module_base \$root_dir/modules
322322
323323
324324 This directory will be the base where lua files are added, and containers are stored
@@ -351,7 +351,7 @@ different. For example:
351351.. code-block :: console
352352
353353 $ mkdir -p /tmp/containers
354- $ shpc config set container_base: /tmp/containers
354+ $ shpc config set container_base /tmp/containers
355355
356356
357357 The same hierarchy will be preserved as to not put all containers in the same
@@ -464,7 +464,7 @@ or you can set the global variable to what you want to use (it defaults to lmod)
464464
465465.. code-block :: console
466466
467- $ shpc config set module_sys: tcl
467+ $ shpc config set module_sys tcl
468468
469469
470470 The command line argument, if provided, always over-rides the default.
@@ -488,7 +488,7 @@ or for a global setting:
488488
489489.. code-block :: console
490490
491- $ shpc config set container_tech: podman
491+ $ shpc config set container_tech podman
492492
493493
494494 If you would like support for a different container technology that has not been
@@ -520,6 +520,26 @@ Container-specific scripts you'll want to include in the container.yaml are desc
520520 # use for singularity aliases
521521 singularity : singularity.sh
522522
523+ Since these are nested values, to get the current value you can use a ``: `` to separate
524+ the fields, e.g.,:
525+
526+ .. code-block :: console
527+
528+ $ shpc config get wrapper_scripts:enabled
529+ wrapper_scripts:enabled False
530+
531+ And if you want to change the default, just add another level:
532+
533+ .. code-block :: console
534+
535+ $ shpc config set wrapper_scripts:enabled true
536+ Updated wrapper_scripts:enabled to be true
537+
538+ And don't forget you can manually update the file in an editor:
539+
540+ .. code-block :: console
541+
542+ $ shpc config edit
523543
524544 Since different container technologies might expose different environment variables (e.g., ``SINGULARITY_OPTS `` vs ``PODMAN_OPTS ``)
525545they are organized above based on the container technology. If you want to customize the wrapper script, simply replace the relative paths
@@ -688,7 +708,7 @@ If you always want to install to an (existing) named view, simply set the ``defa
688708
689709.. code-block :: console
690710
691- $ shpc config set default_view: mpi
711+ $ shpc config set default_view mpi
692712
693713 You should obviously create the view first or you'll get an error message that it does not exist!
694714When you have a default view set, any install that you do will install to the module base and also your view.
@@ -717,7 +737,7 @@ for a short period of time to install to it. If you want to disable this, then j
717737
718738.. code-block :: console
719739
720- $ shpc config set default_view: null
740+ $ shpc config set default_view null
721741
722742 And note you can also ask to install to a view "one off":
723743
@@ -908,10 +928,10 @@ The following example shows changing the default module_base path from the insta
908928.. code-block :: console
909929
910930 # an absolute path
911- $ shpc config set module_base: /opt/lmod/modules
931+ $ shpc config set module_base /opt/lmod/modules
912932
913933 # or a path relative to the install directory, remember to escape the "$"
914- $ shpc config set module_base: \$install_dir/modules
934+ $ shpc config set module_base \$install_dir/modules
915935
916936
917937 And then to get values:
@@ -925,8 +945,8 @@ And to add and remove a value to a list:
925945
926946.. code-block :: console
927947
928- $ shpc config add registry: /tmp/registry
929- $ shpc config remove registry: /tmp/registry
948+ $ shpc config add registry /tmp/registry
949+ $ shpc config remove registry /tmp/registry
930950
931951
932952 You can also open the config in the editor defined in settings at ``config_editor ``
@@ -1081,7 +1101,7 @@ Note that you can also set the namespace as any other setting:
10811101
10821102.. code-block :: console
10831103
1084- $ shpc config set namespace: ghcr.io/autamus
1104+ $ shpc config set namespace ghcr.io/autamus
10851105
10861106 Namespaces currently work with:
10871107
0 commit comments