replit-deploy-integration
Instructions for deploying Replit applications using static, autoscale, or reserved VM configurations.
Install
mkdir -p .claude/skills/replit-deploy-integration && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9442" && unzip -o skill.zip -d .claude/skills/replit-deploy-integration && rm skill.zipInstalls to .claude/skills/replit-deploy-integration
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Deploy Replit apps with Autoscale, Reserved VM, and Static deploymentKey capabilities
- →Configure Autoscale, Reserved VM, and Static deployment types
- →Set up custom domains with SSL auto-provisioning
- →Implement health check endpoints for monitoring
- →Manage production secrets via Replit workspace
- →Perform one-click deployment rollbacks
How it works
The skill guides users through configuring the .replit file for specific deployment targets, setting up environment variables, and adding health checks. It use Replit's built-in deployment infrastructure for scaling and monitoring.
Inputs & outputs
When to use replit-deploy-integration
- →Configure deployment environments
- →Set up custom domains for Replit
- →Manage app scaling settings
- →Deploy apps to production
About this skill
Replit Deploy Integration
Overview
Deploy applications on Replit's hosting platform. Three deployment types: Static (free, frontend-only), Autoscale (scales to zero, pay per request), and Reserved VM (always-on, fixed cost). Includes custom domain setup, health checks, rollbacks, and deployment monitoring.
Prerequisites
- Replit Core, Pro, or Teams plan (deployment access)
- Application working in Workspace ("Run" button)
- Custom domain (optional) with DNS access
Deployment Types
| Type | Best For | Pricing | Scale |
|---|---|---|---|
| Static | HTML/CSS/JS frontends | Free | CDN-backed, auto-cached |
| Autoscale | Variable traffic APIs | Per request | 0 to N instances |
| Reserved VM | Always-on services | $0.20+/day | Fixed resources |
Instructions
Step 1: Configure .replit for Deployment
# .replit — Autoscale deployment (most common)
entrypoint = "src/index.ts"
run = "npx tsx src/index.ts"
[nix]
channel = "stable-24_05"
[env]
NODE_ENV = "production"
[deployment]
run = ["sh", "-c", "npx tsx src/index.ts"]
build = ["sh", "-c", "npm ci --production && npm run build"]
deploymentTarget = "autoscale"
Reserved VM:
[deployment]
run = ["sh", "-c", "node dist/index.js"]
build = ["sh", "-c", "npm ci && npm run build"]
deploymentTarget = "cloudrun"
Static:
[deployment]
deploymentTarget = "static"
publicDir = "dist"
build = ["sh", "-c", "npm ci && npm run build"]
Step 2: Configure Secrets for Production
Workspace Secrets auto-sync to Deployments (2025+).
1. Click lock icon (Secrets) in sidebar
2. Add production secrets:
- DATABASE_URL (auto-populated by Replit PostgreSQL)
- API_KEY, JWT_SECRET, etc.
3. Verify in Deployment Settings > Environment Variables
Step 3: Add Health Check Endpoint
Replit monitors your deployment via health checks. Always include one:
// src/routes/health.ts
import { Router } from 'express';
import { pool } from '../services/db';
const router = Router();
router.get('/health', async (req, res) => {
const checks: Record<string, any> = {
status: 'ok',
uptime: process.uptime(),
timestamp: new Date().toISOString(),
};
// Check database if configured
if (process.env.DATABASE_URL) {
try {
await pool.query('SELECT 1');
checks.database = 'connected';
} catch {
checks.database = 'disconnected';
checks.status = 'degraded';
}
}
// Replit-specific metadata
checks.repl = process.env.REPL_SLUG;
checks.region = process.env.REPLIT_DEPLOYMENT_REGION;
const statusCode = checks.status === 'ok' ? 200 : 503;
res.status(statusCode).json(checks);
});
export default router;
Step 4: Deploy
Via Replit UI:
1. Click "Deploy" button in the top bar
2. Select deployment type:
- Static: for frontend-only apps
- Autoscale: scales to zero when idle
- Reserved VM: always-on, choose machine size
3. Configure machine size (Autoscale/VM):
- 0.25 vCPU / 512 MB — lightweight APIs
- 0.5 vCPU / 1 GB — standard web apps
- 2 vCPU / 4 GB — compute-heavy apps
- 4+ vCPU / 8-16 GB — production workloads
4. Click "Deploy"
5. Monitor build output in the deploy console
Step 5: Custom Domain Setup
1. Go to Deployment Settings > Custom Domain
2. Enter your domain: app.example.com
3. Add DNS record at your registrar:
Type: CNAME
Name: app
Value: your-repl-slug.replit.app
4. Wait for SSL auto-provisioning (1-5 minutes)
5. Verify:
# Verify DNS
dig app.example.com CNAME
# Verify SSL
curl -I https://app.example.com
# Verify health
curl -sf https://app.example.com/health | jq .
For Replit-purchased domains:
- DNS managed in Replit dashboard
- MX records supported for custom email
- SSL auto-provisioned
Step 6: Deployment Rollback
Replit supports one-click rollback to any previous successful deployment.
1. Go to Deployment Settings > History
2. View list of past deployments with timestamps
3. Click "Rollback" on the desired version
4. Deployment reverts immediately
5. Verify health endpoint after rollback
Step 7: Post-Deploy Verification
set -euo pipefail
DEPLOY_URL="https://your-app.replit.app"
echo "=== Deployment Verification ==="
# Health check
echo -n "Health: "
curl -sf "$DEPLOY_URL/health" | jq -r '.status'
# Response time
echo -n "Response time: "
curl -s -o /dev/null -w "%{time_total}s\n" "$DEPLOY_URL/"
# SSL certificate
echo -n "SSL: "
curl -sI "$DEPLOY_URL" | grep -i "strict-transport" && echo "OK" || echo "Missing HSTS"
# Autoscale cold start test
echo "Cold start test: wait 10 min, then curl again"
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Deploy fails at build | Dependency error | Test npm ci && npm run build locally first |
| 503 after deploy | App crashes on start | Check deployment logs, verify secrets |
| Port mismatch | Not using PORT env | app.listen(process.env.PORT || 3000) |
| Cold start slow (>10s) | Heavy imports on startup | Lazy-load non-critical modules |
| Custom domain 404 | DNS not propagated | Wait, or verify CNAME record |
| SSL not provisioning | Wrong DNS record | Must be CNAME to .replit.app |
Resources
- Autoscale Deployments
- Reserved VM Deployments
- Static Deployments
- Deployment Rollbacks
- Custom Domains
- Monitoring Deployments
Next Steps
For multi-environment setup, see replit-multi-env-setup.
When not to use it
- →Deploying non-production apps to Reserved VM
Prerequisites
Limitations
- →Reserved VM requires fixed cost
- →Static deployment is frontend-only
How it compares
It provides platform-specific configuration for Replit's hosting environment rather than generic cloud deployment steps.
Compared to similar skills
replit-deploy-integration side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| replit-deploy-integration (this skill) | 0 | 27d | Caution | Beginner |
| cloudflare-manager | 25 | 9mo | Review | Intermediate |
| swarm-advanced | 7 | 4mo | Review | Advanced |
| azure-functions | 10 | 5mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
cloudflare-manager
qdhenry
Comprehensive Cloudflare account management for deploying Workers, KV Storage, R2, Pages, DNS, and Routes. Use when deploying cloudflare services, managing worker containers, configuring KV/R2 storage, or setting up DNS/routing. Requires CLOUDFLARE_API_KEY in .env and Bun runtime with dependencies installed.
swarm-advanced
ruvnet
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows
azure-functions
aj-geddes
Create serverless functions on Azure with triggers, bindings, authentication, and monitoring. Use for event-driven computing without managing infrastructure.
nuxthub-migration
onmax
Use when migrating NuxtHub projects or when user mentions NuxtHub Admin sunset, GitHub Actions deployment removal, self-hosting NuxtHub, or upgrading to v1/nightly. Covers v0.9.X self-hosting (stable) and v1/nightly multi-cloud (experimental, database/blob not ready).
workflow
vercel
Creates durable, resumable workflows using Vercel's Workflow DevKit. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow devkit", or step-based orchestration.
setup-build-tools
aaddrick
Install build and extraction tools needed for building Claude Desktop Debian packages