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: self-hosting/methods/docker-compose.mdx
+14-6Lines changed: 14 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ title: Docker
4
4
5
5
This guide shows you the steps to deploy a self-hosted instance of Plane using Docker.
6
6
7
-
## Recommended edition
7
+
## Install Plane
8
8
Plane One and Plane Pro are enabled on this edition, so the Free plan on this edition is easier to trial our paid plans from.
9
9
10
10
### Prerequisites
@@ -17,7 +17,11 @@ Plane One and Plane Pro are enabled on this edition, so the Free plan on this ed
17
17
- CentOS
18
18
- Amazon Linux 2 or Linux 2023
19
19
20
-
### Installation
20
+
### Procedure
21
+
22
+
<Tip>
23
+
If you want to upgrade from Community to the Commercial edition, see [Upgrade from Community](/self-hosting/upgrade-from-community).
24
+
</Tip>
21
25
22
26
1.`ssh` into your machine as the root user (or user with sudo access) per the norms of your hosting provider.
23
27
2. Run the command below:
@@ -30,10 +34,13 @@ Plane One and Plane Pro are enabled on this edition, so the Free plan on this ed
30
34
-**Express**: Plane installs with the default configurations.
31
35
-**Advanced**: You can customize the database, Redis, storage and other settings.
32
36
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.
33
-
7. If you want to upgrade to a paid plan, see [Plan upgrades](https://docs.plane.so/workspaces-and-users/upgrade-plan).
37
+
38
+
<Tip>
39
+
If you want to upgrade to a paid plan, see [Plan upgrades](https://docs.plane.so/workspaces-and-users/upgrade-plan).
40
+
</Tip>
34
41
35
-
## Community Edition
36
-
To install our Community Edition, please follow these steps below.
42
+
<Accordiontitle="Install Community Edition ">
43
+
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:
37
44
38
45
### Prerequisites
39
46
@@ -131,4 +138,5 @@ Plane One and Plane Pro are enabled on this edition, so the Free plan on this ed
131
138
Run the `./setup.sh` command. Enter `4` to restart the services.
132
139
133
140
If all goes well, you will see something like this:
Copy file name to clipboardExpand all lines: self-hosting/methods/kubernetes.mdx
+28-32Lines changed: 28 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,15 +4,18 @@ title: Kubernetes
4
4
5
5
This guide shows you the steps to deploy a self-hosted instance of Plane using Kubernetes.
6
6
7
-
## Recommended edition
7
+
## Install Plane
8
8
Plane One and Plane Pro are enabled on this edition, so the Free plan on this edition is easier to trial our paid plans from.
9
9
10
10
### Prerequisites
11
11
12
12
- A working Kubernetes cluster
13
13
-`kubectl` and `helm` on the client system that you will use to install our Helm charts
14
14
15
-
### Installation
15
+
### Procedure
16
+
<Tip>
17
+
If you want to upgrade from Community to the Commercial edition, see [Upgrade from Community](/self-hosting/upgrade-from-community).
18
+
</Tip>
16
19
17
20
1. Open terminal or any other command-line app that has access to Kubernetes tools on your local system.
18
21
2. Set the following environment variables:
@@ -87,10 +90,11 @@ Plane One and Plane Pro are enabled on this edition, so the Free plan on this ed
87
90
--wait \
88
91
--wait-for-jobs
89
92
```
90
-
5. If you want to upgrade to a paid plan, see [Plan upgrades](https://docs.plane.so/workspaces-and-users/upgrade-plan).
93
+
<Tip>
94
+
If you want to upgrade to a paid plan, see [Plan upgrades](https://docs.plane.so/workspaces-and-users/upgrade-plan).
95
+
</Tip>
91
96
92
-
<AccordionGroup>
93
-
<Accordiontitle="Configuration settings">
97
+
### Configuration settings
94
98
95
99
#### License
96
100
@@ -245,13 +249,24 @@ Plane One and Plane Pro are enabled on this edition, so the Free plan on this ed
245
249
|---|:---:|:---:|---|
246
250
| env.storageClass | longhorn || Creating the persitant volumes for the stateful deployments needs the `storageClass` name. Set the correct value as per your kubernetes cluster configuration. |
247
251
| env.secret_key | 60gp0byfz2dvffa45cxl20p1scy9xbpf6d8c5y0geejgkyp1b5 | Yes | This must be a random string which is used for hashing/encrypting the sensitive data within the application. Once set, changing this might impact the already hashed/encrypted data|
248
-
249
-
</Accordion>
250
-
</AccordionGroup>
251
-
252
-
## Community Edition
253
252
254
-
To install our Community Edition, please follow these steps below.
253
+
## Custom Ingress Routes
254
+
255
+
If you are planning to use 3rd party ingress providers, here is the available route configuration
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:
255
270
256
271
### Prerequisites
257
272
@@ -321,8 +336,7 @@ To install our Community Edition, please follow these steps below.
321
336
--wait-for-jobs
322
337
```
323
338
324
-
<AccordionGroup>
325
-
<Accordiontitle="Configuration settings">
339
+
### Configuration settings
326
340
327
341
#### Plane Version
328
342
@@ -450,22 +464,4 @@ To install our Community Edition, please follow these steps below.
450
464
| Setting | Default | Required | Description |
451
465
|---|:---:|:---:|---|
452
466
| env.secret_key | 60gp0byfz2dvffa45cxl20p1scy9xbpf6d8c5y0geejgkyp1b5 | Yes | This must be a random string that is used for hashing/encrypting the sensitive data within the application. Once set, changing this might impact the already hashed/encrypted data|
453
-
454
-
</Accordion>
455
-
</AccordionGroup>
456
-
457
-
458
-
## Custom Ingress Routes
459
-
460
-
If you are planning to use 3rd party ingress providers, here is the available route configuration
0 commit comments