78dadf7 · urbit.org · git.iko.soy

getting-started/booting-a-ship.md+1−1

compare with master

unifiedsplit

@@ -84,7 +84,7 @@ This should produce:

84

85which indicates that the command was processed.

86

87−`|mount %` will cause a `home/` directory to appear inside your _pier_ folder in Unix (the "pier" is our shorthand for the directory whose name corresponds to your Azimuth point). Changes to these files are automatically synced into your ship.

87+`|mount %` will cause a `home/` directory to appear inside your _pier_ folder in Unix (the "pier" is our shorthand for the directory whose name corresponds to your Azimuth point). Once you've changed a file, `|commit %home` to synchronize changes to your pier.

88

89**Note: Do not, under any circumstances, delete your pier. If your pier is deleted, your ship cannot be recovered until the Arvo network is reset ("breached") -- a rare occasion.**

90

learn/arvo/clay.md+1−1

@@ -325,7 +325,7 @@ and this will mount the given clay directory to the mount-point

325directory in Unix. Every file is converted to `%mime` before it's

326written to Unix, and converted back when read from Unix. The

327entire directory is watched (a la Dropbox), and every change is

328−auto-committed to clay.

328+committed once you run `|commit %mount-point`.

329

330### Merging

331

reference/glossary.md+1−2

@@ -94,8 +94,7 @@ Below are Arvo modules, which are called "vanes".

94 to Unix and vice versa.

95

96 A common way to use it is to create a pier, a directory that exists in and is

97− visible in Unix. Changes are automatically recorded from Urbit to the Unix

97+ visible in Unix.

98− directory, and vice versa. Just set it and forget it!

99

98

100 Clay is located at `/home/sys/vane/clay.hoon` within your urbit.

99 Clay is located at `/home/sys/vane/clay.hoon` within your urbit.

101

100

using/creating-a-development-ship.md+1−1

@@ -56,7 +56,7 @@ This should produce:

56

57which indicates that the command was processed.

58

59−`|mount %` will cause a `home/` directory to appear inside your _pier_ folder in Unix (the "pier" is our shorthand for the directory whose name corresponds to your Azimuth point). Changes to these files are automatically synced into your ship.

59+`|mount %` will cause a `home/` directory to appear inside your _pier_ folder in Unix (the "pier" is our shorthand for the directory whose name corresponds to your Azimuth point). Changes to these files can be committed to your pier by running `|commit %home` once you're done.

60

61### Shutting Down and Restarting

62

using/filesystem.md+2−4

@@ -5,11 +5,9 @@ template = "doc.html"

5+++

6Urbit has its own revision-controlled filesystem, Clay. Clay is a typed, global,

7referentially transparent namespace. An easy way to think about it is like typed

8−`git` with continuous sync.

8+`git`.

9

10−The most common way to use Clay is to mount a Clay node in a Unix directory. The

10+The most common way to use Clay is to mount a Clay node in a Unix directory. The mounted directory is always at the root of your

11−Urbit process will watch this directory and automatically record edits as

12−changes, Dropbox style. The mounted directory is always at the root of your

13pier directory.

11pier directory.

14

12

15## Quickstart

13## Quickstart