plugins/nginx-vhosts/subcommands/validate

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

cmd-nginx-validate-config "$@"
feat: Pull invalid nginx configuration when the nginx configs fail to validate - expose an nginx:validate command that can be used to show validation information - properly reference the invalid nginx config, rather than tell the user that another app's nginx config is invalid when deploying their own app - allow a user to cleanup bad nginx config files out of band when they are blocking a deploy _without_ requiring knowing where that nginx config is Note that this may have issues with generated nginx.conf files that depend on other apps or other parts of the nginx config. For now, this is acceptable, though it is something that needs to be field tested. Closes #3162 2018-12-30 08:33:53 -05: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`
feat: Pull invalid nginx configuration when the nginx configs fail to validate - expose an nginx:validate command that can be used to show validation information - properly reference the invalid nginx config, rather than tell the user that another app's nginx config is invalid when deploying their own app - allow a user to cleanup bad nginx config files out of band when they are blocking a deploy _without_ requiring knowing where that nginx config is Note that this may have issues with generated nginx.conf files that depend on other apps or other parts of the nginx config. For now, this is acceptable, though it is something that needs to be field tested. Closes #3162 2018-12-30 08:33:53 -05:00			`source "$PLUGIN_CORE_AVAILABLE_PATH/common/functions"`
refactor: deprecate nginx:validate The command function move was to fix circular import issues... 2020-02-18 17:12:33 -05:00			`source "$PLUGIN_AVAILABLE_PATH/nginx-vhosts/command-functions"`
feat: Pull invalid nginx configuration when the nginx configs fail to validate - expose an nginx:validate command that can be used to show validation information - properly reference the invalid nginx config, rather than tell the user that another app's nginx config is invalid when deploying their own app - allow a user to cleanup bad nginx config files out of band when they are blocking a deploy _without_ requiring knowing where that nginx config is Note that this may have issues with generated nginx.conf files that depend on other apps or other parts of the nginx config. For now, this is acceptable, though it is something that needs to be field tested. Closes #3162 2018-12-30 08:33:53 -05:00
refactor: deprecate nginx:validate The command function move was to fix circular import issues... 2020-02-18 17:12:33 -05:00			`cmd-nginx-validate-config "$@"`