Local development

The basalt CLI runs Postgres, the gateway, auth and storage in containers on your machine, so you can build offline and test migrations before they reach production.

Install the CLI

macOS
Linux
npm

brew install basalt/tap/basalt

curl -fsSL https://get.basalt.run/cli | sh

npm install basalt --save-dev

Start the stack

basalt init
basalt start

The first start pulls about 1.2 GB of images. Later starts take a few seconds.

Service	Local URL
API gateway	`http://localhost:54400`
Studio	`http://localhost:54403`
Postgres	`postgresql://postgres:postgres@localhost:54402/postgres`
Mail catcher	`http://localhost:54404`

Write a migration

basalt migration new add_notes_table

Edit the new file under basalt/migrations/, then apply it with basalt db reset.

Why does `db reset` drop my data?

Reset rebuilds the database from migrations and the seed file, so the local database always matches what production will get. Put fixture rows in basalt/seed.sql.

Is this helpful?