51686d8 · urbit.org · git.iko.soy

concepts/azimuth/blockchain.udon+2−2

compare with master

unifiedsplit

@@ -45,5 +45,5 @@ computation Landscape the latter is not. We need a computational blockchain to

45enforce the specific rules of the Urbit identity registry.

46

47For more background on the decision to use the Ethereum blockchain, check out

48−[these](https://urbit.org/posts/essays/urbit-and-the-blockchain/)

48+[these](urbit.org/posts/essays/urbit-and-the-blockchain)

49−[two](https://urbit.org/posts/essays/bootstrapping-urbit-from-ethereum/) posts.

49+[two](urbit.org/posts/essays/bootstrapping-urbit-from-ethereum/) posts.

concepts/contributing.udon+1−1

@@ -15,7 +15,7 @@ If you're interested in contributing, but don't know where to start, feel free t

15

16Our official guide to contributing can be found [here](https://github.com/urbit/urbit/blob/master/CONTRIBUTING.md), which is most useful for large and low-level changes.

17

18−Before contributing code, you should familiarize yourself with the [Hoon style guide](/docs/learn/arvo/style). For a good example of preferred Hoon coding style, see [ford.hoon](https://github.com/urbit/arvo/blob/master/sys/vane/ford.hoon).

18+Before contributing code, you should familiarize yourself with the [Hoon style guide](/docs/learn/hoon/style). For a good example of preferred Hoon coding style, see [ford.hoon](https://github.com/urbit/arvo/blob/master/sys/vane/ford.hoon).

19

20## Community Guidelines

21

concepts/technical-overview.udon+1−1

@@ -114,7 +114,7 @@ about 3000 lines of Hoon.

114### Nock

115

116Nock is a low-level [homoiconic](https://en.wikipedia.org/wiki/Homoiconicity)

117−combinator language. It's so simple that its [specification](../../nock/definition)

117+combinator language. It's so simple that its [specification](/docs/learn/nock/definition)

118fits on a t-shirt. In some ways Nock resembles a nano-Lisp but its ambitions

119are more narrow. Most Lisps are one-layer: a practical language is to be

120created by extending a theoretically simple interpreter. The abstraction is

using/admin.udon+3−8

@@ -117,17 +117,14 @@ On startup Urbit tries to bind to `localhost:8080`. If you're already

117running something on `8080` -- such as another urbit -- you'll find the urbit

118that you just started on `8081`, and so on. For planets only, we also proxy web

119domains through Urbit's own servers. Any planet `~your-urbit` is also at

120−`your-urbit.urbit.org`.

120+`your-urbit.arvo.network`.

121

122Your urbit serves a simple homepage from `http://localhost:8080` or

123−`https://your-urbit.urbit.org` that should be self-explanatory. Since

123+`https://your-urbit.arvo.network` that should be self-explanatory. Since

124our HTTPS isn't audited / battle tested, we just call it "secure" HTTPS.

125You can find that on `8443`. Or `8444` (and so on) if you're already

126running something on `8443`.

127

128−A complete walkthrough of the Urbit web interface is

129−[here](../web/).

130−

131## Moons

128## Moons

132

129

133Urbit namespace is distributed by having parent nodes sign the keys for child

130Urbit namespace is distributed by having parent nodes sign the keys for child

@@ -173,9 +170,7 @@ moon: ~faswep-navred-sampel-palnet

173`<keyfile>` will be at `path/to/sampel-palnet/.urb/put/moon.key`

170`<keyfile>` will be at `path/to/sampel-palnet/.urb/put/moon.key`

174and does not need editing to be used with the `-k` option.

171and does not need editing to be used with the `-k` option.

175

172

176−You can use the resulting output in the same installation flow from

177−[install](../install) and [setup](../setup), following the same scheme as

178−for booting a planet. That scheme is:

173+The scheme for booting is:

179

174

180```

175```

181$ urbit -w <moonname> -G <key> -c <piername>

176$ urbit -w <moonname> -G <key> -c <piername>

using/generators.udon+1−1

@@ -29,7 +29,7 @@ a

29

30This generator takes one argument of any noun and produces it without any

31changes. If we put this into a file named `echo.hoon` in the `/gen` directory,

32−we can run it from the [Dojo](/docs/learn/arvo/arvo-internals/shell):

32+we can run it from the [Dojo](../shell):

33

34```

35> +echo 42

using/layout.udon+4−4

@@ -47,7 +47,7 @@ This is where the Arvo kernel lives. `sys/` contains:

47

48##### `sys/hoon.hoon`

49

50−[Hoon](/docs/learn/arvo/hoon) is our programming language. Since Hoon

50+[Hoon](/docs/learn/hoon) is our programming language. Since Hoon

51compiles itself, the language is actually specified in this source file.

52

53##### `sys/zuse.hoon`

@@ -104,9 +104,9 @@ That's it. That's the whole system.

104

105## app/

106

107−This is where [Gall](../gall) apps live. Gall apps are stateful

107+This is where [Gall](/docs/learn/arvo/gall) apps live. Gall apps are stateful

108servers, sort of like unix daemons. One familiar one is `app/hall.hoon` which is

109−the source code for [Hall](../hall), the Urbit messaging transport

109+the source code for [Hall](/docs/learn/arvo/hall), the Urbit messaging transport

110layer. And there's also `app/dojo.hoon` — that's your shell.

111

112---

@@ -167,7 +167,7 @@ lib/test/*

167## web/

168

169Here are files publicly accessible to the web, as made possible by

170−[Eyre](../eyre).

170+[Eyre](/docs/learn/arvo/eyre).

171

172---

173

using/messaging.udon+1−1

@@ -27,7 +27,7 @@ be used for that we haven't even thought of.

27

28Here we'll be discussing how to operate the default CLI frontend, Talk,

29to send and receive messages. For a more in-depth look at Hall's internals,

30−take a look at its [documentation](../hall).

30+take a look at its [documentation](/docs/learn/arvo/hall).

31

32## Quickstart

33

using/sail.udon+4−4

@@ -15,10 +15,10 @@ be dealing with Sail as it renders to HTML, a subset of XML.

15### Getting Started

16

17Before starting, make sure that your urbit is

18−[mounted to Unix](https://urbit.org/docs/using/setup/)

18+[mounted to Unix](/docs/getting-started/creating-a-development-ship/)

19

20To host that output, your ship also has a web-server, called

21−[Eyre](https://urbit.org/docs/using/web/), that can be found at

21+Eyre, that can be found at

22`http://localhost:8080/` if it’s your first ship that’s running on the a

23machine, `http://localhost:8081/` if it’s the second ship on that same machine,

24and so on. In the startup messages, a ship will tell you which HTTP port it's

@@ -456,7 +456,7 @@ Hoon. They are part of Ford, our build system.

456

457`/$` is used to get data from the environment, and `/=` adds that data to

458subject in the face `gas`. The

459−[Ford user manual](https://urbit.org/docs/arvo/internals/ford/runes/) has

459+[Ford user manual](/docs/learn/arvo/ford/) has

460details on these and other Ford runes, but understanding these runes isn’t

461necessary for the purposes of this tutorial.

462

@@ -680,7 +680,7 @@ valid lists for the `;* ?: show-list` expression to resolve.

680You should now have foundational knowledge for making web pages with Sail. There

681is, of course, more to learn. If you’re curious, there’s more advanced

682resources out there.

683−The [Ford manual](https://urbit.org/docs/arvo/internals/ford/runes/)

683+The [Ford manual](/docs/learn/arvo/ford/)

684can show you how to access various ship resources for user in your pages. To

685learn more about how the renderer works, take a look at the

686`/home/ren/urb.hoon` file inside your urbit.

using/shell.udon+1−1

@@ -36,7 +36,7 @@ Tall-form Hoon may require multiple lines:

36~your-urbit:dojo< 2

37```

38

39−Hoon uses something called [the subject](/docs/learn/arvo/hoon/the-subject-and-its-legs).

39+Hoon uses something called [the subject](/docs/learn/hoon/hoon-tutorial/the-subject-and-its-legs).

40The Dojo has its own subject, and that's where Hoon's equivalent of variables,

41called faces, are stored.

42

using/udon.udon+6−6

@@ -45,10 +45,10 @@ Udon files using our web interface.

45### Getting Started

46

47Before starting, make sure that your urbit is

48−[mounted to Unix](https://urbit.org/docs/using/setup/)

48+[mounted to Unix](/docs/getting-started/creating-a-development-ship/)

49

50To host Udon and other kinds of files, your ship also has a

51−web-server, called [Eyre](https://urbit.org/docs/using/web/), that can be found

51+web-server, called Eyre, that can be found

52at `http://localhost:8080/` if it’s your first ship that’s running on the

53machine, `http://localhost:8081/` if it’s the second ship on that same machine,

54and so on. If you can't find your ship on one of these for some reason, try the

@@ -323,12 +323,12 @@ destination.

323*Example:*

324

325```

326−[I'm an inline-style link](https://www.urbit.org/docs/reference/shell)

326+[I'm an inline-style link](https://www.urbit.org/docs/using/shell)

327```

328

329###### Produces:

330

331−[I'm an inline-style link](https://www.urbit.org/docs/reference/shell)

331+[I'm an inline-style link](https://www.urbit.org/docs/using/shell)

332

333The second type is a reference-style link, which uses a relative path, based on

334the current page's location. Instead of the full url, we use `..` to fill in

@@ -344,7 +344,7 @@ the all of the URL that the destination has in common with the origin page.

344

345[I'm a reference-style link](../shell)

346

347−If this page is located at `https://www.urbit.org/docs/reference/`, then these two

347+If this page is located at `https://www.urbit.org/docs/using/`, then these two

348examples should have the same destination.

349

350#### Anchor Link

@@ -791,7 +791,7 @@ Note: below we use Urbit's implementation of Markdown, [Udon](#udon).

791This markup language allows you to use snippets of Hoon code but not HTML.

792In particular, we use Sail, a subset of Hoon. This Sail is rendered as HTML

793when the file is served to a client. To learn about Sail, head over to

794−the [Sail](/docs/learn/arvo/arvo-internals/sail) section of the docs.

794+the [Sail](/docs/using/sail) section of the docs.

795

796In `site/web/meet.udon` put:

797