#Quick Start

Get from zero to production in an hour.

#Local Development

Make sure Docker Desktop is running, then:

# 1. Create your project (installs deps, builds libs, generates configs,
#    starts local infra, and creates the initial database migration)
npx @tsdevstack/cli init --template fullstack-auth

# 2. Enter the project
cd <your-project-name>

# 3. Start development
npm run dev

That's it. Your microservices are running locally with Kong gateway, PostgreSQL, and Redis.

If Docker wasn't running during step 1, start it and run npx tsdevstack sync from the project directory before npm run dev.

#What you'll have

After running these commands, you get:

Each service you create gets:

• Hot reload on code changes
• Structured JSON logging
• Automatic health checks at /health
• Prometheus metrics at /metrics
• OpenAPI spec generation

As you develop, add more apps with npx tsdevstack add-service and run npx tsdevstack sync to update configs.

See Running Locally for details.

#Deploy to Cloud

#1. Create Cloud Account

Set up your cloud provider account and credentials. Choose one:

#2. Configure Credentials

Add your credentials to the provider-specific file in .tsdevstack/:

• GCP: .credentials.gcp.json
• AWS: .credentials.aws.json
• Azure: .credentials.azure.json

See the provider guide above for the exact format.

#3. Initialize Cloud

npx tsdevstack cloud:init --gcp   # or --aws or --azure

This validates credentials, enables APIs, and grants required permissions automatically.

#4. Initialize Infrastructure

npx tsdevstack infra:init --env dev

Creates the Terraform state backend and the infrastructure config schema for your provider.

#5. Configure Domains

If you have frontend apps, add their domains to .tsdevstack/infrastructure.json:

{
  "$schema": "./infrastructure.schema.json",
  "version": "1.0.0",
  "dev": {
    "frontend": {
      "domain": "example.com"
    }
  }
}

#6. Deploy

npx tsdevstack infra:deploy --env dev

#7. Configure DNS

The deploy command outputs:

• Load Balancer IP
• SSL validation records

Add these to your domain provider:

• A records pointing to the LB IP
• SSL validation CNAME records

See Domain Setup for details.

#8. Wait for SSL

SSL certificates provision in 30-60 minutes. Then you're live.

#CI/CD

Automate deployments with GitHub Actions. You can deploy from local CLI, CI/CD, or both.

npx tsdevstack infra:init-ci --github

Then add environment-prefixed secrets to your repository (Settings > Secrets and variables > Actions). The secrets depend on your provider:

Replace DEV with STAGING, PROD, etc. for each environment.

If your project uses private npm packages, also add a single NPM_TOKEN repo secret (global, not per-env) and create an .npmrc at project root with ${NPM_TOKEN} interpolation — tsdevstack auto-detects and threads it through generated workflows and docker builds. See Private npm packages.

See CI/CD Setup and the provider-specific CI/CD pages for details.