From b76e2a9ef4bfe2e39f0917f0fe7710815bf9b89e Mon Sep 17 00:00:00 2001 From: James Loh Date: Tue, 15 Jul 2025 11:39:42 +1000 Subject: [PATCH] Simplify initial setup by not include `--profile` arg no ref - As Chris notes this isn't actually required when doing the initial setup/mentioning the specific container you want to deploy - This standardises us in just doing the `--rm run` command for all of them to keep everything nice and neat --- TINYBIRD.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/TINYBIRD.md b/TINYBIRD.md index 2140b38..874e27f 100644 --- a/TINYBIRD.md +++ b/TINYBIRD.md @@ -4,9 +4,9 @@ Note: Currently Traffic Analytics features are behind a feature flag. For now, y 1. Create a Tinybird account and a Tinybird workspace at [tinybird.co](https://auth.tinybird.co/login). You can select any cloud/region you choose. 1. Run `docker compose run --rm tinybird-login` to login to your Tinybird account following the steps given -1. Run `docker compose --profile=analytics up tinybird-sync`. This will copy the Tinybird files from the Ghost container into a shared volume. The service should log "Tinybird files synced into shared volume.", then exit. -1. Run `docker compose --profile=analytics up tinybird-deploy` and wait for the service to exit successfully. This will create your Tinybird datasources, pipes and API endpoints. It may take a minute or two to complete the first time. You should see "Deployment #1 is live!" in your terminal before the service exits. -1. Run `docker compose --profile=analytics run --rm tinybird-login get-tokens` +1. Run `docker compose run --rm tinybird-sync`. This will copy the Tinybird files from the Ghost container into a shared volume. The service should log "Tinybird files synced into shared volume.", then exit. +1. Run `docker compose run --rm tinybird-deploy` and wait for the service to exit successfully. This will create your Tinybird datasources, pipes and API endpoints. It may take a minute or two to complete the first time. You should see "Deployment #1 is live!" in your terminal before the service exits. +1. Run `docker compose run --rm tinybird-login get-tokens` 1. Copy and paste the values from the previous step into your `.env` file 1. Run `docker compose --profile=analytics up -d` to start all services in the background 1. Add `analytics` to `COMPOSE_PROFILES=` in the top of your `.env` file to automatically include the `analytics` profile when running `docker compose` commands