caparazondigital/docker-compose
2
1
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
A 2025-04-10 09:50:18 -07:00 committed by GitHub
parent 86b693a66a
commit 900f1a2608
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
README.md
View File

@ -10,6 +10,23 @@ Decentralized communications that work with or without the Internet
* A subdomain with the MX record pointed to the A record of a node for DeltaChat mail delivery. * A subdomain with the MX record pointed to the A record of a node for DeltaChat mail delivery.
* (Optional) A Tor hidden service [configured](https://community.torproject.org/onion-services/setup/), and listening on port 80 and 8448. * (Optional) A Tor hidden service [configured](https://community.torproject.org/onion-services/setup/), and listening on port 80 and 8448.
# Hardware requirements
The system requirements will depend on several factors, including user-count, federation level, services and selecte, so we recommend choosing a system configuration that allows for the addition of resources.
A bare minimum system running all services for a small number of users would require:
* 4GB RAM
* 2 Cores
* 50Gb disk
Whereas a deployment running all services for hundres of users would require:
* 16GB RAM
* 4 Cores
* 200Gb disk
The previous configuration could potentially scale to a user count of near 1000, if the level of user activity is low, however if each service is very active and federated then we recommend a minimum of:
* 32GB RAM
* 16 Cores
* 1TB disk
# Introduction # Introduction
`dcomms` is a bundle of decentralized communication software running as services in the form of a docker swarm stack. `dcomms` is a bundle of decentralized communication software running as services in the form of a docker swarm stack.