From a924fa976a637dee05c191d85378ce99996dd57b Mon Sep 17 00:00:00 2001 From: James Loh Date: Mon, 23 Jun 2025 14:23:45 +1000 Subject: [PATCH] Pinned Ghost + Tinybird Sync container to same image Closes https://linear.app/ghost/issue/ENG-2414 - These two containers must run the same version of Ghost since the TB container uses assets from the Ghost container - If the two are out of sync we'd be updating or migrating Tinybird to a different set of APIs than what Ghost is expecting which could break things --- .env.example | 3 +++ compose.yml | 6 ++++-- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/.env.example b/.env.example index 829ef64..9db0f33 100644 --- a/.env.example +++ b/.env.example @@ -1,5 +1,8 @@ # COMPOSE_PROFILES=analytics,activitypub +# Which Ghost version to run +GHOST_VERSION=5-alpine + DOMAIN=example.com # Location to store uploaded data diff --git a/compose.yml b/compose.yml index cfb2957..733d6b5 100644 --- a/compose.yml +++ b/compose.yml @@ -17,7 +17,8 @@ services: - ghost_network ghost: - image: ghost:5-alpine + # Do not alter this without updating the Tinybird Sync container as well + image: ghost:${GHOST_VERSION:-5-alpine} restart: always expose: - "2368" @@ -116,7 +117,8 @@ services: # Suporting Services tinybird-sync: - image: ghost:5-alpine + # Do not alter this without updating the Ghost container as well + image: ghost:${GHOST_VERSION:-5-alpine} command: > sh -c " if [ -d /var/lib/ghost/current/core/server/data/tinybird ]; then