Create a virtual enviroment and install tinybird
python3 -m venv .venv
source .venv/bin/activate
pip install tinybird-cliAuthenticate using your admin token from your workspace (twenty_analytics_cli_playground)
tb auth -i
** List of available regions:
[1] us-east4 (gcp) (https://app.us-east.tinybird.co)
[2] europe-west3 (gcp) (https://app.tinybird.co/gcp/europe-west3)
[3] us-east-1 (aws) (https://app.tinybird.co/aws/us-east-1)
[4] us-west-2 (aws) (https://app.tinybird.co/aws/us-west-2)
[5] eu-central-1 (aws) (https://app.tinybird.co/aws/eu-central-1) <- this
[0] Cancel
Use region [5]:
Copy the "admin your@email" token from from https://app.tinybird.co/tokens and paste it here: <pasted Token>
** Auth successful!
** Configuration written to .tinyb file, consider adding it to .gitignoreYou can also log in using your twenty_analytics_token without passing into the interactive mode:
tb auth --token <your twenty_analytics_token >
** Auth successful!
** Configuration written to .tinyb file, consider adding it to .gitignoreTo sync your changes to Tinybird use:
tb push --force --push-depsTo pull data from Tinybird use:
tb pullThings I learned:
- When creating Materialied Views think about populating it first using the files from the fixtures
- When pushing your pipes prefer to push one by one so you can have more coherent error messages
- The Include files will be nodes that will be added at the start of your node in Tinybird UI
- It's best to stick only with only the CLI or the UI when developping in Tinybird
- If you want to format the data us the tb fmt command, perhaps we can add it to the linter in a next pull request.