@@ -6,37 +6,35 @@ template = "page_indiced.html"
66aliases = ["/docs/getting-started/"]
77+++
88
9−This guide covers how to set up and install your own Urbit. Running Urbit on your own is somewhat technical, so if you're not technically inclined you may want to consider a [hosting provider](#hosting-providers).
9+This guide covers how to install and set up your own planet (or comet), but installation for a star is exactly the same. You will first install the Urbit binary, then you will either boot a comet or a planet. It's not too difficult, but if you would prefer to have someone run your urbit for you, consider a [hosting provider](#hosting-providers).
1010
11−## Overview
1211
13−There are two major components of the Urbit ecosystem: **Urbit OS** and **Urbit ID**.
14−
15−The Urbit peer-to-peer (P2P) network is composed of instances of Urbit OS — also called **ships** — that run as virtual machines on any Unix platform. The Urbit ID registry is deployed on the Ethereum blockchain, and individual IDs exist as non-fungible ([ERC-721](https://eips.ethereum.org/EIPS/eip-721)) tokens. On the network, Urbit IDs function as network addresses, represented by pronounceable names like `~padmyn-pasnux`.
12+## Installing Urbit
1613
17−As we'll explain, there are a few types of Urbit ID, but everyday users tend to use **planets**, as full citizens of the network.
14+You'll want the Urbit binary installed first.
1815
19−Two other types of ships are **stars** and **galaxies**. Together these perform essential infrastructural roles for the Urbit network. Each galaxy can distribute 256 stars, and each star can distribute 65,536 planets. So any given planet ultimately came from a specific star, which itself came from a specific galaxy. On the Urbit OS side, stars help route packets; galaxies are more like DNS root servers or ICANN members. The difference with Urbit in the analogy is that Urbit IDs are owned cryptographically by individuals, collectives, and companies alike, and accrue reputation independently.
16+### Windows
2017
21−If you just want to try Urbit out, there are also free IDs called **comets**. They are good for bots and people who are new to Urbit and want to check out the network, but they aren't good for building a reputation as a friendly and responsible peer. Their long names make them difficult to remember—and some communities ban comets to prevent spam—but they're still a good way to see what Urbit is about before buying your own planet.
18+> Please note that this method of installing Urbit is experimental, and we may not be able to assist you if you encounter issues related to WSL 2.
2219
23−To start with a comet, continue below. For planet instructions, see [further below](#boot-your-planet). For star or galaxy instructions, see [this section](#supernode).
20+Urbit cannot run on Windows itself, but there is a convenient way to run Linux using the [Windows Subsystem for Linux 2](https://docs.microsoft.com/en-us/windows/wsl/wsl2-install) on Windows 10. Install the Windows Subsystem for Linux 2 and open a Linux terminal in Windows, then follow the Linux installation instructions below. These instructions have been tested and verified for WSL 2 + Ubuntu 18.04 LTS, as demonstrated in `~sitful-hatred`'s step-by-step setup guide [here](https://subject.network/posts/urbit-wsl2/).
2421
25−## Installing Urbit
22+For performance reasons, do not install Urbit in the mounted Windows volume, but install it in the Linux file system. For example, in your home directory, which can be navigated to by entering `cd ~`.
2623
27−Regardless of your Urbit ID, you'll want the Urbit binary installed first. The Urbit binary runs on a Unix-like operating system – Ubuntu, Fedora, or macOS, for example.
24+### macOS {#macos-and-linux}
2825
29−### macOS and Linux
26+**The macOS binary does not work on M1 macs. Sorry. We're working on an M1 release**
3027
3128```sh
32−#macOS:
3329mkdir urbit
3430cd urbit
3531curl -JLO https://urbit.org/install/mac/latest
3632tar zxvf ./darwin.tgz --strip=1
3733./urbit
3834
39−#Linux:
35+```
36+### Linux
37+```sh
4038mkdir urbit
4139cd urbit
4240wget --content-disposition https://urbit.org/install/linux64/latest
@@ -57,23 +55,13 @@ sudo setcap 'cap_net_bind_service=+ep' /path/to/urbit
5755```
5856(Where `urbit` is the urbit executable downloaded with `wget` prior)
5957
60−### Windows
61−
62−> Please note that this method of installing Urbit is experimental, and we may not be able to assist you if you encounter issues related to WSL 2.
63−
64−Urbit cannot run on Windows itself, but there is a convenient way to run a Linux distro using the [Windows Subsystem for Linux 2](https://docs.microsoft.com/en-us/windows/wsl/wsl2-install) on Windows 10. Install the Windows Subsystem for Linux 2 and open a Linux terminal in Windows, then follow the Linux installation instructions above. These instructions have been tested and verified for WSL 2 + Ubuntu 18.04 LTS, as demonstrated in `~sitful-hatred`'s step-by-step setup guide [here](https://subject.network/posts/urbit-wsl2/).
58+### Choose to boot a comet or a planet
6559
66−For performance reasons, do not install Urbit in the mounted Windows volume, but install it in the Linux file system. For example, in your home directory, which can be navigated to by entering `cd ~`.
67−
68−## Setting up a comet {#comet}
69−
70−**Comets** are 128-bit or 16 syllable Urbit IDs, that look like:
60+If you just want to try Urbit out, you can use a comet. These are disposable, free identities, that are good for people who are new to Urbit and want to check out the network, but they aren't good for building a reputation as a friendly and responsible resident. Their long names (example: `~dasres-ragnep-lislyt-ribpyl--mosnyx-bisdem-nidful-marzod`) make them difficult to remember—and some communities ban comets to prevent spam—but they're still a good way to see what Urbit is about before buying your own planet.
7161
72−`~dasres-ragnep-lislyt-ribpyl--mosnyx-bisdem-nidful-marzod`
62+To start with a comet, continue below. For planet instructions, see [further below](#boot-your-planet).
7363
74−Comets are disposable, free identities that can be used to quickly join the network and try things out.
75−
76−### Booting a comet
64+## Booting a comet {#comet}
7765
7866To boot a comet, go into the command line and run the following command from the `urbit` directory you created during [Urbit installation](#installing-urbit):
7967
@@ -91,43 +79,23 @@ http: live (insecure, loopback) on 12321
9179~sampel_marzod:dojo>
9280```
9381
94−When your ship is finished booting, you will see either the `~sampel_marzod:dojo>` or `~sampel_marzod:chat-cli/` prompt. If you see `:chat-cli`, press `Ctrl-X` to switch into Dojo.
95−
96−To exit Urbit, use `Ctrl-D` or enter `|exit` into Dojo.
82+When your comet is finished booting, you will see `~sampel_marzod:dojo>` (Dojo: the Urbit command line).
9783
98−To start your ship up again, run the following from your `urbit` directory (note the lack of `-c` argument):
84+Get your password to log into landscape (the Urbit web interface) by typing:
9985
10086```sh
101−./urbit mycomet
102−```
103−
104−### The Dojo
105−
106−Let's try our first command in the Dojo, the Urbit OS command line and Hoon REPL, to get oriented.
107−
108−Type `(add 2 2)` into the Dojo. You should see the following:
109−
87++code
11088```
111−~sampel_marzod:dojo> (add 2 2)
112−```
113−
114−When you press Enter, you should see this:
11589
116−```
117−> (add 2 2)
118−4
119−```
90+To exit Urbit, use `Ctrl-D` or enter `|exit` into Dojo.
12091
121−Good, your Dojo is working correctly. Now let's run our first useful command in the Dojo. The first thing you generally want to do with a new ship is to **mount** it. A ship being mounted means that it has a presence on your Unix filesystem, allowing files to be shared between Unix and your ship. To mount your ship, type `|mount %` at the Dojo prompt.
92+To start your comet up again, run the following from your `urbit` directory (note the lack of `-c` argument):
12293
94+```sh
95+./urbit mycomet
12396```
124−|mount %
125−>=
126−```
127−
128−The `>=` output means that a command was successful. Now you can see your ship's files in its Unix directory.
12997
130−### Updating your comet
98+### Updating your comet {#updating}
13199
132100The Urbit binary comes with a somewhat recent release of the Urbit OS, but ships can update automatically ("over the air"), so new binaries aren't necessary every time it's updated. Planets have automatic updates enabled by default, but this is not the case for comets. Many comets are used only once and thrown away, so it would be wasteful to update every single comet as soon as it boots. If you plan to use your comet for more than a quick test, you'll probably want to ensure you're running the latest version of the OS.
133101
@@ -148,217 +116,133 @@ use |ota %disable or |ota ~sponsor %kids to reset it
148116>=
149117```
150118
151−### Using Landscape
152−
153−Landscape is the Urbit web interface, and it's the best way to interact with your ship. To access Landscape:
154−
155−1. Start your ship. In the boot messages, look for a line that says something like `http: live (insecure, public) on 80`. The number given is the port that your ship is using.
156−2. If the port given is 80, simply type `localhost` into your browser's address bar. If the given port is a different number, such as `8080`, you would type `localhost:8080`. You'll be met with a login prompt.
157−3. Type `+code` into your comet's Dojo. Copy-paste the returned code into the field asking for it in the browser page.
158−4. You're in! Now you can explore apps such as Chat, Publish, and more.
159−
160−### Join a group
161−
162−Now that you're on Landscape, join the Urbit Community, a great place for newcomers to ask questions.
163−
164−Click the 'Groups' button on your Landscape home page, and then click the `Join Group` column. Then, enter `~bitbet-bolbel/urbit-community` into the field and press the `Join Group` button.
119+Now that you’re up and running, skip ahead to the [Setup guide](#setup).
165120
166−From the Urbit Community group you can join a variety of chatrooms, notebooks, and collections.
121+## Booting a planet {#boot-your-planet}
167122
168−## Setting up a planet {#id}
123+There are two options for getting started with a planet. You can purchase one on your own and run Urbit yourself, or you can purchase a planet and hosting services through a [hosting provider](#hosting-providers).
169124
170−There are two options for getting started with a planet. You can purchase an Urbit ID on your own and run Urbit yourself, or you can purchase a planet and hosting services through a [hosting provider](#hosting-providers).
171125
172−### Acquire an Urbit ID
126+### Purchase a planet
173127
174−There are a few ways to get an Urbit ID:
128+There are a few ways to get your own planet:
175129
176130- Getting an invitation from a friend.
177−- Purchasing an Urbit ID, including hosting, from a [hosting provider](#hosting-providers) such as [geturbitid.com](https://www.geturbitid.com/).
178−- Manually setting up and hosting an Urbit ID purchased from a third party such as [urbit.live](https://urbit.live), [OpenSea](https://opensea.io), [planet.market](https://planet.market/), [urbit.me](https://urbit.me), [urth systems](https://urth.systems/), or [Urbit Marketplace](https://urbitmarketplace.com/).
131+- Purchasing a planet, including hosting, from a [hosting provider](#hosting-providers) such as [geturbitid.com](https://www.geturbitid.com/).
132+- Manually setting up and hosting an planet purchased from a third party such as [urbit.live](https://urbit.live), [OpenSea](https://opensea.io), [planet.market](https://planet.market/), [urbit.me](https://urbit.me), [urth systems](https://urth.systems/), or [Urbit Marketplace](https://urbitmarketplace.com/).
179133
180−Note that when you buy a planet, you should ensure with the provider that the star is operating. If you already have a planet and need to escape a non-operational star, see [Escaping A Sponsor](@/using/operations/using-your-ship.md#escape).
134+Note that when you buy a planet, you should ensure with the provider that your parent star is operating. If you need to escape a non-operational star, see [Escaping A Sponsor](@/using/operations/using-your-ship.md#escape).
181135
182136### Hosting Providers {#hosting-providers}
183137
184−Hosting providers will often sell you a planet and run your ship for you in a data center. This simplifies the process of setting up and maintaining your Urbit, but the service will probably cost a regular fee.
138+Hosting providers will often sell you a planet and run it for you. This option is very simple but will probably cost a regular fee.
185139
186−Urbit is designed to be portable. This means that if you sign up for hosting now but later want to cease service and run your Urbit yourself, you should be able to work with your hosting provider to obtain all of your data and boot your ship back up without losing anything.
140+Urbit is designed to be portable. This means that if you sign up for hosting now but later want to leave your hosting provider and run your Urbit yourself, you should be able to work with them to obtain all of your data and boot your planet back up without losing anything.
187141
188−Utilizing hosting does mean that you're trusting your provider with your data, but so long as you have an Urbit ID, you'll always own your identity.
142+Using hosting does mean that you're trusting your provider with your data, but so long as you have your planet, you'll always own your identity.
189143
190144Current hosting providers are:
191145
192146- [Tlon Corporation](https://tlon.io): Tlon is the creator of Landscape and is primarily responsible for the creation and maintenance of the Urbit project itself.
193147- [Get an Urbit ID](https://www.geturbitid.com/): Get an Urbit ID was the first hosting provider and is run by a member of the Urbit community.
194148
195−### About your Urbit ID wallet
196149
197−Your Urbit ID is yours. As long as you control its cryptographic secrets, nobody can take it away from you. That's why it's important to know a little bit about the cryptographic architecture of Urbit secrets.
150+### Choose to run your planet on your computer or on a cloud service
198151
199−Urbit ID secrets operate as a system of separate but hierarchically related Ethereum key-pairs. For any given ID, this system of key-pairs is referred to as a **Hierarchical Deterministic (HD) Wallet**. the Urbit HD wallet. Each of these Ethereum addresses have different powers over the same identity, from setting networking keys for communicating in the Urbit network to transferring ownership of identities. Important elements of the HD wallet:
152+Urbit must run on an existing computer somewhere. Most users run their planet on their personal computer, but we recommend eventually using a cloud service (Digital Ocean, Linode, etc) because it allows your planet to be accessed from anywhere on multiple devices. Hosting your planet in the cloud also allows it to always be online and ready for automatic updates. You are welcome to run from your personal computer and switch to the cloud later...all without losing any data!
200153
201−- **Master Ticket**: The "password" at the top of the hierarchy that determines the ownership. All other secrets are derived from this. If the rest of the wallet is lost or compromised, the master ticket can derive everything. You'll log into Bridge with this. Always keep your master ticket extremely safe.
202−
203−- **Management Proxy**: Derived from the master ticket. Can perform non-ownership related operations such as configuring Urbit OS networking keys.
204−
205−- **Keyfile**: Derived from the management proxy. Used as cryptographic proof that your Urbit ship is who it says it is. You use it to start up your ship for the first time.
154+There is a guide for [hosting your planet on DigitalOcean](@/using/operations/hosting.md) and [hosting your planet on Linode](https://jeremytunnell.com/2021/01/09/how-to-install-urbit-on-a-linode-vps), but any cloud hosting service should work.
206155
207156### Get your keyfile {#keyfile}
208157
209−As mentioned previously, there are a few ways to acquire a planet. All methods,
210−however, should result in you receiving at least one secret, such as a **master
211−ticket**. If you received an email invite to Urbit, the master ticket should be
212−a `.pdf` file in the passport folder inside the archive that you downloaded.
158+If you received an email invite to Urbit, the master ticket should be a .pdf file in the passport folder inside the archive that you downloaded. **If you bought your planet or someone sent you one you probably do not have a master ticket, and you probably don't need one. Do not issue a new master ticket unless you are sure you need to.**
213159
214−1. Connect to [Bridge](https://bridge.urbit.org).
215−2. Enter the name of your planet and the associated master ticket in the appropriate fields. Click the "Metamask, Mnemonic, Hardware Wallet..." button for alternate login methods if you don't have a master ticket.
160+1. Connect to [Bridge](https://bridge.urbit.org). (Bridge is like an Urbit wallet)
161+2. Enter the name of your planet and the associated master ticket if you have one. Click the "Metamask, Mnemonic, Hardware Wallet..." button if you don't have a master ticket.
2161623. Once you're logged in, click the "OS" option.
217−4. In resulting page, click the "Download Arvo Keyfile" button. You should
218− receive a `.key` file that contains the secret needed to boot your ship. Hold
219− onto this file. This may be grayed out if you are not using a master ticket.
220− If so, click on "Reset Networking Keys", then click on "Reset Networking Keys" on
221− the following page, validate the transaction using your wallet, and then
222− click Send Trasaction. Once the transaction is complete, the "Download Arvo
223− Keyfile" button should be available for you to press.
224−
225−### Choose to host or run your ship locally
163+4. Click the "Download Arvo Keyfile" button. If this is grayed out, click on "Reset Networking Keys", then click on "Reset Networking Keys" on the following page, validate the transaction using your wallet, and then click "Send Trasaction". Once the transaction is complete, the "Download Arvo Keyfile" button should be available for you to press. You should receive a `.key` file that contains the secret needed to boot your planet. Hold onto this file.
226164
227−There are two supported ways of running an Urbit ship: using a cloud service, or running it locally on your own machine. Most users run things locally at first, but we recommend eventually using a cloud service for Urbit because it allows your ship to be accessed from anywhere on multiple devices. Hosting your ship in the cloud also allows it to always be online and ready for OTA updates. It's technically possible to run your Urbit ship on a home server, but ISPs often restrict this to business plans and opening up your home network to the internet can be unsafe if done improperly.
165+### Run the boot command {#the-dojo}
228166
229−We 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.
167+Navigate to your `urbit` directory.
230168
231−### Boot your planet
232−
233−You'll be booting your ship with the keyfile that you downloaded from Bridge.
234−
235−#### Step 1: Find the path to your keyfile
236−
237−Find the absolute path to the keyfile that you downloaded from Bridge. Copy it.
238−
239−#### Step 2: Run the boot command
240−
241−Enter your `urbit` directory.
242−
243−Once you're inside, run the command below, except with `sampel-palnet` replaced by the name of your
244−Urbit identity, and `path/to/my-planet.key` replaced with the path to your keyfile:
245−
246−```sh
247−./urbit -w sampel-palnet -k path/to/my-planet.key
248−```
249−
250−Or, if you'd prefer to copy-paste your key, you can run:
169+Open your keyfile (it is just a text file) and copy the key inside. Paste it into the following command, with `sampel-palnet` replaced by the name of your
170+planet.
251171
252172```sh
253173./urbit -w sampel-palnet -G rAnDoMkEy
254174```
255175
256−Either command will create a directory called `sampel-palnet/` and begin building your ship. It may take a few minutes.
257−
258−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.
259−
260−To shut down your ship, use `Ctrl-D`. To start your ship up again, run the following from your `urbit` directory:
176+Or you can copy the keyfile into the current directory and run:
261177
262178```sh
263−./urbit sampel-palnet
179+./urbit -w sampel-palnet -k ./my-planet.key
264180```
265181
266−Note that `sampel-palnet/` is the path of a folder, which we just created in your `urbit` directory. This folder is called your ship's **pier**.
267−
268−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.
182+Either command will create a directory called `sampel-palnet/` and begin booting your planet. It may take a few minutes.
269183
270−**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).
184+When your planet is finished booting, you will see `~sampel-palnet:dojo>` (Dojo: the Urbit command line).
271185
272−Delete the keyfile with the command below:
186+Get your password to log into landscape (the Urbit web interface) by typing:
273187
274188```sh
275−rm path/to/my-planet.key
276−```
277−
278−### Updating to the latest binary {#updating}
279−
280−Most 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).
281−
282−To update to the latest binary, download and extract it to replace your existing one. Then run it as before.
283−
284−First shut down your ship, by running the following in dojo (or with `Ctrl-D`).
285−```
286−|exit
189++code
287190```
288191
289−Next download and extract the most recent binary from inside your `urbit` directory:
290−```sh
291−#macOS:
292−curl -JLO https://urbit.org/install/mac/latest
293−tar zxvf ./darwin.tgz --strip=1
294−
295−#Linux:
296−wget --content-disposition https://urbit.org/install/linux64/latest
297−tar zxvf ./linux64.tgz --strip=1
298−```
192+To shut down your planet, use `Ctrl-D`.
299193
300−**NOTE**: Do not delete the directory named after your ship. Your ship itself can be reused, only the binary needs to be changed. This is why we have the directory structure configured as an `urbit` directory that contains your ship and your binary. This structure makes it easy to swap in new binaries.
194+To start your planet up again, run the following from your `urbit` directory.
301195
302−Start up your ship with the new binary from your `urbit` directory:
303196```sh
304197./urbit sampel-palnet
305198```
306199
307−Then you're good to go!
308−
309−### Breaches {#breaches}
310−
311−An important concept on the Urbit network is that of continuity. Continuity refers to how ships remember the order of their own network messages and the network messages of others — these messages are numbered, starting from zero. A breach is when ships on the network agree to forget about this sequence and treat one or more ships like they are brand new.
200+Note that `sampel-palnet/` is the path of a folder, which we just created in your `urbit` directory. This folder is called your planet's **pier**, and it holds all of your data.
312201
313−There are two kinds of breaches: personal breaches and network breaches.
202+Never boot multiple instances of your planet at the same time. You can prevent this from happening on accident by only ever keeping a single copy of your pier.
314203
315−A personal breach can fix many problems with your ship, but should be used as a last resort. A network breach happens when there's a major software update and you must download a new binary.
204+**Important:** once a key has been used to boot a planet onto the network, it cannot be used to boot that planet again later - doing so will cause communication problems with other planets. For this reason you should **delete the keyfile from your machine once your planet has booted successfully**. If you do use the same key twice, you'll need to reset your planet to restore its functionality.
316205
317−For details on breaching, please read the [Guide to Breaches](@/docs/tutorials/guide-to-breaches.md) documentation.
318−
319−## Running a star or galaxy {#supernode}
320−
321−Setting up and running a star or galaxy is a little bit different from setting up and running a planet.
322−
323−### Getting a star or galaxy
324−
325−Stars are valuable cryptographic assets. They can be bought in one of two ways.
326−
327−- Transacting privately with a star owner.
328−- Buying a star on a marketplace like [OpenSea](https://opensea.io/collection/urbit-id)
206+Delete the keyfile with the command below:
329207
330−Galaxies are rare and extremely valuable, meaning that there is no liquid market for them. If you want to buy a galaxy, you'll have to find an individual galaxy owner and transact with them.
208+```sh
209+rm ./my-planet.key
210+```
331211
332−### A note on security
212+## Setup {#setup}
333213
334−As mentioned before, stars are valuable. You are solely responsible for safeguarding your seeds and secret keys, and arming yourself with the computer-security knowledge that is attendant upon that safeguarding. You act at your own risk in reliance upon the contents of the manual. In no way is the Tlon Corporation responsible for the actions, decisions, or other behavior taken or not taken by you in reliance upon this manual.
214+The first thing you generally want to do with a new planet is to **mount** it. A planet being mounted means that it can be seen by Linux, allowing files to be shared between it and your planet. To mount your planet, type `|mount %` at the Dojo prompt.
335215
336−It’s a good idea to store your keys redundantly in case one method fails. If you deem a key to be valuable enough, you can shard it into thirds and store each third in secure, geographically distributed locations. Consider these storage media options:
216+```
217+|mount %
218+>=
219+```
337220
338−- Storing the secret on a hardware wallet that is never connected to a networked machine.
339−- There are products that let you store the key on steel. This medium is resistant to both water damage and fire damage.
221+The `>=` output means that a command was successful. Now you can see your planet's files in its directory.
340222
341−### Getting a star's keyfile
223+To understand what happened with this command, read more about Urbit’s filesystem (called “clay”) [here](@/docs/tutorials/arvo/clay.md).
342224
343−1. Connect to [Bridge](https://bridge.urbit.org).
344−2. Enter the name of your star and the associated master ticket in the appropriate fields. Click the "Metamask, Mnemonic, Hardware Wallet..." button for alternate login methods if you don't have a master ticket.
345−3. Once you're logged in, click the "OS" option.
346−4. In resulting page, click the "Download Arvo Keyfile" button. You should receive a `.key` file that contains the secret needed to boot your ship. Hold onto this file.
225+### Using Landscape
347226
348−### Boot your star
227+Landscape is the Urbit web interface, and it's the best way to interact with your planet. To access Landscape:
349228
350−Because of their need for near-perfect uptime Stars should be hosted on cloud services. We have a guide for [hosting on DigitalOcean](@/using/operations/hosting.md), but any cloud provider should work.
229+1. Start your planet. In the boot messages, look for a line that says something like `http: live (insecure, public) on 80`. The number given is the port that your planet is using.
230+2. If the port given is 80, simply type `localhost` into your browser's address bar. If the given port is a different number, such as `8080`, you would type `localhost:8080`. You'll be met with a login prompt.
231+3. Type your password you got from running `+code` above.
232+4. You're in! Now you can explore groups, join chat channels, share links, and much more.
351233
352−Being an infrastructure node, a star has certain responsibilities to the Urbit network.
234+### Join a group
353235
354−By default, your star accepts software updates from its galaxy and routes them to its planets. You can use this mechanism to push custom software to your planets. Keep in mind that planets expect functional, non-breaking software updates, and generally want to be able to communicate with planets that are sponsored by other stars.
236+Now that you're on Landscape, join the Urbit Community, a great place for newcomers to ask questions.
355237
356−To ensure new planets can connect to your ship, users are expected to participate in network-wide breaches by updating to the latest Urbit version, 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.
238+Click the `Join a Group` button, then enter `~bitbet-bolbel/urbit-community` into the field and press the `Join Group` button.
357239
358−Network-wide breaches are distinct from personal breaches, wherein an individual ship cycles its personal network keys using bridge.
240+From the Urbit Community group you can join a variety of chatrooms, notebooks, and collections.
359241
360−See our [Guide to Breaches](@/docs/tutorials/guide-to-breaches.md) for more information and for instructions on breaching.
242+### Next Steps
361243
362−### Running a galaxy
244+Now that you’re up and running, take some time to deepen your understanding by checking out some of our other guides:
363245
364−A galaxy is at the top of the hierarchy in terms of importance. Thus, if you're interested in running one, please contact support@urbit.org, and we will give you personalized assistance in getting set up.
246+- [Host your Ship in the Cloud](@/using/operations/hosting.md): Follow this guide to set your ship up to run as a cloud server, accessible from anywhere.
247+- [Read the Operations Manual](@/using/operations/using-your-ship.md): Become an expert pilot by learning to use your ship.
248+- [Learn to Develop on Urbit](@/using/develop.md): Learn how to contribute to or develop on Urbit.