mirror of
https://github.com/zulip/zulip.git
synced 2025-10-23 04:52:12 +00:00
docs: Clarify disk space requirements.
Saying "10GB" often causes users to set up a VM with 10GB _total_ space, when the intended reading is that Zulip itself needs 10GB -- and the OS takes up a non-trivial amount of that already.
This commit is contained in:
committed by
Tim Abbott
parent
9d05c80e63
commit
b8b6b1cfd0
@@ -10,10 +10,11 @@ To run a Zulip server, you will need:
|
||||
- A supported CPU architecture:
|
||||
- x86-64
|
||||
- aarch64
|
||||
- At least 2 GB RAM, and 10 GB disk space
|
||||
- At least 2 GB RAM
|
||||
- If you have < 5 GB RAM, we require some swap space; we recommend configuring
|
||||
2 GB of swap
|
||||
- If you expect 100+ users: 4 GB RAM, and 2 CPUs
|
||||
- 10GB free space (i.e. approximately a 25GB total disk, given OS requirements)
|
||||
- A hostname in DNS
|
||||
- Credentials for sending email
|
||||
|
||||
@@ -68,10 +69,10 @@ sudo apt update
|
||||
style instances for organizations with hundreds of users (active or
|
||||
no).
|
||||
|
||||
- Disk space: You'll need at least 10 GB of free disk space for a
|
||||
server with dozens of users. We recommend using an SSD and avoiding
|
||||
cloud storage backends that limit the IOPS per second, since the
|
||||
disk is primarily used for the Zulip database.
|
||||
- Disk space: You'll need at least 10 GB of dedicated free disk space
|
||||
for a server with dozens of users. We recommend using an SSD and
|
||||
avoiding cloud storage backends that limit the IOPS per second,
|
||||
since the disk is primarily used for the Zulip database.
|
||||
|
||||
See our [documentation on scalability](#scalability) below for advice
|
||||
on hardware requirements for larger organizations.
|
||||
|
Reference in New Issue
Block a user