fix(deploy): reorganize structure and rename helm chart (#2666)

* fix(deploy): reorganize structure and update helm chart naming

Moves docker-compose files into deploy/docker-compose/ subdirectory for consistency, deletes conf-examples and deploy README (docs site is canonical), renames helm chart from chart-deco-mcp-mesh to chart-decocms throughout all templates and examples. Updates docker-compose container names and documentation to use consistent naming. Fixes SQLite → PGlite references in deployment docs and updates DATABASE_URL defaults and backup/restore commands.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

* fix(deploy): address PR review feedback

Remove quotes from heredoc delimiters in docs so $(openssl rand -base64 32)
executes instead of being written literally. Add clarifying comment for
topologySpreadConstraints instance label in helm values.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix(deploy): sync helm chart with upstream changes

Replace OTel Collector S3 exporter with S3 file sync sidecar, add
DATA_DIR configuration, and use templated securityContext for collector.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* feat(deploy): replace helm chart with official chart from helm-chart-deco-mcp-mesh

Moves the Helm chart from the standalone helm-chart-deco-mcp-mesh repo into
deploy/helm/ and adds CI to publish it to ghcr.io/decocms from this repo.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>

* fix(ci): trigger chart publish only on Chart.yaml changes

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>

* fix(deploy): rename helm chart from chart-deco-mcp-mesh to chart-deco-studio

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>

* [chore]: add nicacioliveira to maintainers

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>

* fix(deploy): replace all remaining mesh references with deco studio

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>

* docs: fix kubernetes deploy command to use helm chart

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Haiku 4.5 <noreply@anthropic.com>
Co-authored-by: decobot <capy@deco.cx>

Author: 3 people

.github/workflows/publish-chart.yml

@@ -0,0 +1,37 @@
+name: Publish Helm Chart
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - 'deploy/helm/Chart.yaml'
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install Helm
+        uses: azure/setup-helm@v4
+
+      - name: Get chart version
+        id: chart
+        run: echo "version=$(grep '^version:' deploy/helm/Chart.yaml | awk '{print $2}')" >> $GITHUB_OUTPUT
+
+      - name: Login to GHCR
+        run: helm registry login ghcr.io -u ${{ github.actor }} -p ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Package chart
+        run: helm package deploy/helm/ --dependency-update
+
+      - name: Push chart to GHCR
+        run: helm push chart-deco-studio-${{ steps.chart.outputs.version }}.tgz oci://ghcr.io/decocms
+
+      - name: Summary
+        run: echo "Published ghcr.io/decocms/chart-deco-studio:${{ steps.chart.outputs.version }}" >> $GITHUB_STEP_SUMMARY

MAINTAINERS.txt

@@ -6,4 +6,5 @@ JonasJesus42
 aka-sacci-ccr
 vibegui
 tlgimenes
-vibe-dex 
+vibe-dex
+nicacioliveira

README.md

@@ -232,8 +232,8 @@ docker compose -f deploy/docker-compose.postgres.yml up
 # Bun
 bun run build:client && bun run build:server && bun run start
 
-# Kubernetes
-kubectl apply -f k8s/
+# Kubernetes (Helm)
+helm install deco-studio oci://ghcr.io/decocms/chart-deco-studio --version <version> -n deco-studio --create-namespace
 ```
 
 No vendor lock-in. Runs on Docker, Kubernetes, AWS, GCP, or local runtimes.

apps/docs/client/src/content/2026-03-10/en/mcp-mesh/self-hosting/deploy/docker-compose.mdx

@@ -10,11 +10,11 @@ This guide covers deploying the deco CMS locally using Docker Compose for quick
 
 Learn more: [the deco CMS product page](https://www.decocms.com/mesh)
 
-Source (Docker Compose + README): [decocms/mesh/deploy](https://github.com/decocms/mesh/tree/main/deploy)
+Source (Docker Compose + README): [decocms/mesh/deploy](https://github.com/decocms/mesh/tree/main/deploy/docker-compose)
 
 ## Overview
 
-- **SQLite by default** - Works immediately without additional configuration
+- **PGlite by default** - Works immediately without additional configuration
 - **PostgreSQL optional** - Configure via environment variable
 - **Data persistence** - Docker volume to keep data between restarts
 - **Health checks** - Automatic application health monitoring
@@ -32,12 +32,19 @@ The fastest way to test the application:
 
 ```bash
 # 1. Configure environment variables
-# Edit .env and configure BETTER_AUTH_SECRET (required)
-# Generate a secret: openssl rand -base64 32
-cp conf-examples/env.example .env
+# Create a .env file with at least BETTER_AUTH_SECRET
+cat > .env << EOF
+BETTER_AUTH_SECRET=$(openssl rand -base64 32)
+EOF
 
 # 2. Configure authentication
-cp conf-examples/auth-config.json.example auth-config.json
+cat > auth-config.json << 'EOF'
+{
+  "emailAndPassword": {
+    "enabled": true
+  }
+}
+EOF
 
 # 3. Start the application
 docker compose up -d
@@ -75,15 +82,15 @@ The `.env` file contains all configurations.
 | `BETTER_AUTH_URL` | `http://localhost:3000` | URL for authentication |
 | `BASE_URL` | `http://localhost:3000` | Application base URL |
 | `BETTER_AUTH_SECRET` | **required** | Authentication secret |
-| `DATABASE_URL` | `/app/data/mesh.db` | Database URL (SQLite or PostgreSQL) |
+| `DATABASE_URL` | `file:///app/data/mesh.pglite` | Database URL (PGlite or PostgreSQL) |
 
-## Using SQLite (Default)
+## Using PGlite (Default)
 
-SQLite is the default and requires no additional configuration:
+PGlite is the default and requires no additional configuration:
 
 ```bash
 # .env
-DATABASE_URL=/app/data/mesh.db
+DATABASE_URL=file:///app/data/mesh.pglite
 ```
 
 Data will be persisted in the Docker volume `mesh-data` and kept between restarts.
@@ -195,13 +202,11 @@ The deco CMS application loads this file on startup to configure:
 - Email providers (Resend, etc.)
 - Magic link configuration
 
-### Available Example Files
-
-There are two example files in the `conf-examples/` folder:
+### Configuration Examples
 
 #### Simple Configuration
 
-Use this file when you only need basic email and password authentication:
+Use this configuration when you only need basic email and password authentication:
 
 ```json
 {
@@ -218,7 +223,7 @@ Use this file when you only need basic email and password authentication:
 
 #### Complete Configuration (SSO + Email)
 
-Use this file when you need advanced features like SSO, social login and email sending:
+Use this configuration when you need advanced features like SSO, social login and email sending:
 
 ```json
 {
@@ -389,24 +394,24 @@ docker compose up -d
 
 ```bash
 # 1. Backup first
-docker compose exec mesh cp /app/data/mesh.db /app/data/mesh.db.backup
-docker compose cp mesh:/app/data/mesh.db ./backup-$(date +%Y%m%d-%H%M%S).db
+docker compose exec mesh cp -r /app/data/mesh.pglite /app/data/mesh.pglite.backup
+docker compose cp mesh:/app/data/mesh.pglite ./backup-$(date +%Y%m%d-%H%M%S).pglite
 
 # 2. Reset
 docker compose down -v
 docker compose up -d
 ```
 
-#### Method 4: Reset only SQLite (keep other data)
+#### Method 4: Reset only PGlite (keep other data)
 
-If you want to reset only the SQLite database keeping other files:
+If you want to reset only the PGlite database keeping other files:
 
 ```bash
 # Enter container
 docker compose exec mesh sh
 
 # Inside container, remove only the database
-rm /app/data/mesh.db
+rm -rf /app/data/mesh.pglite
 
 # Restart application (will recreate database)
 exit
@@ -458,14 +463,14 @@ docker compose up -d
 
 ## Backup and Restore
 
-### Backup (SQLite)
+### Backup (PGlite)
 
 ```bash
 # Create backup
-docker compose exec mesh cp /app/data/mesh.db /app/data/mesh.db.backup
+docker compose exec mesh cp -r /app/data/mesh.pglite /app/data/mesh.pglite.backup
 
 # Copy to host
-docker compose cp mesh:/app/data/mesh.db ./backup-$(date +%Y%m%d).db
+docker compose cp mesh:/app/data/mesh.pglite ./backup-$(date +%Y%m%d).pglite
 ```
 
 ### Backup (PostgreSQL)

apps/docs/client/src/content/2026-03-10/pt-br/mcp-mesh/self-hosting/deploy/docker-compose.mdx

@@ -10,11 +10,11 @@ Este guia cobre o deploy do deco CMS localmente usando Docker Compose para teste
 
 Saiba mais: [a página do produto deco CMS](https://www.decocms.com/mesh)
 
-Código-fonte (Docker Compose + README): [decocms/mesh/deploy](https://github.com/decocms/mesh/tree/main/deploy)
+Código-fonte (Docker Compose + README): [decocms/mesh/deploy](https://github.com/decocms/mesh/tree/main/deploy/docker-compose)
 
 ## Visão Geral
 
-- **SQLite por padrão** - Funciona imediatamente sem configuração adicional
+- **PGlite por padrão** - Funciona imediatamente sem configuração adicional
 - **PostgreSQL opcional** - Configure via variável de ambiente
 - **Persistência de dados** - Volume Docker para manter dados entre reinicializações
 - **Health checks** - Monitoramento automático de saúde da aplicação
@@ -32,12 +32,19 @@ A forma mais rápida de testar a aplicação:
 
 ```bash
 # 1. Configurar variáveis de ambiente
-# Edite .env e configure BETTER_AUTH_SECRET (obrigatório)
-# Gere um secret: openssl rand -base64 32
-cp conf-examples/env.example .env
+# Crie um arquivo .env com pelo menos BETTER_AUTH_SECRET
+cat > .env << EOF
+BETTER_AUTH_SECRET=$(openssl rand -base64 32)
+EOF
 
 # 2. Configurar autenticação
-cp conf-examples/auth-config.json.example auth-config.json
+cat > auth-config.json << 'EOF'
+{
+  "emailAndPassword": {
+    "enabled": true
+  }
+}
+EOF
 
 # 3. Iniciar a aplicação
 docker compose up -d
@@ -75,15 +82,15 @@ O arquivo `.env` contém todas as configurações.
 | `BETTER_AUTH_URL` | `http://localhost:3000` | URL para autenticação |
 | `BASE_URL` | `http://localhost:3000` | URL base da aplicação |
 | `BETTER_AUTH_SECRET` | **obrigatório** | Secret de autenticação |
-| `DATABASE_URL` | `/app/data/mesh.db` | URL do banco de dados (SQLite ou PostgreSQL) |
+| `DATABASE_URL` | `file:///app/data/mesh.pglite` | URL do banco de dados (PGlite ou PostgreSQL) |
 
-## Usando SQLite (Padrão)
+## Usando PGlite (Padrão)
 
-SQLite é o padrão e não requer configuração adicional:
+PGlite é o padrão e não requer configuração adicional:
 
 ```bash
 # .env
-DATABASE_URL=/app/data/mesh.db
+DATABASE_URL=file:///app/data/mesh.pglite
 ```
 
 Os dados serão persistidos no volume Docker `mesh-data` e mantidos entre reinicializações.
@@ -195,13 +202,11 @@ A aplicação deco CMS carrega este arquivo na inicialização para configurar:
 - Provedores de email (Resend, etc.)
 - Configuração de magic link
 
-### Arquivos de Exemplo Disponíveis
-
-Existem dois arquivos de exemplo na pasta `conf-examples/`:
+### Exemplos de Configuração
 
 #### Configuração Simples
 
-Use este arquivo quando você só precisa de autenticação básica por email e senha:
+Use esta configuração quando você só precisa de autenticação básica por email e senha:
 
 ```json
 {
@@ -218,7 +223,7 @@ Use este arquivo quando você só precisa de autenticação básica por email e
 
 #### Configuração Completa (SSO + Email)
 
-Use este arquivo quando precisar de recursos avançados como SSO, login social e envio de emails:
+Use esta configuração quando precisar de recursos avançados como SSO, login social e envio de emails:
 
 ```json
 {
@@ -389,24 +394,24 @@ docker compose up -d
 
 ```bash
 # 1. Fazer backup primeiro
-docker compose exec mesh cp /app/data/mesh.db /app/data/mesh.db.backup
-docker compose cp mesh:/app/data/mesh.db ./backup-$(date +%Y%m%d-%H%M%S).db
+docker compose exec mesh cp -r /app/data/mesh.pglite /app/data/mesh.pglite.backup
+docker compose cp mesh:/app/data/mesh.pglite ./backup-$(date +%Y%m%d-%H%M%S).pglite
 
 # 2. Resetar
 docker compose down -v
 docker compose up -d
 ```
 
-#### Método 4: Resetar apenas o SQLite (manter outros dados)
+#### Método 4: Resetar apenas o PGlite (manter outros dados)
 
-Se quiser resetar apenas o banco de dados SQLite mantendo outros arquivos:
+Se quiser resetar apenas o banco de dados PGlite mantendo outros arquivos:
 
 ```bash
 # Entrar no container
 docker compose exec mesh sh
 
 # Dentro do container, remover apenas o banco
-rm /app/data/mesh.db
+rm -rf /app/data/mesh.pglite
 
 # Reiniciar a aplicação (vai recriar o banco)
 exit
@@ -458,14 +463,14 @@ docker compose up -d
 
 ## Backup e Restauração
 
-### Backup (SQLite)
+### Backup (PGlite)
 
 ```bash
 # Criar backup
-docker compose exec mesh cp /app/data/mesh.db /app/data/mesh.db.backup
+docker compose exec mesh cp -r /app/data/mesh.pglite /app/data/mesh.pglite.backup
 
 # Copiar para o host
-docker compose cp mesh:/app/data/mesh.db ./backup-$(date +%Y%m%d).db
+docker compose cp mesh:/app/data/mesh.pglite ./backup-$(date +%Y%m%d).pglite
 ```
 
 ### Backup (PostgreSQL)