Local development

Application Makefile targets may require registry, tenancy, environment, and version variables. Inspect the target and its included Makefiles before running it locally. Use your development environment’s configuration and the values in the P2P GitHub variables.

Export the variables required by your target in the current shell. For example, replace the placeholders below with your development configuration:

export BASE_DOMAIN="dev.example.com"
export REPO_PATH="/path/to/app"
export REGION="europe-west2"
export REGISTRY="europe-west2-docker.pkg.dev/PROJECT/REPOSITORY"
export VERSION="$(git rev-parse --short HEAD)"
export TENANT_NAME="engineering"

These values are examples, not a complete environment for every Makefile. Targets that include p2p.mk may derive additional values or require P2P_* inputs. Check your application’s Makefile for its variable names and local development targets.

Authenticate to the development registry before running targets that push images. For targets that access Kubernetes, configure cluster access first. Run build and test targets from the application directory; deployment and promotion targets can change remote environments or registry contents.