Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

docker-selfhost

Sterne2

Forks0

Aktualisiert27. Februar 2026 um 11:26

Docker Compose self-hosting conventions for LifeOS development and production. Use when editing compose files, environment variables, service networking, persistent volumes, health checks, or deployment workflows.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

pvidaal07

pvidaal07/LifeOS

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Netzwerk- und ComputersystemadministratorenInformatik- und Mathematikberufe·SOC 15-1244

Datei-Explorer

2 Dateien

SKILL.md

readonly

name	docker-selfhost
description	Docker Compose self-hosting conventions for LifeOS development and production. Use when editing compose files, environment variables, service networking, persistent volumes, health checks, or deployment workflows.

Docker Selfhost

Objetivo

Mantener paridad dev/prod con despliegue reproducible en VPS/autohosting.

REQUIRED

Mantener docker-compose.yml para desarrollo (DB + utilidades) y docker-compose.prod.yml para stack completo.
Usar .env.example como plantilla mínima de variables.
Persistir PostgreSQL con volumen dedicado (lifeos_pgdata).
Definir healthcheck y depends_on en servicios críticos.
Exponer puertos públicos solo en servicios frontera (proxy/web).
Asegurar que backend usa DATABASE_URL interno de red Docker en producción.

NEVER

No commitear secretos reales en .env.
No depender de nombres/puertos hardcodeados sin variables.
No desplegar cambios de compose sin validar build/arranque local.

Checklist de despliegue

Actualizar .env producción.
docker compose -f docker-compose.prod.yml up -d --build.
Verificar healthchecks, logs y conectividad API/UI.

Mehr aus diesem Repository

gleiches Repository

nestjs-best-practices

pvidaal07/LifeOS

NestJS best practices and architecture patterns for building production-ready applications. This skill should be used when writing, reviewing, or refactoring NestJS code to ensure proper patterns for modules, dependency injection, security, and performance.

2026-02-272

api-contracts

pvidaal07/LifeOS

API DTO and response contract rules for LifeOS backend/frontend compatibility. Use when adding or changing endpoints, request/response DTOs, error payloads, versioning decisions, or Swagger/OpenAPI documentation.

2026-02-272

auth-and-ownership

pvidaal07/LifeOS

Authentication and ownership enforcement rules for LifeOS multi-user isolation. Use when creating or changing auth flows, guarded endpoints, user-scoped queries, or nested resource access checks.

2026-02-272

clean-architecture-ddd

pvidaal07/LifeOS

Clean Architecture + DDD rules for this repo. Triggers: adding/refactoring code across src/domain|application|infrastructure, moving files between layers, creating ports/adapters/use-cases.

2026-02-272

docs

pvidaal07/LifeOS

Repository documentation conventions for LifeOS. Use when creating or updating README, docs/*, architecture notes, API behavior notes, or implementation decisions that must remain clear for future contributors and agents.

2026-02-272

postgresql

pvidaal07/LifeOS

PostgreSQL schema and query safety rules for LifeOS. Use when changing tables, indexes, constraints, migrations, date handling, performance-sensitive queries, or any persistence design decision.

2026-02-272

name	docker-selfhost
description	Docker Compose self-hosting conventions for LifeOS development and production. Use when editing compose files, environment variables, service networking, persistent volumes, health checks, or deployment workflows.

Docker Selfhost

Objetivo

Mantener paridad dev/prod con despliegue reproducible en VPS/autohosting.

REQUIRED

Mantener docker-compose.yml para desarrollo (DB + utilidades) y docker-compose.prod.yml para stack completo.
Usar .env.example como plantilla mínima de variables.
Persistir PostgreSQL con volumen dedicado (lifeos_pgdata).
Definir healthcheck y depends_on en servicios críticos.
Exponer puertos públicos solo en servicios frontera (proxy/web).
Asegurar que backend usa DATABASE_URL interno de red Docker en producción.

NEVER

No commitear secretos reales en .env.
No depender de nombres/puertos hardcodeados sin variables.
No desplegar cambios de compose sin validar build/arranque local.

Checklist de despliegue

Actualizar .env producción.
docker compose -f docker-compose.prod.yml up -d --build.
Verificar healthchecks, logs y conectividad API/UI.