From 542f99c4841691b1817df69a136fb3825e1b4997 Mon Sep 17 00:00:00 2001 From: Leendert de Borst Date: Thu, 7 Aug 2025 07:46:17 +0200 Subject: [PATCH] Rename dockerfile and update readme for clarity (#1098) --- ...rver.all-in-one => Dockerfile.server.singlecontainer} | 0 dockerfiles/README.md | 9 +++++---- 2 files changed, 5 insertions(+), 4 deletions(-) rename dockerfiles/{Dockerfile.server.all-in-one => Dockerfile.server.singlecontainer} (100%) diff --git a/dockerfiles/Dockerfile.server.all-in-one b/dockerfiles/Dockerfile.server.singlecontainer similarity index 100% rename from dockerfiles/Dockerfile.server.all-in-one rename to dockerfiles/Dockerfile.server.singlecontainer diff --git a/dockerfiles/README.md b/dockerfiles/README.md index f1fb73ee4..7c48e7bee 100644 --- a/dockerfiles/README.md +++ b/dockerfiles/README.md @@ -10,11 +10,12 @@ Used to locally build Docker images from source instead of retrieving pre-built ### `docker-compose.dev.yml` Contains containers for aiding in local development of AliasVault. Provides a separate PostgreSQL instance for development on port 5433, managed via `./install.sh configure-dev-db`. -### `Dockerfile.single` -Alternative all-in-one Dockerfile that wraps all AliasVault services (database, API, web, background services) in one container. Primarily used for hosting on limited platforms like NAS/Unraid and small home use scenarios. +### `Dockerfile.server.singlecontainer` +This is a standalone single-container build for easy self-hosting, using s6-overlay to run multiple services (database, API, web, smtp, task runner) inside one image. -### `docker-compose.single.yml` -Docker Compose configuration for the single-container deployment using the image built from `Dockerfile.single`. Includes security settings, resource limits, and health checks optimized for NAS environments. +This build is primarily intended for **limited platforms** like NAS devices, Unraid, or other **small home-use scenarios** where simplicity is preferred over flexibility. + +> **Note:** For production or more advanced setups, we recommend using the default multi-container configuration available via [`../docker-compose.yml`](../docker-compose.yml). ## Usage