git.iko.soy/urbit.org
on 430c6c4 help sign in
urbit.org/docs/using/admin.md
106 lines 4.7 kB history raw
1---
2navhome: /docs/
3next: true
4sort: 3
5title: Basic operation
6---
8# Basic operation
10<div class="row">
11<div class="col-md-8">
13Your Urbit is a persistent Unix process that you mainly control from the console. For some things, a browser will also work.
15</div>
16</div>
18## Shutdown
20You can turn your Urbit off with `ctrl-d` from the `:talk` or `:dojo` prompts.
22## Restart
24To restart your Urbit simply pass the name of your pier:
26 $ urbit some-planet
28or
30 $ urbit comet
33## Logging
35To log Urbit's command line output to a file, use `script`:
37 $ script urbit.log urbit your-urbit
39## Console
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.
43In 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.
45`ctrl-x` - Switches the prompt between running console apps
47`ctrl-c` - Crash current event. Processed at the Unix layer and prints a stack trace.
49`ctrl-d` - From `:talk` or `:dojo` stops your Urbit process.
51`↑` / `↓` - History navigation
53The following emacs-style key bindings are available:
55 ctrl-a cursor to beginning of the line (Home)
56 ctrl-b cursor one character backward (left-arrow)
57 ctrl-e cursor to the end of the line (End)
58 ctrl-f cursor one character forward (right-arrow)
59 ctrl-g beep; cancel reverse-search
60 ctrl-k kill to end of line
61 ctrl-l clear the screen
62 ctrl-n next line in history (down-arrow)
63 ctrl-p previous line in history (up-arrow)
64 ctrl-r reverse-search
65 ctrl-t transpose characters
66 ctrl-u kill to beginning of line
67 ctrl-y yank from kill buffer
69Full coverage of the Urbit shell, the `:dojo` is covered in the [Shell walkthrough](/docs/using/shell).
71## Web
73On 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
74`your-urbit.urbit.org`.
76Your 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`.
78A complete walkthrough of the Urbit web interface is [here](/docs/using/web).
80## Moons
82Urbit namespace is distributed by having parent nodes sign the keys for child nodes. If you have a planet, your parent star issued your ticket. As a planet you, in turn, can sign the keys for moons. The basic idea is: your planet runs permanently in a data center somewhere and moons run on all your devices. Each planet can issue ~4 billion (`2^32`) moons.
84To generate a random moon from your planet run:
86 ~your-urbit:dojo> +moon
88You can use the resulting output in the same installation flow from [install](/docs/using/install).
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.
92## Moving your pier
94Piers 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.
96To 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:
98 tar -Scvzf your-urbit.tar.gz ./your-urbit/
100## Continuity breaches
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.
104Because 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.
106When 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).