Deployment

The easiest way to run Wine Cellar is by using docker as described below.

Docker Deployment

Development / Demo Mode

Note

Not for production use.

Steps:

Copy the development environment configuration:
```
cp .env.dev-sample .env.dev
```
Build the Docker image:
```
docker build -t wine-cellar-dev .
```
Start the application:
```
docker compose up
```

Production Setup

Note

This setup is under development. Proceed with caution.

Note

When using podman instead of docker you might have to add :z to the volumes to allow sharing them between containers and make SELinux happy.

Option 1: Using a Reverse Proxy

Prerequisites:

A configured reverse proxy.
Properly set .env files.

Steps:

Copy and configure environment files:

cp .env.prod.db-sample .env.prod.db
cp .env.prod-sample .env.prod

Edit .env files with secure credentials.

Start the production container:

docker compose -f docker-compose.prod.yml up

Configure your reverse proxy to forward traffic to http://127.0.0.1:8085.

Email Setup

Wine Cellar can send notification emails, including reminders for when a wine should be drunk by ("drink by" reminders).

To enable email notifications, configure the email backend and credentials in your .env-prod file:

DJANGO_EMAIL_HOST=smtp.example.com
DJANGO_EMAIL_PORT=587
DJANGO_EMAIL_HOST_USER=your@email.com
DJANGO_EMAIL_HOST_PASSWORD=yourpassword
DJANGO_EMAIL_USE_TLS=
DJANGO_EMAIL_USE_SSL=
DJANGO_DEFAULT_FROM_EMAIL=Wine Cellar <your@email.com>

Note

USE_TLS and USE_SSL are mutual exclusive, only one can be True