diff options
author | Malfurious <m@lfurio.us> | 2023-08-19 03:57:03 -0400 |
---|---|---|
committer | Malfurious <m@lfurio.us> | 2023-08-19 03:57:03 -0400 |
commit | 65d21438ef6921353288a13aba7d2075182300d6 (patch) | |
tree | cf7d5b2be1f510dd4feb68d7f8f58427b72b9de6 /acid | |
parent | 56c438a250de7b7acec1f0d2f5aade60ccc370f8 (diff) | |
download | cychedelic-65d21438ef6921353288a13aba7d2075182300d6.tar.gz cychedelic-65d21438ef6921353288a13aba7d2075182300d6.zip |
acid: Touch up some documentation
Signed-off-by: Malfurious <m@lfurio.us>
Diffstat (limited to 'acid')
-rw-r--r-- | acid/config.sh | 2 | ||||
-rwxr-xr-x | acid/cyche-build | 6 |
2 files changed, 4 insertions, 4 deletions
diff --git a/acid/config.sh b/acid/config.sh index 857173e..ff44998 100644 --- a/acid/config.sh +++ b/acid/config.sh @@ -23,7 +23,7 @@ CYCHE_SERVICES=( # Latest tag matching glob refs/tags/<shell-*-wildcard> # # <name> is arbitrary, but must be unique. It is used to name various - # docker entities and must contain only "a-z", dashes, or underscores. + # docker entities and must contain only "a-z", "0-9", dashes, or underscores. # The source used to fetch updates for cychedelic itself should be the first # in the list. As just mentioned, it can be named anything, but "cychedelic" diff --git a/acid/cyche-build b/acid/cyche-build index 8363f60..310a087 100755 --- a/acid/cyche-build +++ b/acid/cyche-build @@ -7,13 +7,13 @@ # # In the typical case, this is a straightforward process and `docker compose up` # can properly recreate/start containers for the guest service. However, when -# rebuilding cychedelic itself, --self must be given, to instruct this file to -# modify its behavior to support self-upgrade of the running compose service. +# rebuilding cychedelic itself, `--self` must be given, which modifies this +# script to support self-upgrade of the running compose service. # # In `--self` mode, we prepare and start the cychedelic service under an # alternate project name each time, before taking down the existing (old) # services. This is necessary because running `docker compose up` terminates -# old containers before starting new one. Termination of the ACID service +# old containers before starting new ones. Termination of the ACID service # interrupts the `compose up` process before it can start the replacements. # Normally, `docker compose down` is then not needed. # |