Skip to content

Commit fc2c108

Browse files
authored
Merge pull request #162 from makeplane/preview
Update master branch with changes
2 parents 64b38ad + 8139982 commit fc2c108

File tree

8 files changed

+68
-54
lines changed

8 files changed

+68
-54
lines changed

mint.json

Lines changed: 17 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@
5151
"url": "api-reference"
5252
},
5353
{
54-
"name": "Dev Tools",
54+
"name": "Build and extend",
5555
"url": "dev-tools"
5656
}
5757
],
@@ -67,20 +67,30 @@
6767
{
6868
"group": "Install",
6969
"pages": [
70-
"self-hosting/methods/docker-compose",
71-
"self-hosting/methods/docker-aio",
72-
"self-hosting/methods/docker-swarm",
70+
{
71+
"group": "Docker",
72+
"pages": [
73+
"self-hosting/methods/docker-compose",
74+
"self-hosting/methods/docker-aio",
75+
"self-hosting/methods/docker-swarm"
76+
]
77+
},
7378
"self-hosting/methods/kubernetes",
74-
"self-hosting/methods/coolify",
75-
"self-hosting/methods/portainer",
79+
"self-hosting/methods/podman-quadlets",
7680
{
7781
"group": "Airgapped Edition",
7882
"pages": [
7983
"self-hosting/methods/airgapped-edition",
8084
"self-hosting/methods/airgapped-edition-kubernetes"
8185
]
8286
},
83-
"self-hosting/methods/podman-quadlets"
87+
{
88+
"group": "Managed platforms",
89+
"pages": [
90+
"self-hosting/methods/coolify",
91+
"self-hosting/methods/portainer"
92+
]
93+
}
8494
]
8595
},
8696
{

self-hosting/methods/coolify.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,5 +43,6 @@ This guide shows you the steps to deploy a self-hosted instance of Plane using C
4343
- `AMQP_URL` – Connection string for your external RabbitMQ server.
4444

4545
8. Deploy to launch your Plane instance.
46+
Once the deployment is complete, your Plane instance should be accessible on the configured domain.
4647

47-
Once the deployment is complete, your Plane instance should be accessible on the configured domain.
48+
9. If you've purchased a paid plan, [activate your license key](https://docs.plane.so/workspaces-and-users/manage-licenses#activate-license) to unlock premium features.

self-hosting/methods/docker-aio.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,9 @@ The following ports are exposed:
9494
artifacts.plane.so/makeplane/plane-aio-commercial:stable
9595
```
9696

97-
2. Once it's running, you can access the Plane application on the domain you provided during the deployment.
97+
3. Once it's running, you can access the Plane application on the domain you provided during the deployment.
98+
99+
4. If you've purchased a paid plan, [activate your license key](https://docs.plane.so/workspaces-and-users/manage-licenses#activate-license) to unlock premium features.
98100

99101
## Volume mounts
100102

self-hosting/methods/docker-compose.mdx

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Docker
2+
title: Docker Compose
33
---
44

55
This guide shows you the steps to deploy a self-hosted instance of Plane using Docker.
@@ -40,10 +40,8 @@ Ensure you're using the **latest version of Docker Compose**. Check your Docker
4040
When self-hosting Plane for production use, it is strongly recommended to configure [external database and storage](/self-hosting/govern/database-and-storage). This ensures that your data remains secure and accessible even if the local machine crashes or encounters hardware issues. Relying solely on local storage for these components increases the risk of data loss and service disruption.
4141
</Warning>
4242
6. The installation will take a few minutes to complete and you will see the message **Plane has successfully installed**. You can access the Plane application on the domain you provided during the installation.
43-
44-
<Tip>
45-
If you want to upgrade to a paid plan, see [Plan upgrades](https://docs.plane.so/workspaces-and-users/upgrade-plan).
46-
</Tip>
43+
7. If you've purchased a paid plan, [activate your license key](https://docs.plane.so/workspaces-and-users/manage-licenses#activate-license) to unlock premium features.
44+
4745

4846
<Accordion title="Install Community Edition ">
4947
The Commercial edition comes with a free plan and the flexibility to upgrade to a paid plan at any point. If you still want to install the Community edition, follow the steps below:

self-hosting/methods/docker-swarm.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,4 +56,6 @@ This guide shows you the steps to deploy a self-hosted instance of the Plane Com
5656
docker stack deploy -c <path-to swarm-compose.yml> plane
5757
```
5858

59-
That's it! This will deploy Plane as a Swarm stack, and your instance should be accessible on your configured domain.
59+
That's it! This will deploy Plane as a Swarm stack, and your instance should be accessible on your configured domain.
60+
61+
5. If you've purchased a paid plan, [activate your license key](https://docs.plane.so/workspaces-and-users/manage-licenses#activate-license) to unlock premium features.

self-hosting/methods/kubernetes.mdx

Lines changed: 35 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Ensure you use use the latest Helm chart version.
2626
1. Open terminal or any other command-line app that has access to Kubernetes tools on your local system.
2727
2. Set the following environment variables:
2828
```bash
29-
PLANE_VERSION=v1.15.0
29+
PLANE_VERSION=v1.16.0
3030
```
3131
```bash
3232
DOMAIN_NAME=<subdomain.domain.tld or domain.tld>
@@ -44,29 +44,29 @@ Ensure you use use the latest Helm chart version.
4444

4545
4. Use one of the following ways to deploy Plane:
4646
- **Quick setup**:
47-
This is the fastest way to deploy Plane with the default settings. This will create stateful deployments for Postgres, Redis/Valkey, and Minio with a persistent volume claim using the `longhorn` storage class. This also sets up the Ingress routes for you using `nginx` ingress class. To customize these settings, see the [Custom ingress routes](#custom-ingress-routes).
47+
This is the fastest way to deploy Plane with the default settings. This will create stateful deployments for Postgres, Redis/Valkey, and Minio with a persistent volume claim using the `longhorn` storage class. This also sets up the Ingress routes for you using `nginx` ingress class. To customize these settings, see the [Custom ingress routes](#custom-ingress-routes).
4848

49-
Run the following command to deploy Plane:
49+
Run the following command to deploy Plane:
5050

51-
```bash
52-
helm install plane-app plane/plane-enterprise \
53-
--create-namespace \
54-
--namespace plane \
55-
--set license.licenseDomain=${DOMAIN_NAME} \
56-
--set license.licenseServer=https://prime.plane.so \
57-
--set planeVersion=${PLANE_VERSION} \
58-
--set ingress.enabled=true \
59-
--set ingress.ingressClass=nginx \
60-
--set env.storageClass=longhorn \
61-
--timeout 10m \
62-
--wait \
63-
--wait-for-jobs
64-
```
51+
```bash
52+
helm install plane-app plane/plane-enterprise \
53+
--create-namespace \
54+
--namespace plane \
55+
--set license.licenseDomain=${DOMAIN_NAME} \
56+
--set license.licenseServer=https://prime.plane.so \
57+
--set planeVersion=${PLANE_VERSION} \
58+
--set ingress.enabled=true \
59+
--set ingress.ingressClass=nginx \
60+
--set env.storageClass=longhorn \
61+
--timeout 10m \
62+
--wait \
63+
--wait-for-jobs
64+
```
6565

66-
<Note>
67-
This is the minimum required to set up Plane Commercial edition. You can change the default namespace from `plane`, the default app name from `plane-app`, the default storage class from `longhorn`, and the default ingress class from `nginx` to whatever you would like to.<br/> <br/>
68-
You can also pass other settings referring to the **Configuration Settings** toggle section below.
69-
</Note>
66+
<Note>
67+
This is the minimum required to set up Plane Commercial edition. You can change the default namespace from `plane`, the default app name from `plane-app`, the default storage class from `longhorn`, and the default ingress class from `nginx` to whatever you would like to.<br/> <br/>
68+
You can also pass other settings referring to the **Configuration Settings** toggle section below.
69+
</Note>
7070

7171
- **Advanced setup**:
7272
<Warning>
@@ -77,20 +77,20 @@ Ensure you use use the latest Helm chart version.
7777

7878
1. Run the script below to download the `values.yaml` file and and edit using any editor like Vim or Nano.
7979

80-
```bash
81-
helm show values plane/plane-enterprise > values.yaml
82-
vi values.yaml
83-
```
80+
```bash
81+
helm show values plane/plane-enterprise > values.yaml
82+
vi values.yaml
83+
```
8484

85-
Make sure you set the required environment variables listed below:
86-
- `planeVersion: v1.15.0`
87-
- `license.licenseDomain: <The domain you have specified to host Plane>`
88-
- `license.licenseServer: https://prime.plane.so`
89-
- `ingress.enabled: <true | false>`
90-
- `ingress.ingressClass: <nginx or any other ingress class configured in your cluster>`
91-
- `env.storageClass: <longhorn or any other storage class configured in your cluster>`
85+
Make sure you set the required environment variables listed below:
86+
- `planeVersion: v1.16.0`
87+
- `license.licenseDomain: <The domain you have specified to host Plane>`
88+
- `license.licenseServer: https://prime.plane.so`
89+
- `ingress.enabled: <true | false>`
90+
- `ingress.ingressClass: <nginx or any other ingress class configured in your cluster>`
91+
- `env.storageClass: <longhorn or any other storage class configured in your cluster>`
9292

93-
See the **Configuration settings** toggle section for more details.
93+
See the **Configuration settings** toggle section for more details.
9494

9595
2. After saving the `values.yaml` file, run the following command to deploy Plane:
9696

@@ -103,17 +103,15 @@ Ensure you use use the latest Helm chart version.
103103
--wait \
104104
--wait-for-jobs
105105
```
106-
<Tip>
107-
If you want to upgrade to a paid plan, see [Plan upgrades](https://docs.plane.so/workspaces-and-users/upgrade-plan).
108-
</Tip>
106+
5. If you've purchased a paid plan, [activate your license key](https://docs.plane.so/workspaces-and-users/manage-licenses#activate-license) to unlock premium features.
109107

110108
### Configuration settings
111109

112110
#### License
113111

114112
| Setting | Default | Required | Description |
115113
|---|:---:|:---:|---|
116-
| planeVersion | v1.15.0 | Yes | Specifies the version of Plane to be deployed. Copy this from `prime.plane.so.` |
114+
| planeVersion | v1.16.0 | Yes | Specifies the version of Plane to be deployed. Copy this from `prime.plane.so.` |
117115
| license.licenseDomain | 'plane.example.com' | Yes | The fully-qualified domain name (FQDN) in the format `sudomain.domain.tld` or `domain.tld` that the license is bound to. It is also attached to your `ingress` host to access Plane. |
118116

119117
#### Airgapped settings

self-hosting/methods/podman-quadlets.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,9 @@ Note that you should run these commands without `sudo`.
9595
systemctl --user start {web,space,admin,live,proxy}.service
9696
```
9797

98-
The startup sequence is important: network first, then dependencies, followed by backend services, and finally frontend services.
98+
The startup sequence is important: network first, then dependencies, followed by backend services, and finally frontend services.
99+
100+
6. If you've purchased a paid plan, [activate your license key](https://docs.plane.so/workspaces-and-users/manage-licenses#activate-license) to unlock premium features.
99101

100102
### Verify service status
101103
Check that all services are running correctly:

self-hosting/methods/portainer.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,5 +52,6 @@ This guide shows you the steps to deploy a self-hosted instance of Plane using P
5252
- `AMQP_URL` – Connection string for your external RabbitMQ server.
5353

5454
7. Click **Deploy the stack**.
55+
That's it! Once the deployment is complete, Plane should be up and running on your configured domain.
5556

56-
That's it! Once the deployment is complete, Plane should be up and running on your configured domain.
57+
8. If you've purchased a paid plan, [activate your license key](https://docs.plane.so/workspaces-and-users/manage-licenses#activate-license) to unlock premium features.

0 commit comments

Comments
 (0)