Skip to content

Commit c438203

Browse files
committed
Updated sidebar and commercial edition configuration instructions
1 parent 669d16e commit c438203

File tree

11 files changed

+291
-210
lines changed

11 files changed

+291
-210
lines changed
163 KB
Loading

mint.json

Lines changed: 13 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -57,11 +57,13 @@
5757
],
5858
"navigation": [
5959
{
60-
"group": "Self-hosting",
61-
"pages": ["self-hosting/overview"]
60+
"group": "Self-host Plane",
61+
"pages": [
62+
"self-hosting/overview"
63+
]
6264
},
6365
{
64-
"group": "Install Plane",
66+
"group": "Install",
6567
"pages": [
6668
"self-hosting/methods/docker-compose",
6769
"self-hosting/methods/kubernetes"
@@ -70,7 +72,6 @@
7072
{
7173
"group": "Configure",
7274
"pages": [
73-
"self-hosting/govern/database-and-storage",
7475
"self-hosting/govern/instance-admin",
7576
{
7677
"group": "Authentication",
@@ -79,12 +80,13 @@
7980
"self-hosting/govern/google-oauth",
8081
"self-hosting/govern/github-oauth",
8182
"self-hosting/govern/oidc-sso",
82-
"self-hosting/govern/saml-sso"
83+
"self-hosting/govern/saml-sso",
84+
"self-hosting/govern/reset-password"
8385
]
8486
},
8587
"self-hosting/govern/communication",
88+
"self-hosting/govern/database-and-storage",
8689
"self-hosting/govern/custom-domain",
87-
"self-hosting/govern/reset-password",
8890
"self-hosting/govern/private-bucket",
8991
"self-hosting/telemetry"
9092
]
@@ -93,11 +95,13 @@
9395
"group": "Manage",
9496
"pages": [
9597
"self-hosting/upgrade-from-community",
98+
"self-hosting/manage/backup-restore",
9699
"self-hosting/manage/upgrade-plane",
97-
"self-hosting/manage/prime-cli",
98-
"self-hosting/manage/migrate-plane",
99100
"self-hosting/manage/view-logs",
100-
"self-hosting/manage/backup-restore"
101+
"self-hosting/manage/migrate-plane",
102+
"self-hosting/manage/prime-cli"
103+
104+
101105
]
102106
},
103107
{

self-hosting/govern/communication.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title : Email communication
3-
sidebarTitle: Communication
2+
title : Email notifications
3+
sidebarTitle: Email
44
description: Either during your set-up or sometime later, you will want to set SMTP settings to let your users get emails to reset passwords, onboard themselves right, and get notifications for changes, and receive exports of your data.
55
---
66
## Configuration

self-hosting/govern/custom-domain.mdx

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,12 @@
11
---
2-
title: Brand instance
2+
title: Custom domain
33
description: Host your Plane instance in your custom domain. Our steps differ slightly depending on whether you are hosting on a public IP or a private/internal IP. Follow the steps listed below.
44
---
5-
## Update Configuration in .env File
5+
<Info>
6+
In the Commercial Edition, you can set up a custom domain right during installation.
7+
</Info>
8+
9+
## Update configuration in .env file
610

711
<Note>This step is mandatory for you to host Plane on a custom domain</Note>
812

@@ -22,7 +26,7 @@ CORS_ALLOWED_ORIGINS=https://example.com
2226

2327
If you are hosting Plane on a public IP, then follow the steps here. However, if you are hosting Plane on an internal IP then follow these steps.
2428

25-
## Set DNS A Record (For Public IP)
29+
## Set DNS A record (for public IP)
2630

2731
If your server has a public IP address, you need to configure the DNS A record to point to this IP address. This allows users to access your application using your custom domain name. Here’s how to do it:
2832

@@ -32,7 +36,7 @@ If your server has a public IP address, you need to configure the DNS A record t
3236
- Add a new A record with the hostname set to `@` (or your subdomain if applicable) and the IP address set to your server's public IP address.
3337
- Save the changes. It may take some time for the DNS changes to propagate.
3438

35-
## Configure Reverse Proxy (For Internal IP)
39+
## Configure reverse proxy (for internal IP)
3640

3741
If your server is behind a firewall or router and has an internal IP address, you'll need to set up a reverse proxy to route requests from your custom domain to your server. Follow these steps:
3842

self-hosting/govern/database-and-storage.mdx

Lines changed: 6 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,12 @@
11
---
2-
title: Configure external database and storage
3-
sidebarTitle: Database and storage
2+
title: Configure external PostgreSQL, Redis and S3 storage
3+
sidebarTitle: External database and storage
44
---
55

6-
> **Edition**: Commercial
76

8-
<Tip>
9-
If you're currently on the Community edition and wish to upgrade to the Commercial edition, please refer to [Upgrade from Community](/self-hosting/upgrade-from-community).
10-
</Tip>
7+
The Prime CLI lets you easily configure your Commercial Edition instance, providing options to customize the PostgreSQL database, Redis, external storage, and other advanced settings.
118

12-
The Prime CLI enables you to configure the Commercial edition instance, allowing customization of the PostgreSQL database, Redis, external storage, and other advanced settings.
13-
14-
1. From any directory on your machine, run the Prime CLI with:
9+
1. Run the Prime CLI with ↓:
1510
```sudo prime-cli```
1611

1712
2. Once the CLI is running, enter `configure`, which will guide you through a step-by-step form where you can specify the following:
@@ -21,11 +16,11 @@ The Prime CLI enables you to configure the Commercial edition instance, allowing
2116
*Default*: `80`
2217

2318
- `Max file-upload size`
24-
Set the maximum file size (in MB) that can be uploaded to your Plane app.
19+
Set the maximum file size (in MB) that members can upload.
2520
*Default*: `5 MB`
2621

2722
- `External Postgres URL`
28-
Provide the URL of your external Postgres instance if you want to switch from the default Plane configuration.
23+
Provide the URL of your external PostgreSQL instance if you want to switch from the default Plane configuration.
2924
*Default*: `Postgres 15.5` in the Docker container
3025

3126
- `External Redis URL`

self-hosting/manage/backup-restore.mdx

Lines changed: 50 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,43 @@
11
---
2-
title: Backup and restore data on Community edition
3-
sidebarTitle: Community backup and restore
2+
title: Backup and restore data
3+
sidebarTitle: Backup and restore
44
---
55

6+
Backing up your data regularly helps prevent data loss and allows you to restore your system quickly if necessary. Follow these instructions to back up and restore your data using Plane’s command-line interface.
7+
68
## Backup data
7-
There would a time when you might want to backup your data from docker volumes to external storage like S3 or drives.
9+
Create a backup of your Plane data with ↓:
10+
```bash
11+
sudo prime-cli backup
12+
```
13+
14+
This command initiates a full backup of all critical data, storing it in the default backup location at:
15+
```bash
16+
/opt/plane/backups
17+
```
18+
Each backup file will be timestamped to ensure you can easily identify the latest or a specific backup if needed.
19+
20+
## Restore data
821

9-
Lets again run the ./setup.sh command. You will again be prompted with the below options. This time select `7` to back data up.
22+
You can restore your data from a previous backup with ↓:
23+
```bash
24+
sudo prime-cli restore
1025
```
11-
Select a Action you want to perform:
26+
27+
This command prompts the restoration process, which will overwrite the current data with the data from the most recent backup file. Ensure you have selected the correct backup before running this command, as restoring will replace your current data.
28+
29+
<Accordion title="Backup and restore on Community Edition">
30+
31+
## Backup data
32+
33+
To create a backup, start by running the setup script:
34+
```bash
35+
./setup.sh
36+
```
37+
You’ll see a menu of options—just type 7 to select "Backup Data."
38+
39+
```
40+
Select an Action you want to perform:
1241
1) Install (x86_64)
1342
2) Start
1443
3) Stop
@@ -20,38 +49,37 @@ Select a Action you want to perform:
2049
2150
Action [2]: 7
2251
```
23-
In response, you can find the backup folder
52+
The system will start backing up the PostgreSQL, Redis, and upload data:
53+
2454
```
2555
Backing Up plane-app_pgdata
2656
Backing Up plane-app_redisdata
2757
Backing Up plane-app_uploads
2858
2959
Backup completed successfully. Backup files are stored in /....../plane-app/backup/20240502-1120
3060
```
31-
This backup is stored in your machine and you can then further copy it to any storage service.
61+
The backup files are stored locally, so you can copy them to an external storage service if needed for extra security.
3262
****
3363

34-
3564
## Restore data
65+
Follow these steps to restore data from a backup:
3666

37-
When you want to restore the previously backed-up data, follow the instructions below.
67+
1. Make sure Plane-CE is installed and started, then stop it. This ensures the necessary Docker volumes are ready.
3868

39-
1. Make sure that Plane-CE is installed, started, and then stopped. This ensures that the Docker volumes are created.
40-
41-
2. Download the restore script using the command below. We suggest downloading it in the same folder as setup.sh.
69+
2. Use the command ↓ to download the restore script. It’s easiest to save it in the same directory as `setup.sh`.
4270

4371
```bash
4472
curl -fsSL -o restore.sh https://raw.githubusercontent.com/makeplane/plane/master/deploy/selfhost/restore.sh
4573
chmod +x restore.sh
4674
```
4775

48-
3. Execute the command below to restore your data.
76+
3. Now, run the command to restore your data, specifying the path to your backup folder (the folder with the `*.tar.gz` files):
4977

5078
```bash
5179
./restore.sh <path to backup folder containing *.tar.gz files>
5280
```
5381

54-
As an example, for a backup folder /opt/plane-selfhost/plane-app/backup/20240722-0914, expect the response below:
82+
Here’s an example output for restoring from /opt/plane-selfhost/plane-app/backup/20240722-0914:
5583

5684
```bash
5785
--------------------------------------------
@@ -80,4 +108,11 @@ When you want to restore the previously backed-up data, follow the instructions
80108
Restore completed successfully.
81109
```
82110
83-
4. Start the Plane instance using ./setup.sh start.
111+
4. Start your Plane instance again with ↓:
112+
```bash
113+
./setup.sh start
114+
```
115+
116+
That’s it! You’re back up and running with your restored data.
117+
118+
</Accordion>

self-hosting/manage/prime-cli.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Prime CLI
33
sidebarTitle: Prime CLI
44
---
55

6-
> **Plan**: Plane Pro, Plane One
6+
> **Edition**: Commercial
77
88
<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>
99

0 commit comments

Comments
 (0)