on master help sign in
Merge pull request #116 from heow/master
e8a910bGalen Wolfe-Pauly
docs/using/admin.md+12−10
@@ -2,10 +2,10 @@
2navhome: /docs/
2navhome: /docs/
3next: true
3next: true
4sort: 3
4sort: 3
5−title: Basic operation
5+title: Administration and Operation
6---
6---
7
7
8−# Basic operation
8+# Administration
9
9
10<div class="row">
10<div class="row">
11<div class="col-md-8">
11<div class="col-md-8">
@@ -36,6 +36,16 @@ To log Urbit's command line output to a file, use `script`:
36
36
37 $ script urbit.log urbit your-urbit
37 $ script urbit.log urbit your-urbit
38
38
39+## Moving your pier
40+
41+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.
42+
43+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:
44+
45+ tar -Scvzf your-urbit.tar.gz ./your-urbit/
46+
47+# Operation
48+
39## Console
49## Console
40
50
41Your 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.
51Your 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.
@@ -89,14 +99,6 @@ You can use the resulting output in the same installation flow from [install](/d
89
99
90Moons are automatically synced to their parent `%kids` desk, and can control applications on their parent planet using `|link`. You can read more about those things in the [filesystem](/docs/using/filesystem) and [console](/docs/using/shell) walkthroughs.
100Moons are automatically synced to their parent `%kids` desk, and can control applications on their parent planet using `|link`. You can read more about those things in the [filesystem](/docs/using/filesystem) and [console](/docs/using/shell) walkthroughs.
91
101
92−## Moving your pier
93−
94−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.
95−
96−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:
97−
98− tar -Scvzf your-urbit.tar.gz ./your-urbit/
99−
100## Continuity breaches
102## Continuity breaches
101
103
102While 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.
104While 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.