Local Environment Management

Help with local development environment tasks for daily-api.

Database Access

PostgreSQL runs locally via Docker in a k8s container.

Finding the Container

bash
1docker ps --format "table {{.Names}}" | grep "k8s_app_postgres"

Running Queries

bash
1docker exec <CONTAINER_NAME> psql -U postgres -d api -c "YOUR SQL QUERY"

For multi-line queries:

bash
1docker exec <CONTAINER_NAME> psql -U postgres -d api <<'EOF'
2SELECT * FROM users LIMIT 1;
3EOF

Fake Payment Setup

Payment status for opportunities is tracked on the Organization level via recruiterSubscriptionFlags. Opportunities also store subscription info in their flags column.

Organization Subscription Fields

Opportunity Flags Fields

Fake Payment for Organization

sql
1UPDATE organization
2SET "recruiterSubscriptionFlags" = jsonb_build_object(
3  'status', 'active',
4  'provider', 'paddle',
5  'subscriptionId', 'fake_sub_123',
6  'createdAt', now(),
7  'updatedAt', now(),
8  'items', jsonb_build_array(
9    jsonb_build_object('priceId', 'pri_fake_123', 'quantity', 5)
10  )
11)
12WHERE id = 'ORGANIZATION_ID';

Reset: UPDATE organization SET "recruiterSubscriptionFlags" = '{}' WHERE id = 'ORGANIZATION_ID';

Fake Payment for Opportunity

Requires updating both the organization AND the opportunity:

sql
1-- Step 1: Update organization subscription
2UPDATE organization
3SET "recruiterSubscriptionFlags" = jsonb_build_object(
4  'status', 'active',
5  'provider', 'paddle',
6  'subscriptionId', 'fake_sub_123',
7  'createdAt', now(),
8  'updatedAt', now(),
9  'items', jsonb_build_array(
10    jsonb_build_object('priceId', 'pri_fake_123', 'quantity', 5)
11  )
12)
13WHERE id = (SELECT "organizationId" FROM opportunity WHERE id = 'OPPORTUNITY_ID');
14
15-- Step 2: Update opportunity flags
16UPDATE opportunity
17SET flags = flags || jsonb_build_object(
18  'plan', 'pri_fake_123',
19  'batchSize', 50
20)
21WHERE id = 'OPPORTUNITY_ID';

Reset:

sql
1UPDATE organization SET "recruiterSubscriptionFlags" = '{}'
2WHERE id = (SELECT "organizationId" FROM opportunity WHERE id = 'OPPORTUNITY_ID');
3
4UPDATE opportunity SET flags = flags - 'plan' - 'batchSize'
5WHERE id = 'OPPORTUNITY_ID';

Opportunity State Management

The opportunity table uses a state column (integer) to track lifecycle status. Values come from OpportunityState enum in @dailydotdev/schema.

OpportunityState Values

Update Opportunity State

sql
1-- Set to LIVE
2UPDATE opportunity SET state = 2 WHERE id = 'OPPORTUNITY_ID' RETURNING id, state, title;
3
4-- Set to DRAFT
5UPDATE opportunity SET state = 1 WHERE id = 'OPPORTUNITY_ID' RETURNING id, state, title;
6
7-- Set to CLOSED
8UPDATE opportunity SET state = 3 WHERE id = 'OPPORTUNITY_ID' RETURNING id, state, title;
9
10-- Set to IN_REVIEW
11UPDATE opportunity SET state = 4 WHERE id = 'OPPORTUNITY_ID' RETURNING id, state, title;

Instructions

When the user asks for local environment help:

1. For SQL queries: First find the postgres container, then execute via docker exec
2. For fake payments: Determine if they're providing an opportunity ID or organization ID, run the appropriate SQL
3. Always verify: After changes, run a SELECT to confirm
4. Ask if unclear: If the request is ambiguous, ask clarifying questions

Common requests:

• "Set up fake payment for opportunity X" → Run both org and opportunity updates
• "Set up fake payment for org X" → Run only org update
• "Run SQL: ..." → Execute via docker
• "Reset payment for X" → Run reset queries
• "Check subscription for X" → Query and display current state
• "Update opp X to live/draft/closed" → Update opportunity state

Discovering Schema Information

When handling requests not covered in this skill, use these techniques to discover the correct schema:

1. Check Entity Definitions

Entity files define column names and types:

bash
1# Find the entity file
2grep -r "TableName" src/entity/ --include="*.ts"
3# Read the entity to see column definitions

Key location: src/entity/ - TypeORM entities with @Column decorators show actual DB column names.

2. Find Enum Values

Many columns use integer enums from @dailydotdev/schema. To find enum values:

bash
1# Search for enum usage in codebase
2grep -r "EnumName\." src/ --include="*.ts" | head -20
3
4# Find enum definition in schema package
5grep -r "EnumName" node_modules/@dailydotdev/schema/dist/ --include="*.d.ts"

Common enum locations: node_modules/@dailydotdev/schema/dist/daily-api/*_pb.d.ts

3. Query Existing Data

When unsure about column names or values:

sql
1-- Check table structure
2\d tablename
3
4-- See existing values
5SELECT DISTINCT column_name FROM tablename LIMIT 10;
6
7-- Inspect a specific row
8SELECT * FROM tablename WHERE id = 'xxx' LIMIT 1;

4. Common Gotchas

• Column naming: Entity property names may differ from DB columns (e.g., state not status)
• Integer enums: Many "status" fields are integers, not strings - find the enum definition
• JSONB fields: Use jsonb_build_object() for updates, -> or ->> for queries
• Quoted columns: PostgreSQL requires double quotes for camelCase columns (e.g., "organizationId")

Continuous Improvement

This skill should evolve over time. When you discover new local environment operations, common testing patterns, or useful queries:

1. Add them to this file - Update the SKILL.md with new sections or examples
2. Keep it practical - Focus on operations that are frequently needed
3. Document the why - Explain what fields mean and why certain values are used

If a user asks for something not covered here, help them and then offer to add it to this skill for future use.