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/manage/prime-cli.mdx
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,10 @@
1
1
---
2
-
title: Manage your instance
2
+
title: Prime CLI
3
3
sidebarTitle: Prime CLI
4
4
---
5
+
6
+
> **Plan**: Plane Pro, Plane One
7
+
5
8
<Warning>Update your CLI with the command `sudo prime-cli update-cli` before you download any Plane updates. The latest version of the CLI ensures your Plane upgrades happen smoothly.</Warning>
6
9
7
10
The Prime CLI is our own command-line interface to help you install, upgrade, and manage your instance without being a pro at Docker. -
Copy file name to clipboardExpand all lines: self-hosting/manage/upgrade-plane.mdx
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,10 @@
2
2
title: Update Plane
3
3
---
4
4
5
+
This page provides steps to update Plane to the latest version on your self-hosted instance.
6
+
## Prerequisites
7
+
Create a backup of the Plane instance. See [Backup data](/self-hosting/manage/backup-restore#backup-data) (Recommended)
5
8
## Update Plane version
6
-
7
9
<Note> This upgrade guide is for v0.14.0 and above. If your Plane version is v0.13.2 than v0.14.0 then follow the guide [here](#upgrading-from-v0-13-2-to-v0-14-0) to get to v0.14.0 and then continue with further upgrades.</Note>
8
10
It is always advised to keep Plane up to date with the latest release.
1.`ssh` into your machine as the root user (or user with sudo access) per the norms of your hosting provider.
23
-
2. Run the command below:
24
-
```
25
-
curl -fsSL https://prime.plane.so/install/ | sh -
26
-
```
27
-
3. Follow the instructions on the terminal. Hit `Enter` or `Return` to continue.
28
-
4. Enter the domain name where you will access the Plane app in the format `domain.tld` or `subdomain.domain.tld`. If you are using a paid plan, the domain linked to the license can’t be changed later.
29
-
5. Choose one of the options below:
30
-
-**Express**: Plane installs with the default configurations.
31
-
-**Advanced**: You can customize the database, Redis, storage and other settings.
32
-
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 activate the license for a paid plan, see [Activate instance](/self-hosting/manage-plans/prime-client).
34
-
</Tab>
35
-
36
-
<Tabtitle="COMMUNITY">
37
-
### Prerequisites
38
-
39
-
- Docker installed and running. Choose one of the following options:
40
-
- **Option 1**: Create an EC2 machine on AWS. It must of minimum **t3.medium/t3a.medium**. Run the below command to install docker engine.
1.`ssh` into your machine as the root user (or user with sudo access) per the norms of your hosting provider.
23
+
2. Run the command below:
24
+
```
25
+
curl -fsSL https://prime.plane.so/install/ | sh -
26
+
```
27
+
3. Follow the instructions on the terminal. Hit `Enter` or `Return` to continue.
28
+
4. Enter the domain name where you will access the Plane app in the format `domain.tld` or `subdomain.domain.tld`. If you are using a paid plan, the domain linked to the license can’t be changed later.
29
+
5. Choose one of the options below:
30
+
-**Express**: Plane installs with the default configurations.
31
+
-**Advanced**: You can customize the database, Redis, storage and other settings.
32
+
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 activate the license for a paid plan, see [Activate License](/self-hosting/prime-client).
34
+
35
+
<AccordionGroup>
36
+
<Accordiontitle="Install Community edition">
37
+
38
+
The Enterprise 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 edittion, follow the steps below:
39
+
40
+
### Prerequisites
41
+
42
+
- Docker installed and running. Choose one of the following options:
43
+
-**Option 1**: Create an EC2 machine on AWS. It must of minimum **t3.medium/t3a.medium**. Run the below command to install docker engine.
If you want to download the latest preview release, run the following commands:
66
-
```bash
67
-
export RELEASE=preview
68
-
```
69
-
```bash
70
-
curl -fsSL https://raw.githubusercontent.com/makeplane/plane/$RELEASE/deploy/selfhost/install.sh | sed 's@BRANCH=master@BRANCH='"$RELEASE"'@'> setup.sh
71
-
```
72
-
</Note>
69
+
```bash
70
+
export RELEASE=preview
71
+
```
72
+
```bash
73
+
curl -fsSL https://raw.githubusercontent.com/makeplane/plane/$RELEASE/deploy/selfhost/install.sh | sed 's@BRANCH=master@BRANCH='"$RELEASE"'@'> setup.sh
74
+
```
75
+
</Note>
73
76
4. Make the file executable.
74
77
```bash
75
78
chmod +x setup.sh
@@ -78,7 +81,7 @@ This guide shows you the steps to deploy a self-hosted instance of Plane using D
78
81
```bash
79
82
./setup.sh
80
83
```
81
-
This will prompt you with the below options.
84
+
This will prompt you with the below options.
82
85
```list
83
86
Select a Action you want to perform:
84
87
1) Install (arm64)
@@ -94,50 +97,41 @@ This guide shows you the steps to deploy a self-hosted instance of Plane using D
94
97
6. Enter `1` as input.
95
98
This will create a folder `plane-app` or `plane-app-preview` (in case of preview deployment) and will download the `docker-compose.yaml` and `.env` files.
96
99
7. Enter `8` to exit.
97
-
98
100
8. Set up the environment variables. You can use any text editor to edit this file. Below are the most importants keys you must refer to:
99
-
100
101
-`NGINX_PORT`: This is set to `80` by default. Make sure the port you choose to use is not preoccupied. For example, `NGINX_PORT=8080`
101
-
102
102
-`WEB_URL`: This is set to `http://localhost` by default. Change this to the FQDN you plan to use along with NGINX\_PORT. For example, `https://plane.example.com:8080` or `http://[IP-ADDRESS]:8080`.
103
-
104
103
-`CORS_ALLOWED_ORIGINS`: This is set to `http://localhost` by default. Change this to the FQDN you plan to use along with NGINX\_PORT. For example, `https://plane.example.com:8080` or `http://[IP-ADDRESS]:8080`.
105
-
106
104
9. Run the following command to continue with the setup.
This is the confirmation that all images were downloaded and the services are up and running.
113
+
This is the confirmation that all images were downloaded and the services are up and running.
120
114
121
115
You have successfully self-hosted the `Plane` instance. Access the application by going to IP or domain you have configured it on. For example, `https://plane.example.com:8080` or `http://[IP-ADDRESS]:8080`.
122
116
123
-
124
117
### Stop server
125
118
126
-
In case you want to make changes to `.env` variables, we recommend that you stop the services before doing that.
119
+
In case you want to make changes to `.env` variables, we recommend that you stop the services before doing that.
120
+
121
+
Run the `./setup.sh` command. Enter `3` to stop the services.
127
122
128
-
Run the `./setup.sh` command. Enter `3` to stop the services.
123
+
If all goes well, you will see something like this:
129
124
130
-
If all goes well, you will see something like this:
In case you want to make changes to `.env` variables without stopping the server or noticed some abnormalities in services, you can restart the services.
135
130
136
-
In case you want to make changes to `.env` variables without stopping the server or noticed some abnormalities in services, you can restart the services.
131
+
Run the `./setup.sh` command. Enter `4` to restart the services.
137
132
138
-
Run the `./setup.sh` command. Enter `4` to restart the services.
133
+
If all goes well, you will see something like this:
0 commit comments