@@ -114,8 +114,6 @@ http: live (insecure, loopback) on 12321
114114
115115When your ship is finished booting, you will see either the `~sampel_commet:dojo>` or `~sampel_commet:chat-cli/` prompt. If you're seeing `:chat-cli` press `Ctrl-x` to switch into Dojo. At that point, you should permanently erase your keyfile from your machine.
116116
117−**Important:** once a key has been used to boot a ship onto the network, it cannot be used to boot that ship again later - doing so will cause communication problems with other ships. For this reason you should **delete the keyfile from your machine once your ship has booted successfully**. (If you do use the same key twice, you'll need to conduct a [personal breach](#breaches) to restore your ship to full functionality).
118−
119117To exit Urbit, use `Ctrl-d`. To start your ship up again, run `./urbit mycomet` from the directory that you first booted from. Now let's do some basic commands from inside your ship.
120118
121119### The Dojo
@@ -203,6 +201,47 @@ Using a cloud service costs money, but it's more convenient to use than a local
203201
204202We have a guide for [hosting your ship on DigitalOcean](@/using/operations/hosting.md) which we've found works well, but any cloud hosting service should work.
205203
204+### Booting Your Planet
205+
206+You'll be booting your ship with the keyfile that you downloaded from Bridge [earlier in this document](#id).
207+
208+Note that this section is only for booting a ship that uses the live Urbit network.
209+
210+#### Step 1: Find Your Urbit ID
211+
212+This will look something like `~lodleb-ritrul`. You can see the name of your Urbit ID when you log into your wallet using the [Bridge client](#id).
213+
214+#### Step 2: Find the path to your keyfile
215+
216+Find the absolute path to the keyfile that you downloaded from Bridge. Copy it.
217+
218+#### Step 3: Run the boot command
219+
220+If you are not already within the directory you installed above, enter it by running `cd urbit-v0.10.8-darwin` (for Mac) or `cd urbit-v0.10.8-linux64` (for Linux) from where you ran the install commands. It contains your Urbit binary, and your ship will be installed here as well.
221+
222+Once you're inside, run the command below, except with `sampel-palnet` replaced by the name of your
223+Urbit identity, and `path/to/my-planet.key` replaced with the path to your keyfile:
224+
225+```sh
226+./urbit -w sampel-palnet -k path/to/my-planet.key
227+```
228+
229+Or, if you'd prefer to copy your key in, you can run:
230+
231+```sh
232+./urbit -w sampel-palnet -G rAnDoMkEy
233+```
234+
235+Either command will create a directory called `sampel-palnet/` and begin building your ship. It may take a few minutes.
236+
237+When your ship is finished booting, you will see either the `~sampel-palnet:dojo>` or `~sampel-palnet:chat-cli/` prompt. If you're seeing `:chat-cli` press `Ctrl-x` to switch into Dojo. At that point, you should permanently erase your keyfile from your machine.
238+
239+To shut down your ship, use `Ctrl-d`. To start your ship up again, run `./urbit sampel-palnet/` from the directory where your Urbit binary is saved. Note that in this usage, `sampel-palnet/` is the path of a folder, which by default is located in the same folder as the Urbit binary. This folder is called your ship's **pier**, and you can put it wherever you like.
240+
241+Never boot multiple instances of your ship at the same time. You can prevent this from happening on accident by only ever keeping a single copy of your pier.
242+
243+**Important:** once a key has been used to boot a ship onto the network, it cannot be used to boot that ship again later - doing so will cause communication problems with other ships. For this reason you should **delete the keyfile from your machine once your ship has booted successfully**. (If you do use the same key twice, you'll need to conduct a [personal breach](#breaches) to restore your ship to full functionality).
244+
206245### Updating to the latest binary
207246
208247Most updates to Urbit are downloaded and applied automatically as OTA (Over the Air) updates. Occasionally it would be infeasible to distribute an update this way, and a new `urbit` binary is released. This is announced in the [urbit-dev](https://groups.google.com/a/urbit.org/forum/#!forum/dev) Google Group when it occurs (as are all OTA updates). To update to the latest binary, follow the same process outlined above to download and extract it into a new folder. (the binary linked on this page will always be the latest). Then run it as before with `./urbit path/to/sampel-palnet/`.