docker/docs/_build/python-3.14.3-alpine/plugins/checks/commands

#!/usr/bin/env bash
[[ " help checks:help " == *" $1 "* ]] || exit "$DOKKU_NOT_IMPLEMENTED_EXIT"
source "$PLUGIN_AVAILABLE_PATH/checks/help-functions"
set -eo pipefail
[[ $DOKKU_TRACE ]] && set -x

case "$1" in
  help | checks:help)
    cmd-checks-help "$@"
    ;;

  *)
    exit "$DOKKU_NOT_IMPLEMENTED_EXIT"
    ;;

esac
nginx-vhosts rewrite 2016-02-14 18:43:40 -08:00			`#!/usr/bin/env bash`
subcommand restructure and bashstyle refactor. closes #1579 2016-03-01 13:26:35 -08:00			`[[ " help checks:help " == " $1 " ]] \|\| exit "$DOKKU_NOT_IMPLEMENTED_EXIT"`
refactor: standardize help generation 2020-02-10 00:37:00 -05:00			`source "$PLUGIN_AVAILABLE_PATH/checks/help-functions"`
tests: run mvdan/shfmt on test runs While I do not agree with _every_ style change, this will force Dokku to have consistent formatting across all shell scripts, which is arguably a Good Thing™. The command used to reprocess everything is: ```shell shfmt -l -bn -ci -i 2 -w . ``` 2019-01-07 01:04:17 -05:00			`set -eo pipefail`
			`[[ $DOKKU_TRACE ]] && set -x`
nginx-vhosts rewrite 2016-02-14 18:43:40 -08:00
			`case "$1" in`
Collapse help into expandable command topics 2016-03-15 20:03:35 -07:00			`help \| checks:help)`
refactor: standardize command naming This standardization makes it somewhat easier to read stacktraces as the command names are all uniform, so it will be slightly easier to scan trace output. 2020-02-09 22:41:39 -05:00			`cmd-checks-help "$@"`
nginx-vhosts rewrite 2016-02-14 18:43:40 -08:00			`;;`

			`*)`
cleanup shellcheck SC2086 2016-02-22 10:16:57 -08:00			`exit "$DOKKU_NOT_IMPLEMENTED_EXIT"`
nginx-vhosts rewrite 2016-02-14 18:43:40 -08:00			`;;`

			`esac`