plugins/00_dokku-standard/commands

#!/usr/bin/env bash
[[ " help help:help cleanup:help url:help urls:help version:help " == *" $1 "* ]] || exit "$DOKKU_NOT_IMPLEMENTED_EXIT"
source "$PLUGIN_AVAILABLE_PATH/00_dokku-standard/help-functions"
set -eo pipefail
[[ $DOKKU_TRACE ]] && set -x

case "$1" in
  help | cleanup:help | url:help | urls:help | version:help)
    cmd-standard-help "$@"
    ;;

  *)
    exit "$DOKKU_NOT_IMPLEMENTED_EXIT"
    ;;

esac
normalizing shebang and bash options. also added long-term fix for bootstrap instructions 2013-10-29 17:13:02 -05:00			`#!/usr/bin/env bash`
refactor: move run command to it's own plugin 2021-07-27 01:37:51 -04:00			`[[ " help help:help cleanup:help url:help urls:help version:help " == " $1 " ]] \|\| exit "$DOKKU_NOT_IMPLEMENTED_EXIT"`
refactor: standardize help generation 2020-02-10 00:37:00 -05:00			`source "$PLUGIN_AVAILABLE_PATH/00_dokku-standard/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`
subcommand restructure and bashstyle refactor. closes #1579 2016-03-01 13:26:35 -08:00
			`case "$1" in`
refactor: move run command to it's own plugin 2021-07-27 01:37:51 -04:00			`help \| cleanup:help \| url:help \| urls:help \| version:help)`
refactor: standardize help generation 2020-02-10 00:37:00 -05:00			`cmd-standard-help "$@"`
adding some basic help, also as another example of using plugin hooks 2013-06-30 15:51:41 -05:00			`;;`
initial attempt at plugins 2013-06-30 10:37:32 -05:00
Output error message when a command is not found. Closes #778 Plugins with commands will need to implement a catch-all command that exits with the `DOKKU_NOT_IMPLEMENTED_EXIT`` code (10). This signals to dokku that a given plugin has indeed not executed anything for a plugin (which may not always be the case). Using plugins that do not implement this pattern will result in those plugins silencing the error message. 2014-11-23 18:09:11 -05:00			`*)`
cleanup shellcheck SC2086 2016-02-22 10:16:57 -08:00			`exit "$DOKKU_NOT_IMPLEMENTED_EXIT"`
Output error message when a command is not found. Closes #778 Plugins with commands will need to implement a catch-all command that exits with the `DOKKU_NOT_IMPLEMENTED_EXIT`` code (10). This signals to dokku that a given plugin has indeed not executed anything for a plugin (which may not always be the case). Using plugins that do not implement this pattern will result in those plugins silencing the error message. 2014-11-23 18:09:11 -05:00			`;;`

Remove redundant command from dokku-standard plugin 2013-08-18 14:27:38 +02:00			`esac`