Self hosting Plane PM tool

Oct 7, 2025

671 words · 3 min read

#self-hosting #docker #plane #project-management #caddy

Guide to self hosting Planem project management tool using Caddy for reverse proxy

Introduction

Plane is a modern project management platform. It is open source and offers a generous free plan and also a community edition.

We are using the community edition of Plane. You can know about Plane’s editions here.

In this tutorial I will guide you through the steps to install and configure Plane on Debian 12, setup Plane and use Caddy to automatically reverse proxy and generate an SSL certificate.

Steps

Step 1: Pre-requisites

You need docker installed on the vps as we will use the docker to install Plane. You can follow the instuctions on the docker’s official website.

You also need caddy installed in your system and can follow the instructions on Caddy’s website.

Check and update all other applications using the following.

sudo apt update
sudo apt upgrade

Step 2: Installing Plane

Now we have Docker and Caddy installed on our system we use the following command to to create a directory to install plane in.

mkdir plane

Move into the directory using.

cd plane

Download the latest stable release.

curl -fsSL -o setup.sh https://github.com/makeplane/plane/releases/latest/download/setup.sh

Make the file executable

chmod +x setup.sh

Run the setup file using

1
./setup.sh

You will be prompted with options to run, select 1 to install, it will create a folder plane-app and will download the docker-compose.yaml and `plane.env’ files.

Press 8 to exit.

Navigate into the plane-app directory using

cd plane-app

Open and edit the plane.env file using

sudo nano plane.env

Edit the following

LISTEN_HTTP_PORT=80 to 8080
LISTEN_HTTPS_PORT=443 to 4430
WEB_URL=https://plane.domain.com (replace with your domain)
CORS_ALLOWED_ORIGINS=https://plane.domain.com (replace with your domain)

Port 80 and 443 are being used by Caddy, you need to add different ports in plane.env. Ports such as 8080 and 4430.

This is your finished plane.env, you have no need to edit the docker-compose.yaml file.

1
APP_DOMAIN=localhost
2
APP_RELEASE=v1.0.0
3

4
WEB_REPLICAS=1
5
SPACE_REPLICAS=1
6
ADMIN_REPLICAS=1
7
API_REPLICAS=1
8
WORKER_REPLICAS=1
9
BEAT_WORKER_REPLICAS=1
10
LIVE_REPLICAS=1
11

12
LISTEN_HTTP_PORT=8080
13
LISTEN_HTTPS_PORT=4430
14

15
WEB_URL=https://plane.domain.com
16
DEBUG=0
17
CORS_ALLOWED_ORIGINS=https://plane.domain.com
18
API_BASE_URL=http://api:8000
19

20
#DB SETTINGS
21
PGHOST=plane-db
22
PGDATABASE=plane
23
POSTGRES_USER=plane
24
POSTGRES_PASSWORD=plane
25
POSTGRES_DB=plane
26
POSTGRES_PORT=5432
27
PGDATA=/var/lib/postgresql/data
28
DATABASE_URL=
29

30
# REDIS SETTINGS
31
REDIS_HOST=plane-redis
32
REDIS_PORT=6379
33
REDIS_URL=
34

35
# RabbitMQ Settings
36
RABBITMQ_HOST=plane-mq
37
RABBITMQ_PORT=5672
38
RABBITMQ_USER=plane
39
RABBITMQ_PASSWORD=plane
40
RABBITMQ_VHOST=plane
41
AMQP_URL=
42

43
# If SSL Cert to be generated, set CERT_EMAIl="email <EMAIL_ADDRESS>"
44
CERT_ACME_CA=https://acme-v02.api.letsencrypt.org/directory
45
TRUSTED_PROXIES=0.0.0.0/0
46
SITE_ADDRESS=:80
47
CERT_EMAIL=
48

49

50

51
# For DNS Challenge based certificate generation, set the CERT_ACME_DNS, CERT_EMAIL
52
# CERT_ACME_DNS="acme_dns <CERT_DNS_PROVIDER> <CERT_DNS_PROVIDER_API_KEY>"
53
CERT_ACME_DNS=
54

55

56
# Secret Key
57
SECRET_KEY=60gp0byfz2dvffa45cxl20p1scy9xbpf6d8c5y0geejgkyp1b5
58

59
# DATA STORE SETTINGS
60
USE_MINIO=1
61
AWS_REGION=
62
AWS_ACCESS_KEY_ID=access-key
63
AWS_SECRET_ACCESS_KEY=secret-key
64
AWS_S3_ENDPOINT_URL=http://plane-minio:9000
65
AWS_S3_BUCKET_NAME=uploads
66
FILE_SIZE_LIMIT=5242880
67

68
# Gunicorn Workers
69
GUNICORN_WORKERS=1
70

71
# UNCOMMENT `DOCKER_PLATFORM` IF YOU ARE ON `ARM64` AND DOCKER IMAGE IS NOT AVAILABLE FOR RESPECTIVE `APP_RELEASE`
72
# DOCKER_PLATFORM=linux/amd64
73

74
# Force HTTPS for handling SSL Termination
75
MINIO_ENDPOINT_SSL=0
76

77
# API key rate limit
78
API_KEY_RATE_LIMIT=60/minute
79
DOCKERHUB_USER=artifacts.plane.so/makeplane
80
PULL_POLICY=if_not_present
81
CUSTOM_BUILD=false

Save and close the file.

Step 3: Configuring Caddy

After setting up Plane, we must configure Caddy.

Use the following command to open the CaddyFile

sudo nano /etc/caddy/Caddyfile

Clear out the default contents and paste the following in the file. Replace plane.domain.com with your actual domain.

plane.domain.com {
        reverse_proxy localhost:8080
}

Save and restart Caddy service using the following command.

sudo systemctl restart caddy

Step 4: Start Plane

After configuring Caddy, move into your plane-app directory. Start Plane using the following command.

Run the setup file using

1
./setup.sh

Select 2, this will pull the necessary images, start the containers in the background, and set Plane up and running at port 8080.

You can check if everything is running properly using

sudo docker ps -a

This will list all running Plane containers, services listed and marked as Up.

You can now access Plane through your domain specified in CaddyFile.

plane.domain.com

You will be introduced to God mode in your first visit, following the instructions you can setup your plane instance and admin user.

Update

Run the setup file using

1
./setup.sh

Select 5 to upgrade and then select 4 to restart, this will upgrade and then restart Plane.

Conclusion

With this, your Plane instance is now fully deployed and secured behind a reverse proxy, you have control over your project management.

From here, you can start adding projects, views, and creating new users.

If you run any issues or need further help, fell free to reach out via email or open a discussion