on master help sign in
Clay sync changes
commite457dc4ed057fc796b405460a1c761e1bd7d765b authorMatilde Park <matilde@tlon.io> dateWed 31 Jul 2019, 10:01 (7 years ago) parent21c76eb
5 files changed+6−9
getting-started/booting-a-ship.md+1−1 learn/arvo/clay.md+1−1 reference/glossary.md+1−2 using/creating-a-development-ship.md+1−1 using/filesystem.md+2−4
getting-started/booting-a-ship.md+1−1
@@ -84,7 +84,7 @@ This should produce:
8484
8585which indicates that the command was processed.
8686
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.
8888
8989**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.**
9090
learn/arvo/clay.md+1−1
@@ -325,7 +325,7 @@ and this will mount the given clay directory to the mount-point
325325directory in Unix. Every file is converted to `%mime` before it's
326326written to Unix, and converted back when read from Unix. The
327327entire directory is watched (a la Dropbox), and every change is
328−auto-committed to clay.
328+committed once you run `|commit %mount-point`.
329329
330330### Merging
331331
reference/glossary.md+1−2
@@ -94,8 +94,7 @@ Below are Arvo modules, which are called "vanes".
9494 to Unix and vice versa.
9595
9696 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
98− directory, and vice versa. Just set it and forget it!
97+ visible in Unix.
9998
10099 Clay is located at `/home/sys/vane/clay.hoon` within your urbit.
101100
using/creating-a-development-ship.md+1−1
@@ -56,7 +56,7 @@ This should produce:
5656
5757which indicates that the command was processed.
5858
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.
6060
6161### Shutting Down and Restarting
6262
using/filesystem.md+2−4
@@ -5,11 +5,9 @@ template = "doc.html"
55+++
66Urbit has its own revision-controlled filesystem, Clay. Clay is a typed, global,
77referentially transparent namespace. An easy way to think about it is like typed
8−`git` with continuous sync.
8+`git`.
99
10−The most common way to use Clay is to mount a Clay node in a Unix directory. The
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
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
1311pier directory.
1412
1513## Quickstart