on master help sign in
Suggest hardware requirements for planets & stars (fixes #360)
commitb26bca3c66491931cd8cd6efa16d7fbd15a484eb authorritfed-tabryg <lambda-the-ultimate-username@protonmail.com> dateTue 15 Dec 2020, 12:37 (6 years ago) parent593c68e
2 files changed+7−1
content/using/operations/stars-and-galaxies.md+1−1 content/using/operations/using-your-ship.md+6
content/using/operations/stars-and-galaxies.md+1−1
@@ -38,7 +38,7 @@ See our [Guide to Breaches](https://urbit.org/docs/tutorials/guide-to-breaches)
3838- If you distribute planets, boot and run your star on the Arvo network, or the
3939 planets won't be able to boot for the first time or connect unless they
4040 transfer to a different star.
41−- A star is networking infrastructure. For that reason, the machine running your star or galaxy must have sufficient bandwidth and processing power for your dependent planets.
41+- A star is networking infrastructure. For that reason, the machine running your star or galaxy must have sufficient bandwidth, storage, and processing power for your dependent planets. Until event log pruning is implemented, expect ships to consume more disk space every year; stars looking to serve around 100 planets will want to ensure around 50GB of space per year of operation.
4242- When messaging others, communicate using your star only when speaking in an official/infrastructural capacity. Otherwise, use your personal planet.
4343
4444### Taxes
content/using/operations/using-your-ship.md+6
@@ -67,6 +67,12 @@ Delete the tar file, and, after installing Urbit on your new server, start your
6767./urbit your-urbit
6868```
6969
70+### Hardware requirements
71+
72+Urbit can run on any x86 computer, ideally with at least 2GB of RAM.
73+
74+Urbit maintains a persistent log of the history of your ship. Eventually this log will be automatically trimmed when necessary, but for now it only increases in size. An actively used planet will consume 5-50 GB of storage space per year of operation.
75+
7076### Console
7177
7278Your Urbit terminal is separated into two parts: the prompt (the bottom line) and the record (everything above that). The record is shared; all the output from all the apps in your command set appears in it. The prompt is multiplexed.