mirror/aliasvault
1
0
Fork 0
mirror of https://github.com/aliasvault/aliasvault.git synced 2026-05-24 08:17:57 -04:00
Code Issues Packages Projects Releases Wiki Activity

Rename dockerfile and update readme for clarity (#1098)

Browse Source
This commit is contained in:
Leendert de Borst
2025-08-07 07:46:17 +02:00
committed by Leendert de Borst
parent 6ce666a35d
commit 542f99c484
2 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

0
dockerfiles/Dockerfile.server.all-in-one → dockerfiles/Dockerfile.server.singlecontainer
View File

9
dockerfiles/README.md
View File

@@ -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