plugins/openresty-vhosts/commands

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

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

  openresty:labels:add)
    cmd-openresty-labels-add "$@"
    ;;

  openresty:labels:remove)
    cmd-openresty-labels-remove "$@"
    ;;

  openresty:labels:show)
    cmd-openresty-labels-show "$@"
    ;;

  *)
    exit "$DOKKU_NOT_IMPLEMENTED_EXIT"
    ;;
esac
feat: add openresty proxy implementation This plugin is mostly compatible with the nginx plugin, but runs the proxy within a docker container. Users do not have direct access to add custom openresty configuration at this time, but instead receive the ability to setup automatic ssl on first request via letsencrypt integration. 2023-08-01 02:16:11 -04:00			`#!/usr/bin/env bash`
refactor: rename functions to be plural They are plural for the scheduler-k3s plugin. 2025-11-16 18:12:28 -05:00			`[[ " openresty:help openresty:labels:add openresty:labels:remove openresty:labels:show help " == " $1 " ]] \|\| exit "$DOKKU_NOT_IMPLEMENTED_EXIT"`
feat: add openresty proxy implementation This plugin is mostly compatible with the nginx plugin, but runs the proxy within a docker container. Users do not have direct access to add custom openresty configuration at this time, but instead receive the ability to setup automatic ssl on first request via letsencrypt integration. 2023-08-01 02:16:11 -04:00			`source "$PLUGIN_AVAILABLE_PATH/openresty-vhosts/help-functions"`
refactor: split out label subcommands into distinct commands 2025-11-16 16:30:56 -05:00			`source "$PLUGIN_AVAILABLE_PATH/openresty-vhosts/command-functions"`
feat: add openresty proxy implementation This plugin is mostly compatible with the nginx plugin, but runs the proxy within a docker container. Users do not have direct access to add custom openresty configuration at this time, but instead receive the ability to setup automatic ssl on first request via letsencrypt integration. 2023-08-01 02:16:11 -04:00			`set -eo pipefail`
			`[[ $DOKKU_TRACE ]] && set -x`

			`case "$1" in`
			`help \| openresty:help)`
			`cmd-openresty-help "$@"`
			`;;`

refactor: rename functions to be plural They are plural for the scheduler-k3s plugin. 2025-11-16 18:12:28 -05:00			`openresty:labels:add)`
			`cmd-openresty-labels-add "$@"`
refactor: split out label subcommands into distinct commands 2025-11-16 16:30:56 -05:00			`;;`

refactor: rename functions to be plural They are plural for the scheduler-k3s plugin. 2025-11-16 18:12:28 -05:00			`openresty:labels:remove)`
			`cmd-openresty-labels-remove "$@"`
refactor: split out label subcommands into distinct commands 2025-11-16 16:30:56 -05:00			`;;`

refactor: rename functions to be plural They are plural for the scheduler-k3s plugin. 2025-11-16 18:12:28 -05:00			`openresty:labels:show)`
			`cmd-openresty-labels-show "$@"`
refactor: split out label subcommands into distinct commands 2025-11-16 16:30:56 -05:00			`;;`

feat: add openresty proxy implementation This plugin is mostly compatible with the nginx plugin, but runs the proxy within a docker container. Users do not have direct access to add custom openresty configuration at this time, but instead receive the ability to setup automatic ssl on first request via letsencrypt integration. 2023-08-01 02:16:11 -04:00			`*)`
			`exit "$DOKKU_NOT_IMPLEMENTED_EXIT"`
			`;;`
			`esac`