▶️Quickstart / Setup
How to get up and running with the template stage project.
Last updated
How to get up and running with the template stage project.
Last updated
There are two main ways to develop a stage: locally or within a GitHub Codespace.
You should see this output on the command line, and this in a browser window.
You can skip ahead to the other sections in this guide for a while to work on it, or go straight to the rest of the setup. To run in chat, you'll have to instead run:
When ready to push, for the build to submit to Chub, you'll have to add an API key.
By default, when you run a stage in development, rather than waiting for a chat that may not exist it uses the test runner, which is in src/TestRunner.tsx. There are some example tests in the template, and the initialization data it uses is in src/assets/test-init.json.
If you'd rather edit with a live chat, it's most straightforward when running locally. Just run with the command:
Once you're running locally, go to "Chat Settings", hit 'Staging URL', and put in the URL and refresh the page. This will only work with the localhost version of the URL.
For your changes to push to Chub, you'll need to add a token to the secrets of your GitHub project. From the main page of your new project, go to 'Settings' -> 'Secrets and Variables' -> 'Actions' -> 'Repository secrets' -> 'New Repository Secret'.
Add the token with the name 'CHUB_AUTH_TOKEN'. You can get a write token from https://chub.ai/my_stages?active=tokens.
The next time you push, a stage project will be created in Chub and show up in your stages. To make this happen without a push, go to 'Actions' and rerun the failed push workflow:
If you find the heavy comments in the template annoying, in any *.ts* file use the regex
in anything that supports regex editing (Intellij, et cetera) and delete them all.
In any *.yaml, use: