fcakyon/claude-codex-settings / plugins/polar-skills/skills/polar-local-environment
polar-local-environment
VerifiedThis skill should be used when setting up or managing Polar local development environment with Docker.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.3 KB |
| rules/manage-instances.md | markdown | 2.7 KB |
| rules/payment-testing.md | markdown | 6.2 KB |
| rules/service-architecture.md | markdown | 3.1 KB |
| rules/shell-and-workflows.md | markdown | 2.6 KB |
| rules/start-environment.md | markdown | 3.0 KB |
| rules/stop-environment.md | markdown | 1.6 KB |
| rules/troubleshooting.md | markdown | 6.0 KB |
| rules/view-logs.md | markdown | 1.9 KB |
rules/start-environment.md
View on GitHub---
title: Starting the Local Environment
category: Operations
tags: docker, start, development
---
# Starting the Local Environment
`dev docker up` starts shared infra (if it isn't already running) plus this
worktree's app stack. It **defaults to detached** (`-d` is on by default), so
plain `dev docker up` returns once containers are created.
## Basic commands
**Start in background (the default):**
```bash
dev docker up -d
```
**Start and block until app services are healthy:**
```bash
dev docker up -d --wait
```
`--wait` returns only once api answers `/healthz` and web responds. Prefer it in
scripts and tooling so "up finished" means "actually serving" rather than "the
container was created" — on first boot the app keeps compiling and migrating for
a while after the container starts.
**Start in the foreground and stream logs:**
```bash
dev docker up --no-detach
```
Shared infra still starts detached; only the app stack is attached, so Ctrl+C
stops the app stack.
**Start specific services:**
```bash
dev docker up -d api # api (+ shared infra)
dev docker up -d web # web (+ shared infra)
dev docker up -d api worker # api and worker
```
## Options
| Flag | Description |
| ----------------- | ---------------------------------------------------- |
| `-d` / `--detach` | Detached / background (default) |
| `--no-detach` | Foreground; stream app logs until you stop it |
| `--wait` | Block until app services are healthy (detached only) |
| `-b` / `--build` | Rebuild images before starting |
| `--pull` | Refresh base images before building (see below) |
| `--monitoring` | Include Prometheus and Grafana in shared infra |
| `-i N` | Target instance N explicitly (usually auto-detected) |
## Rebuilding with fresh bases
```bash
dev docker up -b --pull -d
```
`-b` rebuilds the images, and `--pull` refreshes the base images first. Use
`--pull` after a `.python-version` bump or when a rebuild alone still boots the
old interpreter — a cached `FROM` layer can otherwise pin you to a stale base.
See troubleshooting for the "No interpreter found for Python X" symptom.
## First-time startup
First run is slow because it does real work inside the containers:
1. Build the api/web images
2. `uv sync` (api/worker) and `pnpm install` (web) — several minutes
3. Bootstrap the per-instance DB and MinIO buckets
4. Run migrations and load seed data
5. Services become healthy
`dev docker up -d --wait` is the cleanest way to wait this out.
## Finding the URLs
Ports are per-instance, so don't assume 3000/8000. Ask:
```bash
dev docker ports # human-readable
dev docker ports --json # for tooling
```
For instance 0 the app is at http://localhost:3000 (web) and
http://localhost:8000 (api, docs at `/docs`). MinIO exposes ports 9000 (API)
and 9001 (console) on localhost; db and redis have no host port — reach them
with `dev docker exec <service> ...`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |