plugins/scheduler-docker-local/commands

#!/usr/bin/env bash
set -eo pipefail
[[ $DOKKU_TRACE ]] && set -x
source "$PLUGIN_AVAILABLE_PATH/scheduler-docker-local/help-functions"

case "$1" in
  help | scheduler-docker-local:help)
    cmd-scheduler-docker-local-help "$@"
    ;;

  *)
    exit "$DOKKU_NOT_IMPLEMENTED_EXIT"
    ;;

esac
feat: allow disabling chown for persistent storage in scheduler-docker-local Some systems - such as a mounted read-only CIFS filesystem - do not fully support chown, and chowning should be considered optional for cases when the host os has already taken care of permissioning. This commit allows users to disable chown by setting a property on the scheduler-docker-local plugin. 2018-08-01 02:00:32 -04: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`
refactor: standardize help generation 2020-02-10 00:37:00 -05:00			`source "$PLUGIN_AVAILABLE_PATH/scheduler-docker-local/help-functions"`
feat: allow disabling chown for persistent storage in scheduler-docker-local Some systems - such as a mounted read-only CIFS filesystem - do not fully support chown, and chowning should be considered optional for cases when the host os has already taken care of permissioning. This commit allows users to disable chown by setting a property on the scheduler-docker-local plugin. 2018-08-01 02:00:32 -04:00
			`case "$1" in`
			`help \| scheduler-docker-local:help)`
			`cmd-scheduler-docker-local-help "$@"`
			`;;`

			`*)`
			`exit "$DOKKU_NOT_IMPLEMENTED_EXIT"`
			`;;`

			`esac`