pietre/rss2
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rss2/docs/DEPLOY.md
SITO b3bf3d7a7f refactor: reorganizar estructura de archivos en raiz 
Antes la raiz tenia 20+ archivos sueltos. Ahora organizado en:

  docs/       10 archivos .md de documentacion tecnica
  scripts/    3 scripts utilitarios (credentials, migrate, verify)
  config/     entity_config.json (aliases y blacklist NER)
  data/       feeds.csv (feeds precargados)

Eliminados restos de Docker que ya no aplican:
  .dockerignore, .env.example, .env.secure.example, nginx.conf (raiz)

Makefile: eliminados targets docker-build, añadidos install/rebuild/check/poc

Referencias actualizadas en:
  deploy/debian/install.sh  entity_config.json -> config/entity_config.json
  deploy/debian/build.sh    entity_config.json -> config/entity_config.json
  README.md                 links a docs/ y data/ actualizados,
                            arbol de estructura del repo reescrito

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-30 22:29:50 +02:00

2.1 KiB
Raw Permalink Blame History

Deployment Guide

This guide describes how to deploy the application to a new server.

Prerequisites

  • Linux Server (Ubuntu 22.04+ recommended)
  • NVIDIA GPU: Required for translation, embeddings, and NER services.
  • NVIDIA Container Toolkit: Must be installed to allow Docker to access the GPU.
  • Docker & Docker Compose: Latest versions.
  • Git: To clone the repository.
  • External Service: An instance of AllTalk running externally or on the host (port 7851 by default).

Deployment Steps

  1. Clone the Repository

    git clone <your-repo-url>
cd <your-repo-name>

  2. Configure Environment Variables Copy the example configuration file:

    cp .env.example .env

    Edit .env and set secure passwords and configuration:

    nano .env
    • Change POSTGRES_PASSWORD and DB_PASS to a strong unique password.
    • Change SECRET_KEY to a long random string.
    • Verify ALLTALK_URL points to your AllTalk instance (default assumes host machine access).

  3. Start the Services Run the following command to build and start the application:

    docker compose up -d --build

  4. Database Initialization The database will automatically initialize on the first run using the scripts in init-db/. This may take a few minutes. Check logs with:

    docker compose logs -f db

  5. Verify Deployment Access the application at http://<your-server-ip>:8001.

Important Notes

  • Models: The application mounts ./models and ./hf_cache to persist AI models. On the first run, it will attempt to download necessary models (NLLB, BERT, etc.), which requires significant bandwidth and time.
  • Data Persistence: Database data is stored in ./pgdata (mapped in docker-compose). Ensure this directory is backed up.
  • Security: Ensure port 5432 (Postgres) and 6379 (Redis) are firewall-protected and not exposed to the public internet unless intended (Docker maps them to the host network).