mirror of
https://github.com/d0zingcat/ghost-docker.git
synced 2026-05-13 15:09:34 +00:00
Simplify TB initial setup
no ref - By outputting the tokens in the format the `.env` file expects this greatly simplifies the initial setup by just makign it copy -> paste able - This will mean users don't need to load up the UI and copy/paste tokens at all and can do the whole setup (after they've signed up for TB) from the CLI
This commit is contained in:
@@ -6,12 +6,8 @@ Note: Currently Traffic Analytics features are behind a feature flag. For now, y
|
||||
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. Find your workspace's ID and events API endpoint: `docker compose run --rm tinybird-login tb --cloud info`
|
||||
1. Copy the value of "api", and add it to your `.env` file as `TINYBIRD_API_URL`. You can also find this value in your Tinybird Workspace's UI.
|
||||
1. Copy the value of "workspace_id", and add it to your `.env` file as `TINYBIRD_WORKSPACE_ID`
|
||||
1. Using the UI link from the previous step, open your workspace and click on *Tokens* in the left hand menu
|
||||
1. Copy your Tinybird "Workspace admin token" and add it to your `.env` file as `TINYBIRD_ADMIN_TOKEN`
|
||||
1. Copy your Tinybird `tracker` token and add it to your `.env` file as `TINYBIRD_TRACKER_TOKEN`
|
||||
1. Run `docker compose --profile=analytics 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
|
||||
1. At this point, everything should be working. You can test it's working by visiting your site's homepage, then checking the Stats page in Ghost Admin — you should see a view recorded.
|
||||
|
||||
Reference in New Issue
Block a user