You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/docs/guide/deployment-docker.md
+52-7Lines changed: 52 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,52 @@ Deploying Booking Calendar with Docker is the most reliable method for productio
10
10
11
11
---
12
12
13
-
## 1. Fast Track (Standard Setup)
13
+
## 1. Using Pre-built Images (Recommended)
14
+
15
+
The easiest way to run Booking Calendar is by using the pre-built images from our GitHub Container Registry. This avoids the need to build the image locally and ensures you're running a verified version.
16
+
17
+
### Docker Compose (Recommended)
18
+
19
+
Create a `docker-compose.yml` file:
20
+
21
+
```yaml
22
+
services:
23
+
app:
24
+
image: ghcr.io/sametcn99/booking-calendar:latest
25
+
container_name: booking-calendar
26
+
restart: unless-stopped
27
+
ports:
28
+
- "3000:3000"
29
+
volumes:
30
+
- ./data:/app/data
31
+
environment:
32
+
- PORT=3000
33
+
- DATABASE_PATH=/app/data/database.sqlite
34
+
# See Section 3 for more configuration variables
35
+
```
36
+
37
+
Run the application:
38
+
39
+
```bash
40
+
docker compose up -d
41
+
```
42
+
43
+
### Docker Run
44
+
45
+
If you prefer using a single command:
46
+
47
+
```bash
48
+
docker run -d \
49
+
--name booking-calendar \
50
+
-p 3000:3000 \
51
+
-v $(pwd)/data:/app/data \
52
+
-e DATABASE_PATH=/app/data/database.sqlite \
53
+
ghcr.io/sametcn99/booking-calendar:latest
54
+
```
55
+
56
+
---
57
+
58
+
## 2. Manual Build (Custom Setup)
14
59
15
60
### Prepare Environment
16
61
@@ -36,7 +81,7 @@ The application will be accessible at `http://localhost:3000` (or the port you d
36
81
37
82
---
38
83
39
-
## 2. Understanding variables
84
+
## 3. Understanding variables
40
85
41
86
There are two types of variables in Booking Calendar's Docker setup:
42
87
@@ -58,7 +103,7 @@ These can be changed at any time by restarting the container.
58
103
59
104
---
60
105
61
-
## 3. Persistent Data (Volumes)
106
+
## 4. Persistent Data (Volumes)
62
107
63
108
Booking Calendar uses a Docker Volume to ensure your database and settings are not lost when the container is updated or removed.
64
109
@@ -73,7 +118,7 @@ The SQLite database is stored in `/app/data/booking.db` inside the container, wh
73
118
74
119
---
75
120
76
-
## 4. Deploying on Coolify
121
+
## 5. Deploying on Coolify
77
122
78
123
Booking Calendar is optimized for **Coolify**. The `docker-compose.yml` uses `${VAR:-default}` syntax which Coolify automatically parses.
79
124
@@ -84,7 +129,7 @@ Booking Calendar is optimized for **Coolify**. The `docker-compose.yml` uses `${
84
129
85
130
---
86
131
87
-
## 5. Reverse Proxy & SSL
132
+
## 6. Reverse Proxy & SSL
88
133
89
134
For production, you **must** use HTTPS. We recommend:
0 commit comments