Files
AnchorOS/DEPLOYMENT_README.md
Marco Gallegos 66e20d25a7 feat: Add Formbricks integration, update forms with webhooks, enhance navigation
- Integrate @formbricks/js for future surveys (FormbricksProvider)
- Add WebhookForm component for unified form submission (contact/franchise/membership)
- Update contact form with reason dropdown field
- Update franchise form with new fields: estado, ciudad, socios checkbox
- Update franchise benefits: manuals, training platform, RH system, investment $100k
- Add Contacto link to desktop/mobile nav and footer
- Update membership form to use WebhookForm with membership_id select
- Update hero buttons to use #3E352E color consistently
- Refactor contact/franchise pages to use new hero layout and components
- Add webhook utility (lib/webhook.ts) for parallel submission to test+prod
- Add email receipt hooks to booking endpoints
- Update globals.css with new color variables and navigation styles
- Docker configuration for deployment
2026-01-17 22:54:20 -06:00

183 lines
3.3 KiB
Markdown

# 🚀 AnchorOS Deployment Guide
## 📋 **Pre-requisitos**
- VPS con Ubuntu/Debian 20.04+
- Docker y Docker Compose instalados
- Dominio apuntando a tu VPS
- Certificados SSL (Let's Encrypt recomendado)
## 🛠️ **Configuración Inicial**
### 1. **Clonar y configurar**
```bash
git clone https://github.com/your-repo/anchoros.git
cd anchoros
cp .env.example .env
# Editar .env con tus valores reales
```
### 2. **Variables críticas**
```bash
# Requeridas para funcionamiento básico
NEXT_PUBLIC_SUPABASE_URL=https://xxxxx.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=eyJxxxxx
SUPABASE_SERVICE_ROLE_KEY=eyJxxxxx
RESEND_API_KEY=re_xxxxx
NEXT_PUBLIC_APP_URL=https://tu-dominio.com
```
### 3. **SSL Certificates**
```bash
# Instalar Certbot
sudo apt install certbot
# Generar certificados
sudo certbot certonly --standalone -d tu-dominio.com
# Copiar a directorio ssl/
sudo mkdir ssl
sudo cp /etc/letsencrypt/live/tu-dominio.com/fullchain.pem ssl/
sudo cp /etc/letsencrypt/live/tu-dominio.com/privkey.pem ssl/
```
## 🚀 **Deployment**
### **Opción 1: Script Automático**
```bash
./deploy.sh production
```
### **Opción 2: Manual**
```bash
# Build e iniciar
docker-compose -f docker-compose.prod.yml up -d --build
# Verificar
curl http://localhost/health
```
## 📊 **Monitoreo**
### **Logs**
```bash
# Todos los servicios
docker-compose -f docker-compose.prod.yml logs -f
# Servicio específico
docker-compose -f docker-compose.prod.yml logs -f anchoros
```
### **Recursos**
```bash
# Uso de CPU/Memoria
docker stats
# Espacio en disco
df -h
```
### **Health Checks**
```bash
# API health
curl https://tu-dominio.com/api/health
# Nginx status
curl -H "Host: tu-dominio.com" http://localhost/health
```
## 🔧 **Mantenimiento**
### **Updates**
```bash
# Pull latest changes
git pull origin main
# Redeploy
./deploy.sh production
```
### **Backup**
```bash
# Database backup (si usas PostgreSQL local)
docker exec anchoros_db pg_dump -U postgres anchoros > backup.sql
# Logs backup
docker-compose -f docker-compose.prod.yml logs > logs_backup.txt
```
### **SSL Renewal**
```bash
# Renew certificates
sudo certbot renew
# Restart nginx
docker-compose -f docker-compose.prod.yml restart nginx
```
## 🚨 **Troubleshooting**
### **App no responde**
```bash
# Verificar contenedores
docker ps
# Logs de la app
docker logs anchoros_app
# Reiniciar app
docker-compose -f docker-compose.prod.yml restart anchoros
```
### **Error 502 Bad Gateway**
```bash
# Nginx no puede conectar con Next.js
docker logs anchoros_nginx
# Verificar que Next.js esté corriendo
curl http://localhost:3000
```
### **Alta carga de CPU**
```bash
# Verificar procesos
docker stats
# Restart services
docker-compose -f docker-compose.prod.yml restart
```
## 📈 **Optimizaciones de Performance**
### **Nginx Caching**
- Static files: 1 año cache
- API responses: No cache
- Rate limiting: 10 req/s
### **Next.js Optimizations**
- Standalone build
- Gzip compression
- Image optimization
- Console removal en prod
### **Database**
- Conexión pool
- Query optimization
- Redis caching (opcional)
## 🔒 **Seguridad**
- SSL/TLS 1.2+
- Rate limiting
- Security headers
- No exposición de puertos internos
- Variables de entorno seguras
## 📞 **Soporte**
Para issues, revisar:
1. Docker logs
2. Network connectivity
3. Environment variables
4. SSL certificates
5. Database connections