ssh -t terminal.shop -- "archbtw"
-t
forces pty allocation, --
tells ssh to forward the following commands to
the application.
- install bun https://bun.sh/
- go here
- make sure Account Resources is limited to
terminal
instead ofAll accounts
and create the api token. - save it to a
.env
file like this
CLOUDFLARE_API_TOKEN=xxx
you can setup aws credentials however you want but if you are on the terminal team this is how you do it
- place this in
~/.aws/config
[sso-session terminal]
sso_start_url = https://terminaldotshop.awsapps.com/start
sso_region = us-east-2
[profile terminal-dev]
sso_session = terminal
sso_account_id = 058264103289
sso_role_name = AdministratorAccess
region = us-east-2
[profile terminal-production]
sso_session = terminal
sso_account_id = 211125775473
sso_role_name = AdministratorAccess
region = us-east-2
- need to login once a day with
bun sso
in root
if you're only working on frontend you don't need to bring up the whole system - you can create a shell that's linked to the dev
environment.
cd go
sst shell --stage=dev
- this connects you to the dev environment and opens a bash shellgo run ./cmd/cli
- this will run the cli
note - this loads dev secrets into your environment. most of them aren't sensitive but if you are streaming you should avoid logging your env.
if you're working on the full system you can do
sst dev
in root to bring up everything