@@ -10,11 +10,12 @@ To boot your galaxy or star, follow our [installation instructions](@/using/inst
11### Hosting your star
11### Hosting your star
13+If you plan to distribute planets in any capacity, we ask that you keep your star
13−If you plan to distribute planets in any capacity, you must keep your star running. If you fail to do so, those planets will become orphans that are unable to communicate with the network.
14+running. If you fail to do so, those planets will become orphans that are unable
15+to communicate with the network unless they transfer to a new star.
15−To make this as simple as possible, we’re building Terraform-based tooling for star and planet hosting via Google Cloud Platform. Once it’s ready we’ll open source the tooling so you can host stars and planets for yourself and others.
17+See our [cloud hosting instructions](@/using/operations/hosting.md) for
16−
18+instructions on settings up a Digital Ocean droplet.
17−In the meantime, there are [existing instructions](@/using/install.md) for those familiar with booting a Linux instance on GCP, AWS, Digital Ocean, etc.
19### Distributing planets
20### Distributing planets
@@ -28,13 +29,15 @@ By default, your star accepts software updates from its galaxy and routes them t
29To ensure new planets can connect to your ship, users are expected to participate in network-wide breaches by [updating to the latest Urbit version](@/using/install.md), deleting (or archiving) your pier, and then booting your ship using the new binary. If you don’t participate, you won’t be able to communicate with anyone on the network who has updated to the new era.
30To ensure new planets can connect to your ship, users are expected to participate in network-wide breaches by [updating to the latest Urbit version](@/using/install.md), deleting (or archiving) your pier, and then booting your ship using the new binary. If you don’t participate, you won’t be able to communicate with anyone on the network who has updated to the new era.
31−Network-wide breaches are distinct from personal breaches, wherein an individual ship cycles its personal network keys using bridge, and then follows the same steps outlined above.
32+Network-wide breaches are distinct from personal breaches, wherein an individual ship cycles its personal network keys using Bridge, and then follows the same steps outlined above.
33See our [Guide to Breaches](https://urbit.org/docs/tutorials/guide-to-breaches) for more information and for instructions on breaching.
34See our [Guide to Breaches](https://urbit.org/docs/tutorials/guide-to-breaches) for more information and for instructions on breaching.
35### Star-owner etiquette
36### Star-owner etiquette
37−- If you distribute planets, boot and run your star on the Arvo network, or the planets won't be able to boot for the first time or connect.
38+- If you distribute planets, boot and run your star on the Arvo network, or the
39+ planets won't be able to boot for the first time or connect unless they
40+ transfer to a different star.
38- 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 and processing power for your dependent planets.
39- When messaging others, communicate using your star only when speaking in an official/infrastructural capacity. Otherwise, use your personal planet.
42- When messaging others, communicate using your star only when speaking in an official/infrastructural capacity. Otherwise, use your personal planet.