Build image from compose while CI is disabled
This commit is contained in:
+15
-2
@@ -1,8 +1,21 @@
|
|||||||
services:
|
services:
|
||||||
ksan-dev:
|
ksan-dev:
|
||||||
# Built and pushed by CI; deployed by tag, never by :latest, so a rollback
|
# Normally built and pushed by CI; deployed by tag, never by :latest, so a
|
||||||
# is a re-run of `up -d` with an older tag instead of a rebuild.
|
# rollback is a re-run of `up -d` with an older tag instead of a rebuild.
|
||||||
image: ${IMAGE_NAME:-git.ksan.dev/ksan/ksan.dev}:${IMAGE_TAG:-latest}
|
image: ${IMAGE_NAME:-git.ksan.dev/ksan/ksan.dev}:${IMAGE_TAG:-latest}
|
||||||
|
# TEMPORARY — while the Gitea workflows sit at .disabled, nothing builds or
|
||||||
|
# pushes an image, so the VPS builds from its own checkout instead:
|
||||||
|
#
|
||||||
|
# git pull && docker compose up -d --build
|
||||||
|
#
|
||||||
|
# PLANS_PAGES must be in the VPS .env for this to work; it is a build arg
|
||||||
|
# (the codes are baked in via generateStaticParams), not a runtime var.
|
||||||
|
# Remove this block when CI is re-enabled — a registry image is the only
|
||||||
|
# thing `deploy.sh` and `rollback.sh` can deploy by tag.
|
||||||
|
build:
|
||||||
|
context: .
|
||||||
|
args:
|
||||||
|
PLANS_PAGES: ${PLANS_PAGES}
|
||||||
container_name: ksan-dev
|
container_name: ksan-dev
|
||||||
restart: unless-stopped
|
restart: unless-stopped
|
||||||
env_file:
|
env_file:
|
||||||
|
|||||||
Reference in New Issue
Block a user