ca-grow-ops-manager/CREDENTIALS.md at 54d2d2f38763a723421552381490a1c477ab6f2d

fullsizemalt a9ffd1d5ca fix: Correct email domain from .com to .run

- Updated seed script: admin@runfoo.com → admin@runfoo.run
- Updated all documentation to reflect correct email
- Need to re-seed database on deployment

2025-12-09 13:46:25 -08:00

3.3 KiB

Raw Blame History

Environment: Production
URL: https://777wolfpack.runfoo.run
Last Updated: 2025-12-09

Default User Accounts

Owner Account

Email: admin@runfoo.run
Password: password123
Role: OWNER
Permissions: Full access to all features
Hourly Rate: $50.00

Seeded Data

Rooms

The following rooms are pre-configured:

Veg Room 1 - VEG type, 1200 sqft
Flower Room A - FLOWER type, 2500 sqft
Flower Room B - FLOWER type, 2500 sqft
Dry Room - DRY type, 800 sqft

Testing the Application

Navigate to https://777wolfpack.runfoo.run
Enter email: admin@runfoo.run
Enter password: password123
Click "Login"

2. Available Features (Currently Implemented)

✅ Dashboard: Overview of facility operations
✅ Rooms: View and manage grow rooms
✅ Batches: View and manage cultivation batches
✅ Timeclock: Clock in/out for labor tracking

3. Features In Development

⏳ Tasks: Task management and scheduling
⏳ Compliance: Document storage and audit packets
⏳ Settings: User preferences and management
⏳ Reports: Labor analytics and cost tracking

API Access

Base URL

https://777wolfpack.runfoo.run/api

Authentication

# Login to get JWT token
curl -X POST https://777wolfpack.runfoo.run/api/auth/login \
  -H "Content-Type: application/json" \
  -d '{
    "email": "admin@runfoo.run",
    "password": "password123"
  }'

# Response includes:
# - accessToken (use in Authorization header)
# - refreshToken (for token renewal)

Example API Calls

# Get all rooms (requires auth token)
curl https://777wolfpack.runfoo.run/api/rooms \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN"

# Get all batches
curl https://777wolfpack.runfoo.run/api/batches \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN"

Security Notes

⚠️ IMPORTANT: These are development/demo credentials.

Before production use:

Change all default passwords
Implement proper password hashing (currently using plaintext in seed)
Enable 2FA for owner accounts
Rotate JWT secrets
Implement password complexity requirements

Troubleshooting

"Invalid credentials" error

Verify you're using the exact email: admin@runfoo.run
Password is case-sensitive: password123
Check if database has been seeded (see deployment logs)

"Cannot connect to server"

Verify backend is healthy: docker compose ps
Check backend logs: docker compose logs backend
Verify Traefik routing is working

Need to re-seed database

ssh admin@nexus-vector
cd /srv/containers/ca-grow-ops-manager
docker compose exec backend npx prisma db seed

Adding More Users

Currently, user registration is only available through the seed script or direct database access.

Coming in Sprint 2: Admin user management UI

Temporary workaround (SSH to nexus-vector):

docker compose exec backend npx prisma studio
# Opens Prisma Studio on localhost:5555
# Add users manually through the UI

Need help? Check the logs:

ssh admin@nexus-vector "cd /srv/containers/ca-grow-ops-manager && docker compose logs -f"

3.3 KiB Raw Blame History

🔐 CA Grow Ops Manager - Login Credentials