# OmniRoute — Deployment Guide on VM with Cloudflare (Português (Portugal))

🌐 **Languages:** 🇺🇸 [English](../../../../ops/VM_DEPLOYMENT_GUIDE.md) · 🇪🇹 [am](../../../am/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇸🇦 [ar](../../../ar/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇦🇿 [az](../../../az/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇧🇬 [bg](../../../bg/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇧🇩 [bn](../../../bn/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇧🇦 [bs](../../../bs/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇨🇿 [cs](../../../cs/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇩🇰 [da](../../../da/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇩🇪 [de](../../../de/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇬🇷 [el](../../../el/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇪🇸 [es](../../../es/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇪🇪 [et](../../../et/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇷 [fa](../../../fa/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇫🇮 [fi](../../../fi/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇫🇷 [fr](../../../fr/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇪 [ga](../../../ga/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [gu](../../../gu/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇳🇬 [ha](../../../ha/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇱 [he](../../../he/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [hi](../../../hi/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇭🇷 [hr](../../../hr/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇭🇺 [hu](../../../hu/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇦🇲 [hy](../../../hy/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇩 [id](../../../id/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇳🇬 [ig](../../../ig/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇹 [it](../../../it/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇯🇵 [ja](../../../ja/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇬🇪 [ka](../../../ka/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇰🇭 [km](../../../km/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [kn](../../../kn/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇰🇷 [ko](../../../ko/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇱🇹 [lt](../../../lt/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇱🇻 [lv](../../../lv/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [ml](../../../ml/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [mr](../../../mr/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇲🇾 [ms](../../../ms/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇲🇹 [mt](../../../mt/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇲🇲 [my](../../../my/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇳🇵 [ne](../../../ne/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇳🇱 [nl](../../../nl/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇳🇴 [no](../../../no/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [or](../../../or/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [pa](../../../pa/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇵🇭 [phi](../../../phi/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇵🇱 [pl](../../../pl/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇧🇷 [pt-BR](../../../pt-BR/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇷🇴 [ro](../../../ro/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇷🇺 [ru](../../../ru/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇱🇰 [si](../../../si/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇸🇰 [sk](../../../sk/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇸🇮 [sl](../../../sl/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇷🇸 [sr](../../../sr/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇸🇪 [sv](../../../sv/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇰🇪 [sw](../../../sw/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [ta](../../../ta/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [te](../../../te/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇹🇭 [th](../../../th/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇹🇷 [tr](../../../tr/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇺🇦 [uk-UA](../../../uk-UA/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇵🇰 [ur](../../../ur/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇺🇿 [uz](../../../uz/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇻🇳 [vi](../../../vi/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇳🇬 [yo](../../../yo/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇨🇳 [zh-CN](../../../zh-CN/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇹🇼 [zh-TW](../../../zh-TW/docs/ops/VM_DEPLOYMENT_GUIDE.md)

---

🌐 **Languages:** 🇺🇸 [English](../../../../ops/VM_DEPLOYMENT_GUIDE.md) · 🇪🇹 [am](../../../am/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇸🇦 [ar](../../../ar/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇦🇿 [az](../../../az/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇧🇬 [bg](../../../bg/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇧🇩 [bn](../../../bn/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇧🇦 [bs](../../../bs/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇨🇿 [cs](../../../cs/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇩🇰 [da](../../../da/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇩🇪 [de](../../../de/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇬🇷 [el](../../../el/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇪🇸 [es](../../../es/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇪🇪 [et](../../../et/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇷 [fa](../../../fa/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇫🇮 [fi](../../../fi/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇫🇷 [fr](../../../fr/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇪 [ga](../../../ga/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [gu](../../../gu/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇳🇬 [ha](../../../ha/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇱 [he](../../../he/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [hi](../../../hi/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇭🇷 [hr](../../../hr/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇭🇺 [hu](../../../hu/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇦🇲 [hy](../../../hy/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇩 [id](../../../id/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇳🇬 [ig](../../../ig/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇹 [it](../../../it/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇯🇵 [ja](../../../ja/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇬🇪 [ka](../../../ka/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇰🇭 [km](../../../km/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [kn](../../../kn/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇰🇷 [ko](../../../ko/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇱🇹 [lt](../../../lt/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇱🇻 [lv](../../../lv/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [ml](../../../ml/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [mr](../../../mr/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇲🇾 [ms](../../../ms/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇲🇹 [mt](../../../mt/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇲🇲 [my](../../../my/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇳🇵 [ne](../../../ne/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇳🇱 [nl](../../../nl/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇳🇴 [no](../../../no/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [or](../../../or/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [pa](../../../pa/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇵🇭 [phi](../../../phi/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇵🇱 [pl](../../../pl/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇧🇷 [pt-BR](../../../pt-BR/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇷🇴 [ro](../../../ro/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇷🇺 [ru](../../../ru/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇱🇰 [si](../../../si/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇸🇰 [sk](../../../sk/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇸🇮 [sl](../../../sl/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇷🇸 [sr](../../../sr/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇸🇪 [sv](../../../sv/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇰🇪 [sw](../../../sw/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [ta](../../../ta/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇮🇳 [te](../../../te/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇹🇭 [th](../../../th/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇹🇷 [tr](../../../tr/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇺🇦 [uk-UA](../../../uk-UA/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇵🇰 [ur](../../../ur/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇺🇿 [uz](../../../uz/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇻🇳 [vi](../../../vi/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇳🇬 [yo](../../../yo/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇨🇳 [zh-CN](../../../zh-CN/docs/ops/VM_DEPLOYMENT_GUIDE.md) · 🇹🇼 [zh-TW](../../../zh-TW/docs/ops/VM_DEPLOYMENT_GUIDE.md)

Guia completo para instalar e configurar o OmniRoute numa VM (VPS), com o domínio gerido através da Cloudflare.

---

## Pré-requisitos

| Item        | Mínimo                  | Recomendado      |
| ----------- | ----------------------- | ---------------- |
| **CPU**     | 1 vCPU                  | 2 vCPU           |
| **RAM**     | 1 GB                    | 2 GB             |
| **Disco**   | SSD de 10 GB            | SSD de 25 GB     |
| **SO**      | Ubuntu 22.04 LTS        | Ubuntu 24.04 LTS |
| **Domínio** | Registado na Cloudflare | —                |
| **Docker**  | Docker Engine 24+       | Docker 27+       |

**Fornecedores testados**: Akamai (Linode), DigitalOcean, Vultr, Hetzner, AWS Lightsail.

---

## 1. Configurar a VM

### 1.1 Criar a instância

No seu fornecedor de VPS preferido:

- Escolha Ubuntu 24.04 LTS
- Selecione o plano mínimo (1 vCPU / 1 GB de RAM)
- Defina uma palavra-passe forte para o utilizador root ou configure uma chave SSH
- Anote o **IP público** (por exemplo, `203.0.113.10`)

### 1.2 Ligar através de SSH

```bash
ssh root@203.0.113.10
```

### 1.3 Atualizar o sistema

```bash
apt update && apt upgrade -y
```

### 1.4 Instalar o Docker

```bash
# Instalar dependências
apt install -y ca-certificates curl gnupg

# Adicionar o repositório oficial do Docker
install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | gpg --dearmor -o /etc/apt/keyrings/docker.gpg
chmod a+r /etc/apt/keyrings/docker.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu $ (. /etc/os-release && echo "$VERSION_CODENAME") stable" | tee /etc/apt/sources.list.d/docker.list > /dev/null
apt update
apt install -y docker-ce docker-ce-cli containerd.io docker-compose-plugin
```

### 1.5 Instalar o nginx

```bash
apt install -y nginx
```

### 1.6 Configurar a firewall (UFW)

```bash
ufw default deny incoming
ufw default allow outgoing
ufw allow 22/tcp    # SSH
ufw allow 80/tcp    # HTTP (redirecionamento)
ufw allow 443/tcp   # HTTPS
ufw enable
```

> **Dica**: Para obter a máxima segurança, restrinja as portas 80 e 443 apenas aos IPs da Cloudflare. Consulte a secção [Segurança avançada](#advanced-security).

---

## 2. Instalar o OmniRoute

### 2.1 Criar o diretório de configuração

```bash
mkdir -p /opt/omniroute
```

### 2.2 Criar o ficheiro de variáveis de ambiente

```bash
cat > /opt/omniroute/.env << 'EOF'
# === Segurança ===
JWT_SECRET=CHANGE-TO-A-UNIQUE-64-CHAR-SECRET-KEY
INITIAL_PASSWORD=YourSecurePassword123!
API_KEY_SECRET=REPLACE-WITH-ANOTHER-SECRET-KEY
STORAGE_ENCRYPTION_KEY=REPLACE-WITH-THIRD-SECRET-KEY
STORAGE_ENCRYPTION_KEY_VERSION=v1
MACHINE_ID_SALT=CHANGE-TO-A-UNIQUE-SALT
OMNIROUTE_WS_BRIDGE_SECRET=REPLACE-WITH-WS-BRIDGE-SECRET  # OBRIGATÓRIO em produção: utilizado pela ponte WS do Codex Responses

# === Aplicação ===
PORT=20128
NODE_ENV=production
HOSTNAME=0.0.0.0
DATA_DIR=/app/data
APP_LOG_TO_FILE=true
AUTH_COOKIE_SECURE=true
REQUIRE_API_KEY=false

# === URLs (altere para o seu domínio) ===
# URL base interna de servidor para servidor para tarefas agendadas / pedidos ao próprio servidor.
BASE_URL=http://127.0.0.1:20128
# URL destinada ao navegador, utilizada para callbacks OAuth, ligações do painel e URLs públicas geradas.
NEXT_PUBLIC_BASE_URL=https://llms.seudominio.com
# Substituição explícita opcional da origem pública para URLs públicas de recursos geradas.
# OMNIROUTE_PUBLIC_BASE_URL=https://llms.seudominio.com

# === Sincronização na cloud (opcional) ===
# CLOUD_URL=https://cloud.omniroute.online
# NEXT_PUBLIC_CLOUD_URL=https://cloud.omniroute.online
EOF
```

> ⚠️ **IMPORTANTE**: Gere chaves secretas únicas! Utilize `openssl rand -hex 32` para cada chave.

### 2.3 Iniciar o contentor

```bash
docker pull diegosouzapw/omniroute:latest

docker run -d \
  --name omniroute \
  --restart unless-stopped \
  --env-file /opt/omniroute/.env \
  -p 20128:20128 \
  -v omniroute-data:/app/data \
  diegosouzapw/omniroute:latest
```

### 2.4 Verificar se está em execução

```bash
docker ps | grep omniroute
docker logs omniroute --tail 20
```

Deverá apresentar: `[DB] SQLite database ready` e `listening on port 20128`.

---

## 3. Configurar o nginx (proxy inverso)

### 3.1 Gerar o certificado SSL (Cloudflare Origin)

No painel de controlo da Cloudflare:

1. Aceda a **SSL/TLS → Origin Server**
2. Clique em **Create Certificate**
3. Mantenha os valores predefinidos (15 anos, \*.yourdomain.com)
4. Copie o **Origin Certificate** e a **Private Key**

```bash
mkdir -p /etc/nginx/ssl

# Cole o certificado
nano /etc/nginx/ssl/origin.crt

# Cole a chave privada
nano /etc/nginx/ssl/origin.key

chmod 600 /etc/nginx/ssl/origin.key
```

### 3.2 Configuração do Nginx

```bash
cat > /etc/nginx/sites-available/omniroute << 'NGINX'
# Servidor predefinido — bloqueia o acesso direto através do IP
server {
    listen 80 default_server;
    listen [::]:80 default_server;
    listen 443 ssl default_server;
    listen [::]:443 ssl default_server;
    ssl_certificate     /etc/nginx/ssl/origin.crt;
    ssl_certificate_key /etc/nginx/ssl/origin.key;
    server_name _;
    return 444;
}

# OmniRoute — HTTPS
server {
    listen 443 ssl;
    listen [::]:443 ssl;
    server_name llms.yourdomain.com;  # Altere para o seu domínio

    ssl_certificate     /etc/nginx/ssl/origin.crt;
    ssl_certificate_key /etc/nginx/ssl/origin.key;
    ssl_protocols TLSv1.2 TLSv1.3;

    client_max_body_size 100M;

    location / {
        proxy_pass http://127.0.0.1:20128;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;

        # Suporte para WebSocket
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";

        # SSE (eventos enviados pelo servidor) — transmissão contínua de respostas de IA
        proxy_buffering off;
        proxy_cache off;
        proxy_read_timeout 600s;
        proxy_send_timeout 600s;
    }
}

# Redirecionamento de HTTP → HTTPS
server {
    listen 80;
    listen [::]:80;
    server_name llms.yourdomain.com;
    return 301 https://$server_name$request_uri;
}
NGINX
```

Mantenha os tempos limite da transmissão do proxy inverso alinhados com as variáveis de ambiente de tempo limite do OmniRoute. Se aumentar
`FETCH_TIMEOUT_MS` / `STREAM_IDLE_TIMEOUT_MS`, aumente `proxy_read_timeout` / `proxy_send_timeout`
para um valor acima do mesmo limite.

O OmniRoute utiliza `NEXT_PUBLIC_BASE_URL` como a origem canónica apresentada ao browser para as chamadas de retorno OAuth
e para as ligações públicas geradas. As operações de escrita autenticadas no painel utilizam pedidos com a mesma origem
e proteção CSRF associada à sessão, pelo que não necessitam de um URL base público estático. Os
cabeçalhos `X-Forwarded-*` acima continuam a ser metadados de encaminhamento úteis, mas não substituem
a definição do URL público explícito quando o OAuth ou as ligações geradas para o browser necessitam de um. Ative
`OMNIROUTE_TRUST_PROXY` apenas se o OmniRoute não estiver diretamente acessível aos clientes e o seu proxy
remover/recriar os cabeçalhos de reencaminhamento recebidos.

### 3.3 Ativar e testar

```bash
# Remover a configuração predefinida
rm -f /etc/nginx/sites-enabled/default

# Ativar o OmniRoute
ln -sf /etc/nginx/sites-available/omniroute /etc/nginx/sites-enabled/omniroute

# Testar e recarregar
nginx -t && systemctl reload nginx
```

---

## 4. Configurar o DNS da Cloudflare

### 4.1 Adicionar um registo DNS

No painel da Cloudflare → DNS:

| Tipo | Nome   | Conteúdo                  | Proxy      |
| ---- | ------ | ------------------------- | ---------- |
| A    | `llms` | `203.0.113.10` (IP da VM) | ✅ Ativado |

### 4.2 Configurar o SSL

Em **SSL/TLS → Overview**:

- Modo: **Full (Strict)**

Em **SSL/TLS → Edge Certificates**:

- Utilizar sempre HTTPS: ✅ Ativado
- Versão mínima do TLS: TLS 1.2
- Reescritas automáticas de HTTPS: ✅ Ativadas

### 4.3 Testes

```bash
curl -sI https://llms.seudominio.com/health
# Deve devolver HTTP/2 200
```

---

## 5. Operações e manutenção

### Atualizar para uma nova versão

```bash
docker pull diegosouzapw/omniroute:latest
docker stop omniroute && docker rm omniroute
docker run -d --name omniroute --restart unless-stopped \
  --env-file /opt/omniroute/.env \
  -p 20128:20128 \
  -v omniroute-data:/app/data \
  diegosouzapw/omniroute:latest
```

### Consultar os registos

```bash
docker logs -f omniroute          # Fluxo em tempo real
docker logs omniroute --tail 50   # Últimas 50 linhas
```

### Cópia de segurança manual da base de dados

```bash
# Copiar os dados do volume para o anfitrião
docker cp omniroute:/app/data ./backup-$(date +%F)

# Ou comprimir o volume completo
docker run --rm -v omniroute-data:/data -v $(pwd):/backup \
  alpine tar czf /backup/omniroute-data-$(date +%F).tar.gz /data
```

### Restaurar a partir de uma cópia de segurança

```bash
docker stop omniroute
docker run --rm -v omniroute-data:/data -v $(pwd):/backup \
  alpine sh -c "rm -rf /data/* && tar xzf /backup/omniroute-data-YYYY-MM-DD.tar.gz -C /"
docker start omniroute
```

---

## 6. Segurança avançada

### Restringir o nginx aos IPs da Cloudflare

```bash
cat > /etc/nginx/cloudflare-ips.conf << 'CF'
# Intervalos IPv4 da Cloudflare — atualizar periodicamente
# https://www.cloudflare.com/ips-v4/
set_real_ip_from 173.245.48.0/20;
set_real_ip_from 103.21.244.0/22;
set_real_ip_from 103.22.200.0/22;
set_real_ip_from 103.31.4.0/22;
set_real_ip_from 141.101.64.0/18;
set_real_ip_from 108.162.192.0/18;
set_real_ip_from 190.93.240.0/20;
set_real_ip_from 188.114.96.0/20;
set_real_ip_from 197.234.240.0/22;
set_real_ip_from 198.41.128.0/17;
set_real_ip_from 162.158.0.0/15;
set_real_ip_from 104.16.0.0/13;
set_real_ip_from 104.24.0.0/14;
set_real_ip_from 172.64.0.0/13;
set_real_ip_from 131.0.72.0/22;
real_ip_header CF-Connecting-IP;
CF
```

Adicione o seguinte ao `nginx.conf`, dentro do bloco `http {}`:

```nginx
include /etc/nginx/cloudflare-ips.conf;
```

### Instalar o fail2ban

```bash
apt install -y fail2ban
systemctl enable fail2ban
systemctl start fail2ban

# Verificar o estado
fail2ban-client status sshd
```

### Bloquear o acesso direto à porta do Docker

```bash
# Impedir o acesso externo direto à porta 20128
iptables -I DOCKER-USER -p tcp --dport 20128 -j DROP
iptables -I DOCKER-USER -i lo -p tcp --dport 20128 -j ACCEPT

# Tornar as regras persistentes
apt install -y iptables-persistent
netfilter-persistent save
```

---

## 7. Implementar no Cloudflare Workers (opcional)

Para acesso remoto através do Cloudflare Workers (sem expor diretamente a VM):

```bash
# No repositório local
cd omnirouteCloud
npm install
npx wrangler login
npx wrangler deploy
```

Consulte também [TUNNELS_GUIDE.md](./TUNNELS_GUIDE.md) para obter o guia passo a passo do Cloudflare Tunnel incluído no repositório. O worker autónomo `omnirouteCloud/` encontra-se num repositório complementar separado.

---

## Resumo das Portas

| Porta | Serviço     | Acesso                              |
| ----- | ----------- | ----------------------------------- |
| 22    | SSH         | Público (com fail2ban)              |
| 80    | nginx HTTP  | Redirecionamento → HTTPS            |
| 443   | nginx HTTPS | Através do proxy da Cloudflare      |
| 20128 | OmniRoute   | Apenas localhost (através do nginx) |

## Otimização para Pouca Memória / VPS Pequeno

Para implementações em instâncias VPS pequenas (1 GB de RAM ou menos):

- **Desative os serviços em segundo plano** — defina `OMNIROUTE_DISABLE_BACKGROUND_SERVICES=1` para ignorar o agendador, o servidor MCP e as tarefas de manutenção periódicas. Consulte `docs/reference/ENVIRONMENT.md`.
- **Utilize o modo WAL do SQLite** — está ativado por predefinição e reduz o pico de utilização de memória durante leituras simultâneas.
- **Limite a memória heap do V8** — defina `OMNIROUTE_MEMORY_MB` (por exemplo, `512`) para que o ambiente de execução não calibre um limite superior à capacidade da VM. Consulte `docs/reference/ENVIRONMENT.md`.
- **A admissão de pedidos pesados é ajustada automaticamente com o limite da memória heap** -- depois de definir `OMNIROUTE_MEMORY_MB` acima, o orçamento de bytes de ingestão (`OMNIROUTE_CHAT_MAX_INFLIGHT_BYTES`) é derivado desse mesmo limite, pelo que uma VM com memória limitada recebe automaticamente um orçamento inferior para pedidos simultâneos, sem necessidade de configuração adicional; os pedidos excedentes recebem uma resposta `503` repetível com `Retry-After`, em vez de competirem pela memória. Defina o limite legado de contagem de pedidos `OMNIROUTE_CHAT_MAX_HEAVY_IN_FLIGHT` apenas se necessitar de um limite absoluto adicional.
- **Evite executar `next build` no VPS** — efetue a compilação localmente e implemente a saída autónoma (`.next/standalone/`).
- **Monitorize com `top` / `free -m`** — normalmente, o OmniRoute utiliza 200–400 MB de RSS em inatividade numa VM com 1 GB.