on master help sign in
Merge pull request #1750 from urbit/restructure-getting-started

Restructure getting started

commit43400af24f9d7f9687daa6bfac3a8f9f9e59dfa8 authorGordon <gordon.cieplak@urbit.org> dateTue 23 Aug 2022, 18:07 (4 years ago) parentd4afcfac92dab5
5 files changed+233−278
content/getting-started/cli.md+147−76 content/getting-started/get-planet.md+46−3 content/getting-started/server.md−164 pages/getting-started/[[...slug]].js+36−35 vercel.json+4
content/getting-started/cli.md+147−76
@@ -1,11 +1,21 @@
11+++
2−title = "Command line install"
3−weight = 4
2+title = "Command line app"
3+weight = 2
44description = "Installation instructions for power users."
5−tag = "additional"
65+++
76
8−If you're a power user, you can run the Urbit virtual machine directly using the command line. Choose the code for your operating system and run the commands in your terminal.
7+If you're a power user, you can run the Urbit virtual machine directly using the
8+command line. This can be run on your local machine or a server in the cloud, we
9+just cover the general case here.
10+
11+Note there is a much more comprehensive [cloud hosting
12+guide](https://operators.urbit.org/manual/running/hosting) which walks through
13+setting up Urbit on a [Digital Ocean](https://www.digitalocean.com/) VPS.
14+
15+### 1. Install Urbit
16+
17+Choose your operating system and run the given command in your terminal to
18+download the Urbit runtime:
919
1020{% tabs %}
1121
@@ -15,12 +25,12 @@ If you're a power user, you can run the Urbit virtual machine directly using the
1525curl -L https://urbit.org/install/mac/latest | tar xzk --strip=1 && ./urbit
1626```
1727
18−Note our Mac build is only compatible with Apple Silicon (M1/M2) via Rosetta.
19−If you have such a machine you must run the following command:
20−
21−```
22−/usr/sbin/softwareupdate --install-rosetta --agree-to-license
23−```
28+> Note our Mac build is only compatible with Apple Silicon (M1/M2) via Rosetta.
29+> If you have such a machine you may need to run the following command:
30+>
31+> ```
32+> /usr/sbin/softwareupdate --install-rosetta --agree-to-license
33+> ```
2434
2535{% /tab %}
2636
@@ -30,12 +40,13 @@ If you have such a machine you must run the following command:
3040curl -L https://urbit.org/install/linux64/latest | tar xzk --strip=1 && ./urbit
3141```
3242
33−Linux users may need to run this command in another terminal window to access your Urbit on port 80:
34−
35−```shell
36−sudo apt-get install libcap2-bin
37−sudo setcap 'cap_net_bind_service=+ep' ./urbit
38−```
43+> Linux users may need to run this command in another terminal window to access
44+> your urbit on port 80:
45+>
46+> ```shell
47+> sudo apt-get install libcap2-bin
48+> sudo setcap 'cap_net_bind_service=+ep' ./urbit
49+> ```
3950
4051{% /tab %}
4152
@@ -45,12 +56,12 @@ sudo setcap 'cap_net_bind_service=+ep' ./urbit
4556curl -L https://urbit.org/install/windows/latest | tar -xzkf - --strip-components=1 && urbit
4657```
4758
48−Windows 10 build 17063 and later includes the familiar `curl` and `tar`
49−command-line tools. If you're running an older version of Windows, you may need
50−to visit
51−[https://github.com/urbit/urbit/releases/latest](https://github.com/urbit/urbit/releases/latest)
52−in the browser, download the `windows.zip` file, extract it and execute the
53−contained `urbit.exe` file in the command prompt.
59+> Windows 10 build 17063 and later includes the familiar `curl` and `tar`
60+> command-line tools. If you're running an older version of Windows, you may need
61+> to visit
62+> [https://github.com/urbit/urbit/releases/latest](https://github.com/urbit/urbit/releases/latest)
63+> in the browser, download the `windows.zip` file, extract it and execute the
64+> contained `urbit.exe` file in the command prompt.
5465
5566{% /tab %}
5667
@@ -62,99 +73,159 @@ If successful, you will see a block of output beginning with the line:
6273Urbit: a personal server operating function
6374```
6475
65−### Booting a free identity {% #comet %}
76+### 2. Boot Urbit
6677
67−There are two parts to Urbit: an **ID** and an **Operating System**.
78+An Urbit instance is intrinsically tied to a unique identity called an **Urbit
79+ID**. There are five classes of Urbit ID, but we will consider two here: comets
80+and planets.
6881
69−You have just installed the Operating System on your computer.
82+- **Comet:** A comet is an identity which anyone can generate themselves, for
83+ free. It's a good option to try out Urbit. Comets are limited by the fact they
84+ cannot be "factory reset", meaning if your urbit somehow becomes broken or
85+ corrupted then you'll have to start again with a new identity. In that sense,
86+ they are impermanent.
7087
71−The **ID** is similar to a username and password on another site. The difference is that the public part (the username) is verified by thousands of people around the world while only you hold the key (the password) to that ID.
88+- **Planet:** A planet is a permanent identity which you own forever. Planets
89+ are the class intended for individuals. While there are essentially an
90+ unlimited number of comets, planets are more scarce (preventing spamming,
91+ among other things). This scarcity means they usually aren't free (though
92+ sometimes nice people give them away). This guide will assume you've already
93+ acquired a planet. If you haven't, you can refer to the ["Get a planet"
94+ guide](https://urbit.org/getting-started/get-planet) before continuing.
7295
73−There are five kinds of Urbit IDs but to get started you only need to know about two: we call them **planets** and **comets**.
96+Follow the instructions for your case:
7497
75−---
98+{% tabs %}
7699
77−**Planets** are scarce (this prevents spamming, among other things) and usually require a price to acquire. This is the recommended way to run Urbit, but it's a bit more involved.
100+{% tab label="Boot a Comet" %}
78101
79−A planet name looks like `~sampel-palnet`.
102+In the terminal, with the `urbit` binary you installed in the previous step, a
103+comet can be booted with the `-c` option:
80104
81−[Follow this guide](/getting-started/) if you have already acquired a planet.
105+```bash
106+./urbit -c mycomet
107+```
82108
83−[Find a planet to purchase](/getting-started/get-planet)
109+> `mycomet` will be the name given to the data folder it will create. You can
110+> choose any name you like.
84111
85−---
112+It may take a while to initialize the comet (usually only a couple of minutes,
113+but it could take longer). When it's done, it'll take you to the dojo prompt
114+(the dojo is Urbit's shell):
86115
87−**Comets** are practically unlimited and free to acquire. At present, these are a great way to try out the network for free.
116+```
117+ames: live on 31337
118+http: web interface live on http://localhost:8080
119+http: loopback live on http://localhost:12321
120+~sampel_marzod:dojo>
121+```
88122
89−A comet name looks like `~dasres-ragnep-lislyt-ribpyl--mosnyx-bisdem-nidful-marzod`.
123+You can shut down the comet again by typing `|exit` in the dojo or hitting
124+`Ctrl+D`. When it's first shut down, the runtime will be copied inside the data
125+folder, so you can start it up again by doing:
90126
91−[Read more about Urbit ID here](/understanding-urbit/urbit-id)
127+```bash
128+./mycomet/.run
129+```
92130
93−---
131+Since comets are often used temporarily and then discarded, kernel updates are
132+not enabled by default. If you plan to use your comet for a while, it's a good
133+idea to enable updates with the following command in the dojo:
94134
95−To boot a comet, go into the command line and run the following command:
135+```
136+|ota (sein:title our now our)
137+```
96138
97−```sh
98−./urbit -c mycomet
139+Lastly, while the dojo is quite powerful, most people use their urbit via
140+Landscape, the browser-based UI. In order to access Landscape, you need your web
141+login code. You can get this by running the following command in the dojo:
142+
143+```
144++code
145+```
146+
147+It'll spit out a code that'll look something like `lidlut-tabwed-pillex-ridrup`.
148+Copy the code it gives you to the clipboard.
149+
150+{% /tab %}
151+
152+{% tab label="Boot a Planet" %}
153+
154+In order to boot a planet, you need a copy of its private keys. If you got your
155+planet via a claim link, the passport backup `.zip` file you downloaded will
156+contain a file called something like `sampel-palnet-1.key`. If you don't have
157+the passport backup or you got your planet by another method, you can instead
158+login to [Bridge](https://bridge.urbit.org/), select your planet, go to the OS
159+section, and hit the "Download Keyfile" button.
160+
161+Back in the terminal, with the `urbit` binary you installed in the previous
162+step, you can boot your planet with the following command (replacing
163+`sampel-palnet` with your own planet and pointing to the location of your
164+keyfile):
165+
166+```bash
167+./urbit -w sampel-palnet -k sampel-palnet-1.key
99168```
100169
101−It may take a while to load the comet (probably only take a few minutes, but it could take longer). This comes along with it being free. When it's done you'll some messages ending like this:
170+This will create a data folder with the name of your planet and begin booting.
171+It may take a while to initialize the planet (usually only a couple of minutes,
172+but it could take longer). When it's done, it'll take you to the dojo prompt
173+(the dojo is Urbit's shell):
102174
103175```
104176ames: live on 31337
105177http: web interface live on http://localhost:8080
106178http: loopback live on http://localhost:12321
107−~sampel_marzod:dojo>
179+~sampel-palnet:dojo>
108180```
109181
110−When your comet is finished booting, you will see `~sampel_marzod:dojo>` (Dojo: the Urbit command line).
182+You can shut down the planet again by typing `|exit` in the dojo or hitting
183+`Ctrl+D`. When it's first shut down, the runtime will be copied inside the data
184+folder, so you can start it up again by doing:
111185
112−To exit Urbit, use `Ctrl-D` or enter `|exit` into Dojo.
113−
114−To start your comet up again, run the following command:
115−
116−```sh
117−./mycomet/.run
186+```bash
187+./sampel-palnet/.run
118188```
119189
120−### Using the web interface
190+While the dojo is quite powerful, most people use their urbit via Landscape, the
191+browser-based UI. In order to access Landscape, you need your web login code.
192+You can get this by running the following command in the dojo:
121193
122−Urbit is an entirely new computer, so by default it drops you into the "dojo," which is its terminal. Like your current computer, it can be used to do just about anything if you know the right commands. You only need to know one command for now.
194+```
195++code
196+```
123197
124−At the moment, the most common way to use Urbit is by launching apps like Groups (a communications suite) from the web interface homescreen. The web interface allows you to use your ship without touching the terminal. You just need to get the password, or `code`, from the terminal.
198+It'll spit out a code that'll look something like `lidlut-tabwed-pillex-ridrup`
199+(note this is a separate code to your master ticket). Copy the code it gives you
200+to the clipboard.
125201
126−1. With your Urbit running, look for a line that says something like `http: web interface live on http://localhost:8080`. The number given is the port that your ship is using. It will most likely be 80 or 8080, but we're just making sure.
127−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.
128−3. In the window where you found the port number, type `+code` and press return. Copy-paste the code that appears into the "Access Key" field in the browser, and press continue.
129−4. Once in, take a look around and try launching an app like Groups.
202+One last thing: The `sampel-palnet-1.key` keyfile is only needed once, when you
203+first boot your planet. Now that it's booted, it's good security practice to
204+delete that keyfile.
130205
131−## Next Steps
206+{% /tab %}
132207
133−### Updating your comet {% #updating %}
208+{% /tabs %}
134209
135−Urbit comes with a recent release of the Urbit OS, but automatic updates of the `%base` desk (which contains the kernel of the OS) are not enabled by default 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.
210+### 3. Login
136211
137−You can enable updates for your comet by typing `|ota (sein:title our now our)` into Dojo and pressing Enter.
212+While your urbit is running, the web interface called *Landscape* can be
213+accessed in the browser. Its URL will usually be either `localhost` or
214+`localhost:8080`, depending on your platform. To check the address, you can look
215+at the boot messages in the terminal. You should see a line like:
138216
139217```
140−> |ota (sein:title our now our)
141−>=
142−kiln: activated install into %base from [~samzod %kids]
143−kiln: downloading update for %base from [~samzod %kids]
218+http: web interface live on http://localhost:8080
144219```
145220
146−### Read More about the Dojo {% #the-dojo %}
147−
148−The dojo is Urbit's command line. You can use it to control your ship, or to execute arbitrary code. Check out the links below for more information.
149−
150−- [Basic Operations](/using/os/getting-started)
151−- [Basic Hoon](/docs/tutorials/hoon/hoon-school/setup)
152−- [Glossary Entry](/docs/glossary/dojo)
153−
154−### Purchase a Permanent Identity {% #boot-your-planet %}
221+Whichever address and port it says there is the one to open in the browser.
155222
156−You can continue using this comet indefinitely. There are currently few differences between using a comet-level identity and a planet-level one. However, some groups will not allow comets entry in order to maintain a certain level of quality, and changes may be made in the future that further devalue comets. They will always, however, be able to access the basic functions of the network.
223+Once open, you'll be presented with the login screen. Paste in the web login
224+code you copied from the dojo in the previous step and hit "continue". You'll
225+now be taken to your homescreen, with tiles for the default apps such as Groups
226+and Terminal.
157227
158−A comet also comes with a long and fairly unmemorable name whereas a planet has a short name and a "sigil" (avatar) associated with it that makes it more identifiable on the network. You may notice all this within the first few minutes of using Urbit.
228+### Next steps
159229
160−[For details of how to purchase a planet, visit this page](/getting-started/get-planet).
230+Learn how to [get around your
231+urbit](https://urbit.org/getting-started/getting-around).
content/getting-started/get-planet.md+46−3
@@ -68,14 +68,57 @@ Learn more about [layer 2 for planets](/using/id/layer-2-for-planets) in the Use
6868
6969{% /callout %}
7070
71+
72+### Claiming your planet
73+
74+An invitation to claim your planet comes in one of two forms.
75+
76+The first is an email invitation with an Urbit ID and a Master Ticket.
77+
78+The second, only recently made available through our [L2 solution](/using/id/layer-2-for-planets), is an activation code or a link to activate on [Bridge](https://bridge.urbit.org), which can be thought of as an Urbit account management tool.
79+
80+![](https://media.urbit.org/site/getting-started/Server-setup-1.jpg)
81+
82+Clicking a link to activate a planet on Bridge will take you to page which will generate a Master Ticket for you. Follow the instructions which will prompt you to download a copy of your Passport: your Master Ticket, management proxy, and keyfile. Store your Master Ticket and management proxy somewhere safe, hold on to the keyfile, and proceed to the next step.
83+
84+{% callout %}
85+
86+**Claiming L1 planets**
87+
88+If you’ve purchased an L1 planet, you won’t need to claim it because you already own it as an NFT. Simply log into Bridge using Metamask or your wallet of choice.
89+
90+{% /callout %}
91+
92+
93+### Using Bridge to get your keyfile
94+
95+Now that you have your planet, you can create your keyfile (eg. `sample-palnet.key`), which is the cryptographic signature required to encrypt and decrypt messages on Urbit's P2P network.
96+
97+- **Claimed L2 planets**
98+ If you’ve claimed your L2 Planet then you should already have downloaded your Passport, which contains your Master Ticket and keyfile.
99+
100+- **Master Ticket holders**
101+ If you haven’t downloaded your Passport but have a Master Ticket, then you can simply log in with Bridge using the Master Ticket option with your planet name and Master Ticket password. Click the ID box near the bottom of the page to open the ID page, then click the **Download Passport** button, which contains your keyfile.
102+
103+- **L1 Planet Purchasers**
104+ Log in to Bridge with your Ethereum wallet using Metamask or the wallet of your choice with WalletConnect. Click the “OS” box on the bottom of the page to open the OS page, and then click the **Download Keyfile** button.
105+
106+
71107### Next steps
72108
73109Got your planet?
74110
75−Get your planet [set it up locally with Port](/getting-started/desktop).
111+Get it up and running with one of these options:
112+
113+- Let a [hosting provider](/getting-started/hosted) do the hard work for you.
114+
115+- [Try Port](/getting-started/desktop), the user-friendly desktop app.
76116
77−Read the [Server setup](/getting-started/server) guide to learn how to get it set up on a server.
117+- For power users, check out the [command line install
118+ guide](/getting-started/cli) and run your urbit from the terminal.
78119
79−Or, follow the instructions of a [hosting provider](/getting-started/hosted) and set up your planet there.
120+- If you have a bit of Linux server experience, the [cloud hosting
121+ guide](https://operators.urbit.org/manual/running/hosting) will help you set
122+ up Urbit on a Digital Ocean VPS, so you can access it from anywhere.
80123
81124Remember, your planet is yours and you can always change how you run your urbit in the future.
content/getting-started/server.mddeleted−164
@@ -1,164 +0,0 @@
1−+++
2−title = "Server setup"
3−description = "Run urbit on a local or cloud server"
4−weight = 2
5−+++
6−
7−### 1. Get yourself a planet
8−
9−Here's some of the hard fun work we talked about earlier.
10−
11−There are two ways to get a planet.
12−
13−**A) Ask nicely**
14−
15−Visit the instructions for [launching a temporary comet with Port](/getting-started/desktop), get yourself onto the network, find a group, and start conversations with people with planets to spare. Many urbiters are also active on [Twitter](https://twitter.com), where you can also ask around.
16−
17−**B) Buy a planet**
18−
19−There are many markets and individuals selling planets such as [azimuth.shop](https://azimuth.shop), [Networked Subject](https://subject.network), and [Wexpert Systems](https://wexpert.systems) for Ethereum, Bitcoin, and USD respectively.
20−
21−{% callout %}
22−
23−**Layer 1 vs Layer 2 planet purchasing**
24−
25−The websites listed in B) sell Layer 2 (L2) planets -- which means they avoid Ethereum’s volatile and expensive gas fees. However, markets such as [OpenSea](https://opensea.io) and many Urbit-specific markets such as [Urbitex](https://urbitex.io) sell planets directly on Ethereum L1, which means they are significantly more expensive.
26−
27−For this reason we generally advise using a L2 planet market, unless you are interested in a very rare sigil or a particular planet name.
28−
29−{% /callout %}
30−### 2. Claim your planet
31−
32−An invitation to claim your planet comes in one of two forms.
33−
34−The first is an email invitation with an Urbit ID and a Master Ticket.
35−
36−The second, only recently made available through our [L2 solution](/using/id/layer-2-for-planets), is an activation code or a link to activate on [Bridge](https://bridge.urbit.org), which can be thought of as an Urbit account management tool.
37−
38−![](https://media.urbit.org/site/getting-started/Server-setup-1.jpg)
39−
40−Clicking a link to activate a planet on Bridge will take you to page which will generate a Master Ticket for you. Follow the instructions which will prompt you to download a copy of your Passport - your Master Ticket, management proxy, and keyfile. Store your Master Ticket and management proxy somewhere safe, hold on to the keyfile, and proceed to the next step.
41−
42−{% callout %}
43−
44−**Claiming L1 planets**
45−
46−If you’ve purchased an L1 planet, you won’t need to claim it because you already own it as an NFT. Simply log into Bridge using Metamask or your wallet of choice.
47−
48−{% /callout %}
49−### 3. Use Bridge to get your keyfile
50−
51−Now that you have your planet, you can create your keyfile (eg. `sample-palnet.key`), which is the cryptographic signature required to encrypt and decrypt messages on Urbit's P2P network.
52−
53−- **Claimed L2 planets**
54− If you’ve claimed your L2 Planet then you should already have downloaded your Passport, which contains your Master Ticket and keyfile.
55−
56−- **Master Ticket holders**
57− If you haven’t downloaded your Passport but have a Master Ticket, then you can simply log in with Bridge using the Master Ticket option with your planet name and Master Ticket password. Click the ID box near the bottom of the page to open the ID page, then click the **Download Passport** button, which contains your keyfile.
58−
59−- **L1 Planet Purchasers**
60− Log in to Bridge with your Ethereum wallet using Metamask or the wallet of your choice with WalletConnect. Click the “OS” box on the bottom of the page to open the OS page, and then click the **Download Keyfile** button.
61−
62−### Install Urbit via the command line
63−
64−These instructions assume you have access to a **remote Linux system** running on a **VPS or cloud provider** of your choice. If you want to run Urbit locally, whether on Linux, macOS, or Windows, click the appropriate section below.
65−
66−You may also want to see the cloud hosting guide for additional details like setting your domain name and establishing a firewall, but for now, we'll focus on getting you set up as soon as possible.
67−
68−Download Urbit with the following commands:
69−
70−{% tabs %}
71−
72−{% tab label="MacOS" %}
73−
74−```bash
75−curl -L https://urbit.org/install/mac/latest | tar xzk --strip=1 && ./urbit
76−```
77−
78−Note our Mac build is only compatible with Apple Silicon (M1/M2) via Rosetta.
79−If you have such a machine you must run the following command:
80−
81−```
82−/usr/sbin/softwareupdate --install-rosetta --agree-to-license
83−```
84−
85−{% /tab %}
86−
87−{% tab label="Linux" %}
88−
89−```shell
90−curl -L https://urbit.org/install/linux64/latest | tar xzk --strip=1 && ./urbit
91−```
92−
93−Linux users may need to run this command in another terminal window to access your Urbit on port 80:
94−
95−```shell
96−sudo apt-get install libcap2-bin
97−sudo setcap 'cap_net_bind_service=+ep' ./urbit
98−```
99−
100−{% /tab %}
101−
102−{% tab label="Windows" %}
103−
104−```winbatch
105−curl -L https://urbit.org/install/windows/latest | tar -xzkf - --strip-components=1 && urbit
106−```
107−
108−Windows 10 build 17063 and later includes the familiar `curl` and `tar`
109−command-line tools. If you're running an older version of Windows, you may need
110−to visit
111−[https://github.com/urbit/urbit/releases/latest](https://github.com/urbit/urbit/releases/latest)
112−in the browser, download the `windows.zip` file, extract it and execute the
113−contained `urbit.exe` file in the command prompt.
114−
115−{% /tab %}
116−
117−{% /tabs %}
118−
119−Next, transfer `your-keyfile.key` to your server using scp or an FTP client.
120−
121−Now you can run Urbit for the first time. Run the below command, replacing ames_port with a public port number between 49152 to 65535, sampel-palnet with the name of your planet, and sampel-palnet.key with the name of your keyfile.
122−
123−```sh
124−./urbit -p ames_port -w sampel-palnet -k sampel-palnet.key
125−```
126−
127−Arvo, the Urbit OS, now creates a directory called `sampel-palnet/` and begins booting your planet and establishing connections with the P2P network. When that's finished, you'll see Dojo, the Urbit command line:
128−
129−```
130−~sampel-palnet:dojo>
131−```
132−
133−Welcome to Urbit! You can skip ahead to [log in](#log-in), or stick around for some tips.
134−
135−### 4. Tips
136−
137−Check out the [cloud hosting guide](/using/running/hosting) for tips on improving the environment for Urbit, with a particular focus on establishing your domain name and using SSL for encryption.
138−
139−Shut down your planet by typing Ctrl+D into Dojo.
140−
141−The `urbit` binary will have automatically "docked" with your pier, copying
142−itself inside so a separate binary isn't necessary. To boot your planet up
143−again, run `./sampel-palnet/.run -p ames_port`, once again replacing
144−`ames_port` with the port you used previously.
145−
146−Your planet's folder, `sampel-palnet/`, is called your pier, and it holds all your data. If you want to migrate your data from one system to another, you must bring your pier.
147−
148−You should also delete your keyfile from your remote system to prevent yourself from using the same key twice, which will cause communication problems with other planets.
149−
150−```sh
151−rm your-keyfile.key
152−```
153−
154−### 5. Log in
155−
156−First, use your browser to navigate to the URL+port where your ship is running. This could be an IP address or a fully-qualified domain name, depending on how you set yours up.
157−
158−Instead of a static password, Urbit uses an Access Key, which is given by your ship itself.
159−
160−Open up the Urbit CLI again if it's not still running, and enter +code. The output is your Access Key, which you need to copy and paste into your browser. Click Continue to finish authentication and log in.
161−
162−### Next steps
163−
164−Learn how to [get around your urbit](/getting-started/getting-around).
pages/getting-started/[[...slug]].js+36−35
@@ -148,40 +148,6 @@ function LaunchCards() {
148148 ),
149149 href: "/getting-started/desktop",
150150 },
151− {
152− title: "Server setup",
153− subtitle: "Deploy Urbit on a cloud/VPS provider",
154− points: [
155− {
156− title: "Benefits",
157− content: ["Complete data ownership", "Accessibility from anywhere"],
158− },
159− {
160− title: "Considerations",
161− content: [
162− "Requires monthly cloud service subscription & (one-time) Urbit ID purchase",
163− "Requires Linux proficiency",
164− ],
165− },
166− ],
167− svg: (
168− <svg
169− width="50"
170− height="50"
171− viewBox="0 0 61 45"
172− fill="none"
173− xmlns="http://www.w3.org/2000/svg"
174− >
175− <path
176− fill-rule="evenodd"
177− clip-rule="evenodd"
178− d="M49.2551 15.2806C49.5291 16.4304 50.4122 17.3353 51.5533 17.636H51.5527C54.4975 18.5808 57.035 20.4998 58.7427 23.0815C60.4504 25.6633 61.227 28.7507 60.9424 31.8327C60.5301 35.2182 58.8836 38.3348 56.3195 40.5811C53.7554 42.8274 50.4492 44.0491 47.0418 44.0118H35.4601V35.1486H38.0641C38.8723 35.1521 39.6109 34.7022 39.9547 33.9966C40.2985 33.2909 40.1869 32.4547 39.6658 31.8567L32.0952 23.1122C31.6983 22.657 31.1132 22.3924 30.4969 22.3924C29.8807 22.3924 29.2955 22.657 28.8987 23.1122L21.3337 31.8567C20.8144 32.4547 20.701 33.2874 21.0448 33.9948C21.3867 34.7005 22.1237 35.1503 22.9301 35.1486H25.5414V44.0118H13.9581C10.5508 44.049 7.24457 42.8274 4.68045 40.5811C2.11627 38.3347 0.469828 35.2181 0.057545 31.8327C-0.227016 28.7505 0.549654 25.6631 2.25729 23.0815C3.9652 20.4998 6.50276 18.5808 9.44724 17.636C10.5883 17.3353 11.4714 16.4304 11.7454 15.2806C12.9452 9.48101 16.7593 4.5598 22.0737 1.9542C27.3911 -0.651399 33.6097 -0.651399 38.9268 1.9542C44.2412 4.56034 48.0555 9.48122 49.2551 15.2806Z"
179− className="fill-wall-600"
180− />
181− </svg>
182− ),
183− href: "/getting-started/server",
184− },
185151 {
186152 title: "Hosted urbit",
187153 subtitle: "Deploy Urbit on a managed service",
@@ -234,7 +200,42 @@ function LaunchCards() {
234200 />
235201 </svg>
236202 ),
237− href: "/getting-started/hosted",
203+ href: "https://operators.urbit.org/manual/running/hosting",
204+ },
205+ {
206+ title: "Command line app",
207+ subtitle: "Run Urbit from the terminal",
208+ points: [
209+ {
210+ title: "Benefits",
211+ content: ["Greater control", "Reliable", "Smaller footprint"],
212+ },
213+ {
214+ title: "Considerations",
215+ content: [
216+ "Requires familiarity with the command line",
217+ ],
218+ },
219+ ],
220+ svg: (
221+ <svg
222+ width="55"
223+ height="55"
224+ viewBox="0 0 66 50"
225+ fill="none"
226+ xmlns="http://www.w3.org/2000/svg"
227+ >
228+ <path
229+ fill-rule="evenodd"
230+ clip-rule="evenodd"
231+ d="M52.9288 0.03125H3.07125C1.39393 0.03125 0.03125 1.39393 0.03125 3.07125V52.9288C0.03125 53.7333 0.351879 54.5081 0.921894 55.0781C1.49191 55.6481 2.26671 55.9688 3.07125 55.9688H52.9288C53.7333 55.9688 54.5081 55.6481 55.0781 55.0781C55.6481 54.5081 55.9688 53.7333 55.9688 52.9288V3.07125C55.9688 2.26671 55.6481 1.49189 55.0781 0.921894C54.5081 0.351894 53.7333 0.03125 52.9288 0.03125V0.03125ZM12.8 38.7912L20.78 30.7368L12.8 22.7568L17.1314 18.4254L27.2402 28.6079C27.8191 29.1779 28.1456 29.9586 28.1456 30.7721C28.1456 31.5885 27.8191 32.3693 27.2402 32.9393L17.0577 43.0481L12.8 38.7912ZM38.9425 43.1226H27.0113V37.0426H38.8688L38.9425 43.1226Z"
232+ className="fill-wall-600"
233+ />
234+
235+
236+ </svg>
237+ ),
238+ href: "/getting-started/cli",
238239 },
239240 ];
240241 return (
vercel.json+4
@@ -3,6 +3,10 @@
33 "silent": true
44 },
55 "redirects": [
6+ {
7+ "source": "/getting-started/server",
8+ "destination": "/getting-started/cli"
9+ },
610 {
711 "source": "/applications",
812 "destination": "/ecosystem?type=applications"