on master help sign in
Some updates to /docs/using/: Point people to Fora in setup; update install steps for stars & galaxies; up to date source layout; change to sorting; formatting and additions
commit30f92fe05405316c0526433d66a297f7488d5e02 authorKeaton Dunsford <keaton@tlon.io> dateThu 21 Dec 2017, 18:03 (9 years ago) parent1be2287
4 files changed+278−165
docs/using/admin.md+72−45 docs/using/install.md+64−50 docs/using/layout.md+75−43 docs/using/setup.md+67−27
docs/using/admin.md+72−45
@@ -2,96 +2,123 @@
22navhome: /docs/
33navuptwo: true
44next: true
5−sort: 4
5+sort: 3
66title: Administration and operation
77---
88
99# Administration and operation
1010
11−<div class="row">
12−<div class="col-md-8">
13−
14−Your Urbit is a persistent Unix process that you mainly control from the console. For some things, a browser will also work.
15−
16−</div>
17−</div>
11+Your Urbit is a persistent Unix process that you mainly control from the
12+console. For some things, a browser will also work.
1813
1914## Shutdown
2015
21−You can turn your Urbit off with `ctrl-d` from the Talk or Dojo prompts.
16+You can turn your Urbit off with `Ctrl-d` from the Talk or Dojo prompts.
2217
2318## Restart
2419
2520To restart your Urbit simply pass the name of your pier:
2621
27− $ urbit some-planet
22+```
23+$ urbit some-planet
24+```
2825
2926or
3027
31− $ urbit comet
32−
28+```
29+$ urbit comet
30+```
3331
3432## Logging
3533
3634To log Urbit's command line output to a file, use `script`:
3735
38− $ script urbit.log urbit your-urbit
36+```
37+$ script urbit.log urbit your-urbit
38+```
3939
4040## Moving your pier
4141
42−Piers are designed to be portable, but it *must* be done while the Urbit is turned off. Urbit networking is stateful, so you can't run two copies of the same Urbit in two places.
43−
44−To move a pier, simply move the contents of the directory it lives in. To keep these files as small as possible we usually use the `--sparse` option in `tar`. With a pier `your-urbit/` something like this (from inside `urbit/`) should work:
42+Piers are designed to be portable, but it _must_ be done while the Urbit
43+is turned off. Urbit networking is stateful, so you can't run two copies
44+of the same Urbit in two places.
4545
46− tar -Scvzf your-urbit.tar.gz ./your-urbit/
46+To move a pier, simply move the contents of the directory it lives in.
47+To keep these files as small as possible we usually use the `--sparse`
48+option in `tar`. With a pier `your-urbit/` something like this (from
49+inside `urbit/`) should work:
4750
48−# Operation
51+```
52+tar -Scvzf your-urbit.tar.gz ./your-urbit/
53+```
4954
5055## Console
5156
52−Your 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.
57+Your Urbit terminal is separated into two parts: the prompt (the bottom
58+line) and the record (everything above that). The record is shared; all
59+the output from all the apps in your command set appears in it. The
60+prompt is multiplexed.
5361
54−In the CLI Urbit apps can process your input before you hit return. To see this in action try entering `)` as the first character at the Dojo prompt. Since there is no dojo command or hoon expression that starts with ')', the dojo rejects it.
62+In the CLI Urbit apps can process your input before you hit return. To
63+see this in action try entering `)` as the first character at the Dojo
64+prompt. Since there is no Dojo command or Hoon expression that starts
65+with ')', the Dojo rejects it.
5566
56−`ctrl-x` - Switches the prompt between running console apps
67+`Ctrl-x` - Switches the prompt between running console apps
5768
58−`ctrl-c` - Crash current event. Processed at the Unix layer and prints a stack trace.
69+`Ctrl-c` - Crash current event. Processed at the Unix layer and prints a stack trace.
5970
60−`ctrl-d` - From Talk or Dojo stops your Urbit process.
71+`Ctrl-d` - From Talk or Dojo stops your Urbit process.
6172
6273`↑` / `↓` - History navigation
6374
6475The following emacs-style key bindings are available:
6576
66− ctrl-a cursor to beginning of the line (Home)
67− ctrl-b cursor one character backward (left-arrow)
68− ctrl-e cursor to the end of the line (End)
69− ctrl-f cursor one character forward (right-arrow)
70− ctrl-g beep; cancel reverse-search
71− ctrl-k kill to end of line
72− ctrl-l clear the screen
73− ctrl-n next line in history (down-arrow)
74− ctrl-p previous line in history (up-arrow)
75− ctrl-r reverse-search
76− ctrl-t transpose characters
77− ctrl-u kill to beginning of line
78− ctrl-y yank from kill buffer
79−
80−Full coverage of the Urbit shell, the Dojo is covered in the [Shell walkthrough](/docs/using/shell).
77+```
78+Ctrl-a Cursor to beginning of the line (Home)
79+Ctrl-b Cursor one character backward (left-arrow)
80+Ctrl-e Cursor to the end of the line (End)
81+Ctrl-f Cursor one character forward (right-arrow)
82+Ctrl-g Beep; cancel reverse-search
83+Ctrl-k Kill to end of line
84+Ctrl-l Clear the screen
85+Ctrl-n Next line in history (down-arrow)
86+Ctrl-p Previous line in history (up-arrow)
87+Ctrl-r Reverse-search
88+Ctrl-t Transpose characters
89+Ctrl-u Kill to beginning of line
90+Ctrl-y Yank from kill buffer
91+```
92+
93+Full coverage of the Urbit shell, the Dojo is covered in the
94+[Shell walkthrough](../shell/).
8195
8296## Web
8397
84−On startup Urbit tries to bind to `localhost:8080`. If you're already running something on `8080` you'll find your Urbit on `8081`, and so on. For planets only, we also proxy web domains through Urbit's own servers. Any planet `~your-urbit` is also at
85−`your-urbit.urbit.org`.
98+On startup Urbit tries to bind to `localhost:8080`. If you're already
99+running something on `8080` you'll find your Urbit on `8081`, and so on.
100+For planets only, we also proxy web domains through Urbit's own servers.
101+Any planet `~your-urbit` is also at `your-urbit.urbit.org`.
86102
87−Your Urbit serves a simple homepage from `http://localhost:8080` or `https://your-urbit.urbit.org` that should be self-explanatory. Since our HTTPS isn't audited / battle tested we just call it "secure" HTTPS. You can find that on `8443`. Or `8444` (and so on) if you're already running something on `8443`.
103+Your Urbit serves a simple homepage from `http://localhost:8080` or
104+`https://your-urbit.urbit.org` that should be self-explanatory. Since
105+our HTTPS isn't audited / battle tested we just call it "secure" HTTPS.
106+You can find that on `8443`. Or `8444` (and so on) if you're already
107+running something on `8443`.
88108
89−A complete walkthrough of the Urbit web interface is [here](/docs/using/web).
109+A complete walkthrough of the Urbit web interface is
110+[here](../web/).
90111
91112## Continuity breaches
92113
93−While the Urbit network is in this alpha state we sometimes have to reboot the whole network. This happens either when major changes need to be shipped or we hit a bug that can't be fixed over the air.
114+While the Urbit network is in this alpha state we sometimes have to
115+reboot the whole network. This happens either when major changes need
116+to be shipped or we hit a bug that can't be fixed over the air.
94117
95−Because Urbit networking is stateful we call this a 'continuity breach'. Everything has to be restarted from scratch. Your pier will continue to function after we have breached, but it wont connect to the rest of the Urbit network.
118+Because Urbit networking is stateful we call this a _continuity breach_.
119+Everything has to be restarted from scratch. Your pier will continue to
120+function after we have breached, but it wont connect to the rest of the
121+Urbit network.
96122
97−When this happens, back up any files you'd like to save, shut down your Urbit and recreate it (as if you were starting for the first time).
123+When this happens, back up any files you'd like to save, shut down your
124+Urbit and recreate it (as if you were starting for the first time).
docs/using/install.md+64−50
@@ -8,19 +8,19 @@ title: Install
88
99# Install
1010
11−Installing Urbit is easy. It just takes a few minutes to get an
12−instance up and running on the network.
11+Installing Urbit is easy. It just takes a few minutes to get an
12+instance up and running on the network.
1313
1414Urbit is designed to run on any Unix box with an internet connection.
1515Debian (jessie), Mac OS X, FreeBSD and Fedora all work well.
1616
1717If you run into trouble installing Urbit, please let us know via
1818email, [questions@urbit.org](mailto:questions@urbit.org), or on the
19−forum: [urbit.org/fora](https://urbit.org/fora). You can also chat
19+forum: [urbit.org/fora](https://urbit.org/fora). You can also chat
2020with us at [urbit.org/stream](https://urbit.org/stream).
2121
22−> Urbit is alpha software. It’s not yet completely stable, its crypto
23−> hasn’t been audited, and there are plenty of rough edges. Urbit is
22+> Urbit is alpha software. It’s not yet completely stable, its crypto
23+> hasn’t been audited, and there are plenty of rough edges. Urbit is
2424> lots of fun to play with, but not quite ready for your important or
2525> sensitive data.
2626
@@ -28,10 +28,10 @@ with us at [urbit.org/stream](https://urbit.org/stream).
2828
2929Urbit `0.5.1` is now live! We expect there to be a delay in getting our
3030updated `urbit-0.5.1` binary packages propagated to Homebrew, APT and
31−the other various package managers. So for now, **please
32−build and install Urbit from source**. The instructions below will walk
33−you through how to do that. You'll then be free to continue the boot
34−and setup process as normal, per the rest of this Using docs section.
31+the other various package managers. So for now, **please build and
32+install Urbit from source**. The instructions below will walk you through
33+how to do that. You'll then be free to continue the boot and setup
34+process as normal, per the rest of this Using docs section.
3535
3636## Build from source
3737
@@ -39,41 +39,45 @@ and setup process as normal, per the rest of this Using docs section.
3939
4040Urbit depends on:
4141
42− C compiler (gcc or clang)
43− automake
44− autoconf
45− libtool
46− cmake
47− ragel
48− re2c
49− libcurl
50− curses
51− gmp
52− libsigsegv
53− openssl
42+```
43+C compiler (gcc or clang)
44+automake
45+autoconf
46+libtool
47+cmake
48+ragel
49+re2c
50+libcurl
51+curses
52+gmp
53+libsigsegv
54+openssl
55+```
5456
5557Which can usually be installed with the following one-liners:
5658
57− # Mac OS X [Homebrew]
58− $ brew install gmp libsigsegv openssl libtool autoconf automake cmake
59+```
60+# Mac OS X [Homebrew]
61+$ brew install gmp libsigsegv openssl libtool autoconf automake cmake
5962
60− # Mac OS X [Macports]
61− $ sudo port install gmp libsigsegv openssl autoconf automake cmake
63+# Mac OS X [Macports]
64+$ sudo port install gmp libsigsegv openssl autoconf automake cmake
6265
63− # Ubuntu or Debian
64− $ sudo apt-get install libgmp3-dev libsigsegv-dev openssl libssl-dev libncurses5-dev make exuberant-ctags automake autoconf libtool g++ ragel cmake re2c libcurl4-gnutls-dev
66+# Ubuntu or Debian
67+$ sudo apt-get install libgmp3-dev libsigsegv-dev openssl libssl-dev libncurses5-dev make exuberant-ctags automake autoconf libtool g++ ragel cmake re2c libcurl4-gnutls-dev
6568
66− # Fedora
67− $ sudo dnf install gcc gcc-c++ gmp-devel openssl-devel openssl ncurses-devel libsigsegv-devel ctags automake autoconf libtool ragel cmake re2c libcurl-devel
69+# Fedora
70+$ sudo dnf install gcc gcc-c++ gmp-devel openssl-devel openssl ncurses-devel libsigsegv-devel ctags automake autoconf libtool ragel cmake re2c libcurl-devel
6871
69− # FreeBSD
70− $ pkg install gmake gmp libsigsegv curl python automake autoconf ragel cmake re2c libtool curl
72+# FreeBSD
73+$ pkg install gmake gmp libsigsegv curl python automake autoconf ragel cmake re2c libtool curl
7174
72− # Arch
73− $ pacman -S gcc gmp libsigsegv openssl automake autoconf ragel cmake re2c libtool ncurses curl
75+# Arch
76+$ pacman -S gcc gmp libsigsegv openssl automake autoconf ragel cmake re2c libtool ncurses curl
7477
75− # AWS
76− $ sudo yum --enablerepo epel install gcc gcc-c++ gmp-devel openssl-devel ncurses-devel libsigsegv-devel ctags automake autoconf libtool cmake re2c libcurl-devel
78+# AWS
79+$ sudo yum --enablerepo epel install gcc gcc-c++ gmp-devel openssl-devel ncurses-devel libsigsegv-devel ctags automake autoconf libtool cmake re2c libcurl-devel
80+```
7781
7882### Clone and make
7983
@@ -81,9 +85,11 @@ Once your dependencies are installed the rest is easy.
8185
8286If you're cloning the `urbit/urbit` Git repository for the first time, run:
8387
84− $ git clone https://github.com/urbit/urbit
85− $ cd urbit
86− $ make # gmake on FreeBSD
88+```
89+$ git clone https://github.com/urbit/urbit
90+$ cd urbit
91+$ make # gmake on FreeBSD
92+```
8793
8894_**Updated for the `2017.12.7` continuity breach**_
8995
@@ -91,23 +97,30 @@ If you already have a clone of the `urbit/urbit` Git repository, assuming
9197your `origin` upstream is the `urbit/urbit` repository on Github, run the
9298following commands to make sure you're on the correct, clean Git branch:
9399
94− $ cd urbit
95− $ git fetch --all
96− $ git checkout master
97− $ git reset --hard origin/master
98− $ make # gmake on FreeBSD
100+```
101+$ cd urbit
102+$ git fetch --all
103+$ git checkout master
104+$ git reset --hard origin/master
105+$ make # gmake on FreeBSD
106+```
99107
100−After running `make`, your Urbit executable is in `bin/urbit`. Install it wherever you'd like.
108+After running `make`, your Urbit executable is in `bin/urbit`. Install
109+it wherever you'd like.
101110
102− # sudo install -m 0755 bin/urbit /usr/local/bin
111+```
112+$ sudo install -m 0755 bin/urbit /usr/local/bin
113+```
103114
104115Test that it works:
105116
106− $ urbit
107− simple usage:
108− urbit -c <mycomet> to create a comet (anonymous urbit)
109− urbit -w <myplanet> -t <myticket> if you have a ticket
110− urbit <myplanet or mycomet> to restart an existing urbit
117+```
118+$ urbit
119+simple usage:
120+ urbit -c <mycomet> to create a comet (anonymous urbit)
121+ urbit -w <myplanet> -t <myticket> if you have a ticket
122+ urbit <myplanet or mycomet> to restart an existing urbit
123+```
111124
112125### Boot your urbit
113126
@@ -134,3 +147,4 @@ For Amazon there’s a StackOverflow thread
134147
135148Don’t spend a lot of time tweaking these settings; the simplest
136149thing is fine.
150+
docs/using/layout.md+75−43
@@ -2,107 +2,139 @@
22navhome: /docs/
33navuptwo: true
44next: true
5−sort: 3
5+sort: 4
66title: Source layout
77---
88
9−<div class="row">
10−<div class="col-md-8">
11−
129# Arvo source
1310
14−When you boot an Urbit we transfer the current version of the Arvo operating environment to your Urbit over our network. That is, the source for the system lives on your Urbit. Here we'll take a brief tour through the structure of a base Arvo desk.
11+When you boot an Urbit we transfer the current version of the Arvo
12+operating environment to your Urbit over our network. That is, the
13+source for the system lives on your Urbit. Here we'll take a brief tour
14+through the structure of a base Arvo desk.
15+
16+Looking at the top level of
17+[the Arvo repo](http://github.com/urbit/arvo), or any Urbit desk that
18+has been mounted to Unix we see something like:
19+
20+```
21+app/
22+arvo/
23+gen/
24+lib/
25+mar/
26+ren/
27+sec/
28+sur/
29+sys/
30+web/
31+web.md
32+```
1533
16−</div>
17−</div>
34+Let's step through directory by directory.
1835
19−Looking at the top level of [the Arvo repo](http://github.com/urbit/arvo), or any Urbit desk that has been mounted to Unix we see something like:
36+## `sys/`
2037
21− app/
22− arvo/
23− gen/
24− lib/
25− mar/
26− ren/
27− sec/
28− sur/
29− web/
30− web.md
38+This is where the Arvo kernel lives. `sys/` contains:
3139
32−Let's step through directory by directory.
40+### `sys/hoon.hoon`
3341
34−## `app/`
42+Hoon is our programming langauge. Since Hoon compiles itself the
43+language is actually specified in this source file.
44+
45+### `sys/zuse.hoon`
46+
47+Zuse is the Arvo standard library.
3548
36−This is where Gall apps live. Gall apps are stateful servers, sort of like unix daemons. One familiar one is `app/talk.hoon` which is the source code for Talk the urbit messaging transport layer. And there's also `app/dojo.hoon` — that's your shell.
49+### `sys/arvo/hoon`
3750
38−## `arvo/`
51+This is the source file for the central Arvo event dispatcher.
3952
40−This is where the Arvo vanes live. Vanes are sort of like kernel modules. These are worth listing one by one:
53+### `sys/vane`
4154
42−### `arvo/ames.hoon`
55+Vanes are sort of like kernel modules. These are worth listing one by one:
56+
57+### `sys/vane/ames.hoon`
4358
4459Ames is our network protocol.
4560
46−### `arvo/behn.hoon`
61+### `sys/vane/behn.hoon`
4762
4863Behn is a simple timer.
4964
50−### `arvo/clay.hoon`
65+### `sys/vane/clay.hoon`
5166
5267Clay is our filesystem.
5368
54−### `arvo/dill.hoon`
69+### `sys/vane/dill.hoon`
5570
5671Dill is our terminal driver.
5772
58−### `arvo/eyre.hoon`
73+### `sys/vane/eyre.hoon`
5974
6075Eyre is our webserver.
6176
62−### `arvo/ford.hoon`
77+### `sys/vane/ford.hoon`
6378
6479Ford is our build system.
6580
66−### `arvo/gall.hoon`
81+### `sys/vane/gall.hoon`
6782
6883Gall is our application model.
6984
70−### `arvo/hoon.hoon`
85+### `sys/vane/jael.hoon`
86+
87+Jael is our secret vault.
7188
72−Hoon is our programming langauge. Since Hoon compiles itself the language is actually specified in this source file.
89+### `sys/vane/xmas.hoon`
7390
74−### `arvo/zuse.hoon`
91+Xmas is the new Ames, which will go live in our next big release.
7592
76−Zuse is the Hoon library.
93+That's it. That's the whole system.
7794
78−That's it. That's the whole system.
95+## `app/`
96+
97+This is where Gall apps live. Gall apps are stateful servers, sort of
98+like unix daemons. One familiar one is `app/hall.hoon` which is the
99+source code for Hall, the Urbit messaging transport layer. And there's
100+also `app/dojo.hoon` — that's your shell.
79101
80102## `gen/`
81103
82−`gen/` holds generators. Generators are short Dojo scripts.
104+`gen/` holds generators. Generators are short Dojo scripts.
83105
84106## `lib/`
85107
86−`lib/` holds shared libraries for programs. `lib/sole` is a good example — that's the console library that's shared by both Dojo in the command line, and the Dojo web client.
108+`lib/` holds shared libraries for programs. `lib/sole` is a good
109+example — that's the console library that's shared by both Dojo in the
110+command line, and the Dojo web client.
87111
88112## `mar/`
89113
90−This is where marks live. Marks are data type definitions used by Ford. A mark is like a mime-type, but specified in executable code.
114+This is where marks live. Marks are data type definitions used by Ford.
115+A mark is like a mime-type, but specified in executable code.
91116
92117## `ren/`
93118
94−These are web renderers. A renderer handles web requests of a particular type.
119+These are web renderers. A renderer handles web requests of a particular
120+type.
95121
96−Default web requests in urbit are handled as a `.urb`, which is caught by the `urb.hoon` renderer. This wraps the request in our default `css` and `js` and adds some routing magic for certain paths.
122+Default web requests in urbit are handled as a `.urb`, which is caught
123+by the `urb.hoon` renderer. This wraps the request in our default `CSS`
124+and `JS` and adds some routing magic for certain paths.
97125
98126## `sur/`
99127
100−`sur/` contains shared data structures. Files in `sur` are like header files in C.
128+`sur/` contains shared data structures. Files in `sur` are like header
129+files in C.
101130
102131## `web/`
103132
104−There are the files publicly accessible to the web, as made possible by Eyre.
133+There are the files publicly accessible to the web, as made possible by
134+Eyre.
105135
106136## `web.md`
107137
108−This is the homepage for your urbit. You'll see it at `http://localhost:8080/` or `http://fintud-macrep.urbit.org/`.
138+This is the homepage for your urbit. You'll see it at
139+`http://localhost:8080/` or `https://your-urbit.urbit.org/`.
140+
docs/using/setup.md+67−27
@@ -10,39 +10,49 @@ title: Setup
1010
1111On disk your urbit is an append-only log and a checkpoint. Or, in
1212simpler terms, a directory where we keep your urbit’s state. We call
13−this a ‘pier’.
13+this a _pier_.
1414
1515## Initialize
1616
1717To create an urbit, we need an identity. This identity is both a network
1818address and a memorable name.
1919
20−You are probably creating one of two kinds of urbit: a 32-bit "planet"
21−or a 128-bit "comet." For a quick terminology guide and high-level
22−refresher, refer to this [handy reference sheet](/docs/about/glossary).
20+You are probably creating one of two kinds of urbit: a 32-bit _planet_
21+or a 128-bit _comet_. For a quick terminology guide and high-level
22+refresher, refer to this [handy reference sheet](../../about/glossary/).
2323
2424If you have an Urbit invitation, you'll have a planet like
2525`~fintud-macrep` and `~fortyv-tombyt-tabsen-sonres`. To create your
2626pier:
2727
28− $ urbit -w fintud-macrep -t fortyv-tombyt-tabsen-sonres
28+```
29+$ urbit -w fintud-macrep -t fortyv-tombyt-tabsen-sonres
30+```
2931
3032This will create a directory `fintud-macrep/` and begin building your
3133urbit. This may take a few minutes.
3234
33−If you do not have a ticket, you can still make a 'comet', a wild urbit
35+> If you are booting a star, the process is the same as above, with your
36+> respective star name and ticket.
37+>
38+> If you are booting a galaxy, see
39+> [this Fora post](https://urbit.org/fora/posts/~2016.8.17..21.04.11..1450~/).
40+
41+If you do not have a ticket, you can still make a _comet_, a wild urbit
3442drifting through cyberspace. Pick your own directory name, it doesn't
3543matter:
3644
37− $ urbit -c mycomet
45+```
46+$ urbit -c mycomet
47+```
3848
3949This will create the directory `mycomet/` and generate a 128-bit
4050identity for your urbit.
4151
4252## Orientation
4353
44−When your urbit is finished booting you should see a `dojo>` prompt.
45−Welcome!
54+After about five to ten minutes, when your urbit is finished booting,
55+you should see a `dojo>` prompt. Welcome!
4656
4757By default your urbit is quite bare-bones. Let's stroll through what's
4858already running:
@@ -52,50 +62,79 @@ already running:
5262The command prompt in front of you is a simple shell and Hoon REPL.
5363Let's make sure it works:
5464
55− ~your-urbit:dojo> (add 2 2)
65+```
66+~your-urbit:dojo> (add 2 2)
67+```
5668
5769Should produce:
5870
59− > (add 2 2)
60− 4
71+```
72+> (add 2 2)
73+4
74+```
6175
6276Good.
6377
78+
6479### Messaging — Talk
6580
6681Use `ctrl-x` to change your prompt. Let's join the main Urbit chat
6782channel, `/urbit-meta`:
6883
69− ~your-urbit:talk[] ;join ~samzod/urbit-meta
84+```
85+~your-urbit:talk[] ;join ~samzod/urbit-meta
86+```
7087
7188Talk is stateful, so your urbit will download a backlog.
72−`/urbit-meta` is the place to ask questions, get help and talk about
73−anything Urbit-related.
89+`/urbit-meta` is the place to ask questions, get help, talk about
90+anything Urbit-related, and meet everyone on here.
91+
92+### Discussion — Fora
93+
94+Fora is the place for long-form Urbit discussion. It's hosted on an
95+Urbit and served over HTTP via Eyre, Urbit's web server.
96+
97+Head on over to:
98+
99+ https://urbit.org/~~/fora
100+
101+The `/~~/` in the URL will redirect you to a login page, which will
102+provide you steps to run the `+code` generator (shell script) in your
103+Dojo to get your password. Copy and paste that into your password box
104+input and hit Enter. After loading, you'll find yourself redirected to
105+the Fora home page, authenticated, where you can post and comment under
106+the name of your ship.
74107
75108### Web — Tree
76109
77−Urbit is also accessible through the web. Try opening:
110+Your Urbit is also accessible through its own web interface. Try
111+opening:
78112
79− http://localhost:8080/
113+ http://localhost:8080/~~/
80114
81−in your favorite browser. You'll be prompted to use `+code` in your Dojo
82−to retrive your password and log in. This page was generated by Tree,
83−the basic Urbit web interface. You can also access your urbit through
84−`http://your-urbit.urbit.org`. Note that this latter approach is slower
85−for the time being because we proxy over the Urbit network, Ames, but a
86−better, faster solution for this is in the works.
115+in your favorite browser. Like on `urbit.org`, you'll be prompted to use
116+`+code` in your Dojo to retrive your password and log in. This page was
117+generated by Tree, the basic Urbit web interface. You can also access
118+your urbit through `https://your-urbit.urbit.org/~~/`. Note that this
119+latter approach is slower for the time being because we proxy over the
120+Urbit network, Ames, but a better, faster solution for this is in the
121+works.
87122
88123### Filesystem — Clay
89124
90125Clay, the Urbit filesystem, isn't mounted to Unix by default. Switch
91126to the Dojo prompt and run:
92127
93− ~your-urbit:dojo> |mount %
128+```
129+~your-urbit:dojo> |mount %
130+```
94131
95132This should produce:
96133
97− > |mount %
98− >=
134+```
135+> |mount %
136+>=
137+```
99138
100139which indicates the command was processed.
101140
@@ -105,6 +144,7 @@ folder. Changes to these files are automatically synced into your urbit.
105144## Learn more
106145
107146If you're eager to get started programming you're ready to head over to
108−<a href="../../hoon/demo">the Hoon demo</a>.
147+[the Hoon section](../../hoon/mission/).
109148
110149To learn more about using the system, let's keep going:
150+