replit-multi-env-setup
Configure Replit dev/staging/production environments with separate databases, secrets, and deployment tiers. Use when setting up multi-environment deployments, managing per-environment secrets, or implementing environment-specific Replit configurations. Trigger with phrases like "replit environments", "replit staging", "replit dev prod", "replit environment setup", "replit separate databases". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill replit-multi-env-setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Replit Multi-Environment Setup ## Overview Configure development, staging, and production environments on Replit. Leverages Replit's built-in dev/prod database separation, environment-specific secrets, and deployment types. Covers the Replit-native approach (single Repl, dual databases) and the multi-Repl approach (separate Repls per environment). ## Prerequisites - Replit Core or Teams plan (deployment access) - PostgreSQL provisioned in Database pane - Understanding of Replit Secrets ## Environment Strategy ### Approach 1: Single Repl, Dual Databases (Recommended) Replit natively provides separate development and production databases: ```markdown Workspace "Run" button → Development database Deployed app (.replit.app) → Production database Both use the same DATABASE_URL env var — Replit routes automatically. No code changes needed between environments. ``` ### Approach 2: Multi-Repl (Staging + Production) For teams that need a staging environment: ```markdown Repl 1: my-app-staging → Autoscale deployment → staging.replit.app Repl 2: my-app-prod → Reserved VM deployment → app.example.com Each Repl has its own: - Secrets (different API keys per environment) - PostgreSQL database
- Overview
- Prerequisites
- Environment Strategy
- Approach 1: Single Repl, Dual Databases (Recommended)
- Approach 2: Multi-Repl (Staging + Production)
- Instructions
- Step 1: Environment Detection
- Step 2: Environment-Specific Configuration
- Step 3: Separate Secrets Per Environment
- Step 4: GitHub Branch Strategy (Multi-Repl)
- Step 5: Database Migration Between Environments
- Step 6: Environment Indicator in UI
- Error Handling
- Resources
What does the replit-multi-env-setup skill do?
Configure Replit dev/staging/production environments with separate databases, secrets, and deployment tiers. Use when setting up multi-environment deployments, managing per-environment secrets, or implementing environment-specific Replit configurations. Trigger with phrases like "replit environments", "replit staging", "replit dev prod", "replit environment setup", "replit separate databases". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill replit-multi-env-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.