plugins/nginx-vhosts/commands

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

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

  *)
    exit "$DOKKU_NOT_IMPLEMENTED_EXIT"
    ;;

esac
Import ssl certificates Also ensures output is stored in proper tls directory Closes #518 2014-11-22 16:04:05 -05:00			`#!/usr/bin/env bash`
subcommand restructure and bashstyle refactor. closes #1579 2016-03-01 13:26:35 -08:00			`[[ " help nginx:help " == " $1 " ]] \|\| exit "$DOKKU_NOT_IMPLEMENTED_EXIT"`
refactor: standardize help generation 2020-02-10 00:37:00 -05:00			`source "$PLUGIN_AVAILABLE_PATH/nginx-vhosts/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`
rebuild nginx config on domain change 2014-12-12 17:53:30 -08:00
Import ssl certificates Also ensures output is stored in proper tls directory Closes #518 2014-11-22 16:04:05 -05:00			`case "$1" in`
Add PLUGIN:help command to each plugin 2014-11-22 17:52:46 -05:00			`help \| nginx: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-nginx-vhosts-help "$@"`
refactor: move nginx:help to internal-functions 2017-02-20 22:35:52 -07:00			`;;`
Import ssl certificates Also ensures output is stored in proper tls directory Closes #518 2014-11-22 16:04:05 -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"`
refactor: move nginx:help to internal-functions 2017-02-20 22:35:52 -07: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
Import ssl certificates Also ensures output is stored in proper tls directory Closes #518 2014-11-22 16:04:05 -05:00			`esac`