plugins/nginx-vhosts/proxy-enable

#!/usr/bin/env bash
set -eo pipefail
[[ $DOKKU_TRACE ]] && set -x
source "$PLUGIN_CORE_AVAILABLE_PATH/common/functions"

trigger-nginx-vhosts-proxy-enable() {
  declare desc="enable nginx proxy"
  declare trigger="proxy-enable"
  declare APP="$1"

  if [[ "$(plugn trigger proxy-type "$APP")" == "nginx" ]]; then
    plugn trigger domains-enable "$APP" "false"
    plugn trigger app-restart "$APP"
  fi
}

trigger-nginx-vhosts-proxy-enable "$@"
nginx-vhosts rewrite 2016-02-14 18:43:40 -08:00			`#!/usr/bin/env bash`
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			`source "$PLUGIN_CORE_AVAILABLE_PATH/common/functions"`

refactor: standardize trigger code 2020-02-10 02:40:59 -05:00			`trigger-nginx-vhosts-proxy-enable() {`
use declare for description variable 2016-03-08 15:30:34 -05:00			`declare desc="enable nginx proxy"`
refactor: standardize trigger code 2020-02-10 02:40:59 -05:00			`declare trigger="proxy-enable"`
			`declare APP="$1"`
nginx-vhosts rewrite 2016-02-14 18:43:40 -08:00
refactor: rewrite proxy plugin in golang 2020-02-22 06:35:30 -05:00			`if [[ "$(plugn trigger proxy-type "$APP")" == "nginx" ]]; then`
refactor: move domain manipulation into triggers This allows other plugins to avoid understanding the underlying details of how domains might be integrated with. 2020-05-06 00:16:51 -04:00			`plugn trigger domains-enable "$APP" "false"`
			`plugn trigger app-restart "$APP"`
nginx-vhosts rewrite 2016-02-14 18:43:40 -08:00			`fi`
			`}`

refactor: standardize trigger code 2020-02-10 02:40:59 -05:00			`trigger-nginx-vhosts-proxy-enable "$@"`