Update docs for Docker related content #664
Conversation
|
@alex-cit could you review the texts here? |
| A low-latency, high-bandwidth environment is preferred due to volume of data needed to perform synchronization with <MainPlatformName />. This is specially important on large projects with hundreds of megabytes in between syncs. | ||
|
|
||
|
|
||
| ### Infrastructure overview |
There was a problem hiding this comment.
what about maps / SSO stack, shall we have something similar there?
There was a problem hiding this comment.
I would not mix here optional components. Maybe on the dedicated sections to add something related with infrastructure requirements? It's mainly for Maps stack...
There was a problem hiding this comment.
yes, I would not add it here but to corresponding sections if we have ones
There was a problem hiding this comment.
I believe we don't have a maps stack section (yet)
There was a problem hiding this comment.
let's create a ticket at least for not to forget
src/server/install/index.md
Outdated
| @@ -7,7 +7,34 @@ Installation guide will help you to install your <CommunityPlatformNameLink /> o | |||
|
|
|||
| ## Installation System Requirements | |||
|
|
|||
| We recommend using a dedicated host machine with 8 GB of memory. 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. | |||
| 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. | |||
There was a problem hiding this comment.
something like t3a.large equivalent should be enough but surely we can have some buffer
There was a problem hiding this comment.
t3a.large has only 2vCPUs, is this enough to handle generic enterprise deployments?
There was a problem hiding this comment.
we have it running on such machine with docker compose but there is not much load as it is only for testing - so we can say minimum t3a.large for staging/low load environments and more cpus if clients expect higher load
|
|
||
| ### Firewall ports | ||
|
|
||
| By default, only HTTP port `8080` need to be open on firewall side. Also is recommended to open `443` port if SSL is enabled. |
There was a problem hiding this comment.
I think that we recommend using HTTPS for production use.
| All other infrastructure instances will work within the same docker network group, so no additional ports need to be managed on firewall side. | ||
|
|
||
|
|
||
| ## Install Docker from official source |
There was a problem hiding this comment.
We can rename it to Install Docker or move that to some info tip message in following text.
No description provided.