vers

usage

# start postgres container for tests
yarn pg:test-container:start

# lint, typecheck, unit tests
yarn lint
yarn typecheck
yarn test

# build, dev, test specific project
yarn build:<project>
yarn dev:<project>
yarn test:<project>

# run graphql types codegen
yarn codegen:graphql

# run panda css codegen
yarn codegen:styles

# regenerate tsconfig's paths after adding/renaming a package
yarn codegen:paths

# spin up full backend via docker compose
yarn stack start

# rebuild full backend
yarn stack build

# generate and run our postgres migrations
yarn pg:migrations-generate
yarn pg:migrations-run:dev

# update our postgres migrations after updating drizzle
yarn pg:migrations-update

# install e2e browsers
yarn playwright install

# run all e2e tests
yarn e2e

# stop full backend
yarn stack stop

# stop specific service
yarn stack stop:<service>

generating keys for JWT signing & verification

# generate rs256 private key
openssl genpkey -algorithm RSA -pkeyopt rsa_keygen_bits:2048 | openssl pkcs8 -topk8 -nocrypt > privkey.pem

# extract pubkey
openssl pkey -pubout -in privkey.pem -out pubkey.crt

creating a new fly deployment

cd projects/<project-name>

# initial deployment
fly launch

# attach our service to our postgres instance
fly pg attach vers-pg --database-name=vers

# create secrets if needed
fly secrets set SESSION_SECRET=$(openssl rand -hex 32) HONEYPOT_SECRET=$(openssl rand -hex 32)

# setting jwt signing secrets
fly secrets set --app=vers-service-api JWT_SIGNING_PRIVKEY=- < privkey.pem

development with cursor

all of our cursor rules are in the .cursor directory.

consider prompting an agentic composer like:

We are working on a new feature for the <project-name> project.
At a high level, we want to <describe-feature>.

Read @__initialization.mdc and confirm you're ready to proceed.