# How do I setup Tinybird analytics with Ghost Portainer Compose?

**URL:** <https://forum.ghost.org/t/how-do-i-setup-tinybird-analytics-with-ghost-portainer-compose/59342>\
**Category:** Developer help\
**Created:** [August 6, 2025, 3:18am UTC](https://forum.ghost.org/t/how-do-i-setup-tinybird-analytics-with-ghost-portainer-compose/59342 "2025-08-06T03:18:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![joshuniverse](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/joshuniverse/32/30150_2.png) [@joshuniverse](https://forum.ghost.org/u/joshuniverse)\
**Post date:** [August 6, 2025, 3:18am UTC](https://forum.ghost.org/t/how-do-i-setup-tinybird-analytics-with-ghost-portainer-compose/59342/1 "2025-08-06T03:18:48Z")

</div>

It seems that there is a new analytics feature in Ghost 6 which integrates with Tinybird analytics. How do we setup the configuration for a Ghost self-hosted instance with docker compose/portainer?

---

<div class="post-metadata">

**Author:** ![jannis](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/jannis/32/39718_2.png) [@jannis](https://forum.ghost.org/u/jannis)\
**Post date:** [August 6, 2025, 5:42am UTC](https://forum.ghost.org/t/how-do-i-setup-tinybird-analytics-with-ghost-portainer-compose/59342/2 "2025-08-06T05:42:47Z")

</div>

> [@joshuniverse](#):
>
> with docker compose

The instructions for that here here:

> **[How To Install Ghost With Docker (preview) - Ghost Developer Docs](https://docs.ghost.org/install/docker#enabling-web-analytics)**
>
> Preview our new batteries-included tools for self-hosting Ghost using Docker Compose.

I don’t think Portainer has a way to run `docker compose` commands. Been a while since I have used it, so happy to be corrected.

What these commands do is configure your Tinybird workspace and create tokens. You could run these commands locally on your machine, and then use the tokens it generated in Portainer.

If Ghost changes something in the Tinybird pipelines, you’d have to run the `tinybird-deploy` locally again.
