mattermost/server/config.mk
Jesse Hallam 4c25d03f67
Automate setup-go-work as a dependency for Make targets (#35476)
* automate setup-go-work

It's all to easy to forget to `make setup-go-work`, only to run into mysterious build failures. Let's default to doing this automatically, unless `SKIP_SETUP_GO_WORK` is true (or the legacy `IGNORE_GO_WORK_IF_EXISTS`, which was oddly named, since we can't actually ignore it.)

* Make setup-go-work recipe fail-fast with set -e
2026-03-20 19:12:20 +00:00

35 lines
1.1 KiB
Makefile

# Do not modify this file, if you want to configure your own environment copy
# this file in config.override.mk and modify that file, or defining environment
# variables using the same names found here.
# Enable services to be run in docker.
#
# Possible options: postgres, minio, inbucket, openldap, dejavu,
# keycloak, elasticsearch, opensearch, redis, prometheus,
# grafana, loki and otel-collector.
#
# Must be space separated names.
#
# Example: postgres elasticsearch
ENABLED_DOCKER_SERVICES ?= postgres inbucket redis prometheus grafana loki otel-collector
# Disable entirely the use of docker
MM_NO_DOCKER ?= false
# Run the server in the background
RUN_SERVER_IN_BACKGROUND ?= true
# Data loaded by default in openldap when container starts.
#
# Possible options: test or qa
LDAP_DATA ?= test
# Mock the CWS.
MM_ENABLE_CWS_MOCK ?= false
# Skip running setup-go-work automatically.
# IGNORE_GO_WORK_IF_EXISTS is supported for backwards compatibility.
ifdef IGNORE_GO_WORK_IF_EXISTS
SKIP_SETUP_GO_WORK ?= $(IGNORE_GO_WORK_IF_EXISTS)
endif
SKIP_SETUP_GO_WORK ?= false