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/view-logs.md
View on GitHub---
title: Viewing Service Logs
category: Debugging
tags: logs, debugging, troubleshooting
---
# Viewing Service Logs
`dev docker logs` **follows by default** (`-f` is on). It auto-routes by service
name: app services (api/worker/web) come from this instance's `polar-app-<N>`
project, and infra services (db/redis/minio/...) from `polar-shared`.
## Commands
**Follow all app logs (the default):**
```bash
dev docker logs
```
**Print current logs and exit (don't follow):**
```bash
dev docker logs --no-follow
dev docker logs --no-follow api
```
Use `--no-follow` in scripts or when you just want a snapshot — otherwise the
command blocks streaming. (This maps to a foreground `docker compose logs`.)
**Specific service logs:**
```bash
dev docker logs api
dev docker logs worker
dev docker logs web
dev docker logs db # auto-routed to polar-shared
dev docker logs redis
dev docker logs minio
```
**Follow a specific service:**
```bash
dev docker logs -f api
```
**Instance-specific logs:**
```bash
dev docker logs -i 1 api
```
## Log Interpretation
### API Logs
**Successful request:**
```
INFO: 127.0.0.1:54321 - "GET /api/v1/users HTTP/1.1" 200
```
**Error:**
```
ERROR: Exception in endpoint
Traceback (most recent call last):
...
```
### Worker Logs
**Task started:**
```
[dramatiq.MainProcess] Task started: polar.tasks.example:process
```
**Task completed:**
```
[dramatiq.MainProcess] Task completed in 0.123s
```
### Web Logs
**Page compiled:**
```
✓ Compiled /dashboard in 234ms
```
**Error:**
```
Error: Cannot find module 'xxx'
```
## Debugging Tips
1. **Follow API logs during development:**
```bash
dev docker logs -f api
```
2. **Check worker for background job issues:**
```bash
dev docker logs -f worker
```
3. **Database issues - check db:**
```bash
dev docker logs db
```
4. **Startup issues - check all:**
```bash
dev docker logs
```
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 |