atareao zrewidował ten Gist 16 hours ago. Przejdź do rewizji
3 files changed, 214 insertions
compose-runner.yaml(stworzono plik)
| @@ -0,0 +1,114 @@ | |||
| 1 | + | # ============================================================================= | |
| 2 | + | # config/compose-runner.yaml | |
| 3 | + | # Extracto del compose REAL del stack `gitea` (co1, 2026-11-17) | |
| 4 | + | # ============================================================================= | |
| 5 | + | # | |
| 6 | + | # Gestionado con Dockge. El compose completo vive en: | |
| 7 | + | # /home/lorenzo/docker/dockge/stacks/gitea/compose.yaml | |
| 8 | + | # | |
| 9 | + | # Aquí se muestra el servicio `runner` y el contexto mínimo del stack. | |
| 10 | + | # Secretos redactados. | |
| 11 | + | # ============================================================================= | |
| 12 | + | ||
| 13 | + | services: | |
| 14 | + | ||
| 15 | + | # --------------------------------------------------------------------------- | |
| 16 | + | # El forge | |
| 17 | + | # --------------------------------------------------------------------------- | |
| 18 | + | gitea: | |
| 19 | + | image: gitea/gitea:28.2.0 | |
| 20 | + | container_name: gitea | |
| 21 | + | restart: unless-stopped | |
| 22 | + | environment: | |
| 23 | + | - TZ=Europe/Madrid | |
| 24 | + | volumes: | |
| 25 | + | - ./data:/data | |
| 26 | + | networks: | |
| 27 | + | - internal | |
| 28 | + | - proxy | |
| 29 | + | healthcheck: | |
| 30 | + | test: ["CMD", "curl", "-fSs", "http://gitea:3000/api/healthz"] | |
| 31 | + | interval: 30s | |
| 32 | + | timeout: 5s | |
| 33 | + | retries: 3 | |
| 34 | + | labels: | |
| 35 | + | # Traefik: HTTPS para la web | |
| 36 | + | - "traefik.http.routers.gitea-secure.entrypoints=https" | |
| 37 | + | - "traefik.http.routers.gitea-secure.rule=Host(`gitea.territoriolinux.es`)" | |
| 38 | + | - "traefik.http.services.gitea.loadbalancer.server.port=3000" | |
| 39 | + | # Traefik: entrypoint TCP para el acceso Git por SSH | |
| 40 | + | - "traefik.tcp.routers.gitea-ssh.entrypoints=git" | |
| 41 | + | - "traefik.tcp.routers.gitea-ssh.rule=HostSNI(`*`)" | |
| 42 | + | - "traefik.tcp.services.gitea-ssh.loadbalancer.server.port=22" | |
| 43 | + | ||
| 44 | + | # --------------------------------------------------------------------------- | |
| 45 | + | # La base de datos | |
| 46 | + | # --------------------------------------------------------------------------- | |
| 47 | + | db: | |
| 48 | + | image: postgres:18-alpine | |
| 49 | + | container_name: gitea-db-1 | |
| 50 | + | restart: unless-stopped | |
| 51 | + | environment: | |
| 52 | + | - POSTGRES_DB=gitea | |
| 53 | + | - POSTGRES_USER=gitea | |
| 54 | + | - POSTGRES_PASSWORD=[REDACTADO] | |
| 55 | + | volumes: | |
| 56 | + | - postgres_data:/var/lib/postgresql/data | |
| 57 | + | networks: | |
| 58 | + | - internal | |
| 59 | + | ||
| 60 | + | # --------------------------------------------------------------------------- | |
| 61 | + | # EL RUNNER — el objeto de esta demo | |
| 62 | + | # --------------------------------------------------------------------------- | |
| 63 | + | runner: | |
| 64 | + | # Imagen propia construida encima de gitea/act_runner:latest | |
| 65 | + | # con el toolchain de CI (Docker CLI, git, node, Rust/Cargo, git-cliff) | |
| 66 | + | image: local/act_runner:docker | |
| 67 | + | container_name: gitea_runner | |
| 68 | + | restart: unless-stopped | |
| 69 | + | volumes: | |
| 70 | + | # 1) El socket de Docker del host, montado dentro del runner | |
| 71 | + | - /var/run/docker.sock:/var/run/docker.sock:rw | |
| 72 | + | # 2) La config del runner, en solo lectura | |
| 73 | + | - ./runner/config.yaml:/config.yaml:ro | |
| 74 | + | # 3) Datos del runner (fichero .runner con las credenciales) | |
| 75 | + | - ./data/runner:/data:rw | |
| 76 | + | group_add: | |
| 77 | + | # 999 = gid del grupo `docker` del host (docker:x:999:lorenzo) | |
| 78 | + | # Es lo que da permiso al runner sobre /var/run/docker.sock | |
| 79 | + | - "999" | |
| 80 | + | environment: | |
| 81 | + | - GITEA_INSTANCE_URL=https://gitea.territoriolinux.es | |
| 82 | + | - GITEA_RUNNER_REGISTRATION_TOKEN=[REDACTADO] | |
| 83 | + | - GITEA_RUNNER_NAME=co1-runner | |
| 84 | + | - CONFIG_FILE=/config.yaml | |
| 85 | + | - TZ=Europe/Madrid | |
| 86 | + | depends_on: | |
| 87 | + | gitea: | |
| 88 | + | condition: service_healthy | |
| 89 | + | networks: | |
| 90 | + | - internal | |
| 91 | + | ||
| 92 | + | # --------------------------------------------------------------------------- | |
| 93 | + | # Backup diario de Postgres | |
| 94 | + | # --------------------------------------------------------------------------- | |
| 95 | + | backup: | |
| 96 | + | image: atareao/postgres-backup:latest | |
| 97 | + | container_name: backup_postgres | |
| 98 | + | restart: unless-stopped | |
| 99 | + | environment: | |
| 100 | + | - SCHEDULE=0 0 9 * * * * # cron con segundos | |
| 101 | + | - RETENTION_DAYS=7 | |
| 102 | + | - RETENTION_WEEKS=4 | |
| 103 | + | - RETENTION_MONTHS=6 | |
| 104 | + | networks: | |
| 105 | + | - internal | |
| 106 | + | ||
| 107 | + | networks: | |
| 108 | + | internal: | |
| 109 | + | driver: bridge | |
| 110 | + | proxy: | |
| 111 | + | external: true | |
| 112 | + | ||
| 113 | + | volumes: | |
| 114 | + | postgres_data: | |
renovate.yaml(stworzono plik)
| @@ -0,0 +1,56 @@ | |||
| 1 | + | # ============================================================================= | |
| 2 | + | # config/renovate.yaml | |
| 3 | + | # Workflow REAL de Renovate en Gitea Actions (co1, 2026-11-17) | |
| 4 | + | # ============================================================================= | |
| 5 | + | # | |
| 6 | + | # Vive en el repo central `atareao/renovate-bot`, en .gitea/workflows/renovate.yaml | |
| 7 | + | # | |
| 8 | + | # OJO: en Gitea los workflows van en .gitea/workflows/, NO en .github/workflows/ | |
| 9 | + | # (ver punto 18 del guión: los workflows no viajan tal cual). | |
| 10 | + | # | |
| 11 | + | # Se dispara con un cron: sábados a las 02:00 (UTC en Gitea Actions). | |
| 12 | + | # ¿Por qué de madrugada? Porque no molesta a nadie y el runner está libre. | |
| 13 | + | # ============================================================================= | |
| 14 | + | ||
| 15 | + | name: Renovate | |
| 16 | + | ||
| 17 | + | on: | |
| 18 | + | schedule: | |
| 19 | + | # sábados 02:00 (UTC en Gitea Actions) | |
| 20 | + | - cron: "0 2 * * 6" | |
| 21 | + | workflow_dispatch: | |
| 22 | + | inputs: | |
| 23 | + | logLevel: | |
| 24 | + | type: choice | |
| 25 | + | default: info | |
| 26 | + | options: [debug, info, warn, error, fatal] | |
| 27 | + | ||
| 28 | + | jobs: | |
| 29 | + | renovate: | |
| 30 | + | runs-on: ubuntu-latest | |
| 31 | + | container: | |
| 32 | + | image: ghcr.io/renovatebot/renovate:latest | |
| 33 | + | # --user root: el contenedor oficial corre como root | |
| 34 | + | # -v /data/renovate-cache:/cache: caché persistente entre ejecuciones | |
| 35 | + | options: --user root -v /data/renovate-cache:/cache | |
| 36 | + | steps: | |
| 37 | + | - uses: actions/checkout@v4 | |
| 38 | + | ||
| 39 | + | - shell: bash | |
| 40 | + | run: | | |
| 41 | + | # El autodescubrimiento está roto con usuarios bot (ver punto 21). | |
| 42 | + | # Por eso la lista de repos la genera un script propio que consulta | |
| 43 | + | # la API de Gitea y la inyecta por variable de entorno. | |
| 44 | + | export RENOVATE_REPOSITORIES="$(node scripts/discover-repos.mjs)" | |
| 45 | + | exec renovate | |
| 46 | + | env: | |
| 47 | + | # El token llega por secreto de Actions. NUNCA en el YAML. | |
| 48 | + | RENOVATE_TOKEN: ${{ secrets.RENOVATE_TOKEN }} | |
| 49 | + | RENOVATE_PLATFORM: gitea | |
| 50 | + | RENOVATE_ENDPOINT: https://gitea.territoriolinux.es/api/v1 | |
| 51 | + | RENOVATE_CONFIG_FILE: config.js | |
| 52 | + | RENOVATE_CACHE_DIR: /cache | |
| 53 | + | OSV_OFFLINE_MAX_AGE: 7d | |
| 54 | + | RENOVATE_OWNER: atareao | |
| 55 | + | # Repos que NO tienen rama `development` (ver trampa 2, punto 21) | |
| 56 | + | RENOVATE_EXCLUDE: atareao/renovate-bot,atareao/repo-A,atareao/repo-B,atareao/repo-C,atareao/repo-D | |
runner-config.yaml(stworzono plik)
| @@ -0,0 +1,44 @@ | |||
| 1 | + | # ============================================================================= | |
| 2 | + | # config/runner-config.yaml | |
| 3 | + | # config.yaml REAL del act_runner (co1, 2026-11-17) | |
| 4 | + | # ============================================================================= | |
| 5 | + | # | |
| 6 | + | # El runner lee este fichero SOLO al arrancar. | |
| 7 | + | # Si lo cambias, hay que reiniciar el contenedor. | |
| 8 | + | # | |
| 9 | + | # Se monta en el contenedor como /config.yaml (solo lectura) y se le | |
| 10 | + | # indica con la variable de entorno CONFIG_FILE=/config.yaml | |
| 11 | + | # ============================================================================= | |
| 12 | + | ||
| 13 | + | log: | |
| 14 | + | level: info | |
| 15 | + | ||
| 16 | + | runner: | |
| 17 | + | # Fichero con las credenciales del runner (id + token). | |
| 18 | + | # Se trata como un SECRETO. Un segundo proceso con el mismo fichero | |
| 19 | + | # se niega a arrancar. | |
| 20 | + | file: .runner | |
| 21 | + | ||
| 22 | + | # Dos jobs a la vez. Decisión propia (el defecto es 1). | |
| 23 | + | capacity: 2 | |
| 24 | + | ||
| 25 | + | # Tres horas máximo por job. Decisión propia (el defecto es 3h). | |
| 26 | + | timeout: 3h | |
| 27 | + | ||
| 28 | + | fetch_timeout: 5s | |
| 29 | + | fetch_interval: 2s | |
| 30 | + | ||
| 31 | + | # DÓNDE CORRE CADA JOB (ver punto 14 del guión) | |
| 32 | + | labels: | |
| 33 | + | # Los workflows que pidan runs-on: ubuntu-latest corren en contenedor | |
| 34 | + | - "ubuntu-latest:docker://docker.gitea.com/runner-images:ubuntu-latest" | |
| 35 | + | # El label `co1` es host: sin aislamiento, para despliegues | |
| 36 | + | - "co1:host" | |
| 37 | + | ||
| 38 | + | cache: | |
| 39 | + | enabled: true | |
| 40 | + | ||
| 41 | + | container: | |
| 42 | + | network: "" | |
| 43 | + | privileged: false | |
| 44 | + | docker_host: "" | |