As there is no officially supported integration that really works I've prepared a simple CI/CD pipelines to cover vercel's preview and production environments.
<name>_dev
,<name>_stage
,<name>
To reflect vercel's environments. (They will also be separated on tinybird so in case of mistake you will not nuke production env)
Below this readme you will find ready workflows taht you need to deploy inside .github/workflows/
Learn more about Using secrets in github actions here.
GH secrets naming:
TB_STAGE_TOKEN
- Tinybird stage (<name>_stage
) workspace admin token
TB_ADMIN_TOKEN
- Tinybird production (<name>
) workspace admin token
IMPORTANT Replace <tb_project_dir> with your repo's tinybird directory path inside workflow files!
Option 1
Use your Tinybird CLI to work with dev (<name>_dev
) enviroment.
Option 2
When your are using UI to manage your tinybird instances you need to make tb pull
using tinybird cli to pull config files to your repository code.