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: src/server/install/index.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,10 @@ Installation guide will help you to install your <CommunityPlatformNameLink /> o
7
7
8
8
## Installation System Requirements
9
9
10
-
We recommend using a dedicated host machine with **8 GB** of memory and **4 vCPUS**. The requirements for CPU and persistent storage depend largely on the frequency of project updates and the anticipated size of the data you expect to store respectively.
11
-
A very conservative rule of thumb, regarding needed disk size would be `qgis project size * number of versions`.
10
+
For a typical deployment, we recommend using a dedicated host machine with **8 GB** of memory and **2 vCPUS** (similar to AWS `t3a.large` instances).
11
+
The requirements for CPU and persistent storage depend largely on the frequency of project updates and the anticipated size of the data you expect to store respectively.
12
+
A very conservative rule of thumb, regarding needed disk size would be `mergin maps project size * number of versions`.
13
+
If you have a team size over 25 people and synchronize often your <MainPlatformName /> projects, consider a host with **4 vCPUS**.
12
14
13
15
On OS level, we recommend to use a Linux distribution that has fully compatibility with Docker, since <MainPlatformName /> is deployed by default with `docker compose`.
14
16
@@ -27,8 +29,8 @@ A low-latency, high-bandwidth environment is preferred due to volume of data nee
27
29
28
30
### Firewall ports
29
31
30
-
By default, only HTTP default ports (`80`, and `443` if SSL is enabled) need to be open on firewall side.
31
-
All other infrastructure instance will work within the same docker network group.
32
+
By default, only HTTP port `8080`need to be open on firewall side. Also is recommended to open `443` port if SSL is enabled.
33
+
All other infrastructure instances will work within the same docker network group, so no additional ports need to be managed on firewall side.
0 commit comments