feat(web): show git SHA in footer for post-deploy verification
Dockerfile takes SOURCE_COMMIT as a build arg and bakes it into the image as GIT_COMMIT. Coolify sets SOURCE_COMMIT on every deploy, so the value in the footer changes with each successful push → build. ARG is placed after COPY . so only a thin final layer rebuilds when the SHA changes; pip install stays cached. Outside Coolify the default is "dev" and the footer renders "build dev". Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
81d6b65eae
commit
0144cb2844
5 changed files with 23 additions and 2 deletions
|
|
@ -8,6 +8,13 @@ RUN pip install --no-cache-dir -r requirements.txt
|
|||
|
||||
COPY . .
|
||||
|
||||
# Stamp the image with the git SHA so the web footer can show which commit is
|
||||
# live. Coolify passes SOURCE_COMMIT as a build arg on every deploy; outside
|
||||
# Coolify the ARG defaults to "dev". Placed after COPY so only this thin layer
|
||||
# rebuilds when the SHA changes — pip install stays cached.
|
||||
ARG SOURCE_COMMIT=dev
|
||||
ENV GIT_COMMIT=${SOURCE_COMMIT}
|
||||
|
||||
EXPOSE 8000
|
||||
|
||||
HEALTHCHECK --interval=30s --timeout=5s --start-period=10s --retries=3 \
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue