shrub/pkg/arvo
Jared Tobin 6ccc843165
Merge branch 'arvo-errors' (#2366)
* origin/arvo-errors: (35 commits)
  pill: all
  vane: jet-hints all vanes for profiling
  arvo: refines crash printfs
  arvo: fix wire (and adapt old) for %vega reset notification
  arvo: removes all vase literals from |va
  arvo: removes all traces of meta-meta card reduction
  arvo: cleanup per review
  arvo: removes vestigial |is core
  arvo: remove refactoring comments
  arvo: replace $milt with $meta
  arvo: replace $mill with $maze
  worker: sends new error-notification events
  arvo: removes %gave, generalizes %hurl
  vane: prints error notifications where not handled
  behn: forward %drip error notifications, refactor %crud handling
  ames: downcast %hear error notification to %hole
  vane: downcast all error notifications to %crud
  arvo: removes (commented out) legacy event routing
  test: updates vane calling convention
  dill: "downcast" +call error notification to %crud
  ...

Signed-off-by: Jared Tobin <jared@tlon.io>
2020-03-06 13:45:33 +04:00
..
app Merge pull request #2403 from urbit/publish-meta-ota 2020-03-05 20:35:27 -08:00
gen Merge branch 'master' into os1-rc 2020-02-26 19:18:17 -08:00
lib Merge branch 'arvo-errors' (#2366) 2020-03-06 13:45:33 +04:00
mar link-view: support %delete and %invite actions 2020-03-04 22:11:54 +01:00
ren various: remove trailing whitespace 2020-01-03 22:06:42 +01:00
sur link-view: support %delete and %invite actions 2020-03-04 22:11:54 +01:00
sys Merge branch 'master' into arvo-errors 2020-03-05 11:56:49 -08:00
ted gall: (list path) in %fact and %kick 2019-12-23 13:37:32 +01:00
tests Merge branch 'master' into arvo-errors 2020-03-05 11:56:49 -08:00
.gitattributes gitattributes: export-ignore additions [ci skip] 2020-02-01 17:40:27 +04:00
.ignore Write top-level pier code; hook up Ames and Behn. 2019-07-31 19:34:14 -07:00
LICENSE.txt Pull in latest v0.8.0.rc changes 2019-07-16 15:59:39 -07:00
README.md master without pills, hopefully 2019-10-14 16:02:27 -04:00
TESTING.udon Pull in latest v0.8.0.rc changes 2019-07-16 15:59:39 -07:00

Arvo

A clean-slate operating system.

Usage

To run Arvo, you'll need Urbit. To install Urbit and run Arvo please follow the instructions in the getting started docs. You'll be on the live network in a few minutes.

If you're doing development on Arvo, keep reading.

Documentation

Find Arvo's documentation on urbit.org.

Development

To boot a fake ship from your development files, run urbit with the following arguments:

urbit -F zod -A /path/to/arvo -c fakezod

Mount Arvo's filesystem allows you to update its contents through Unix. To do so, run |mount in dojo. It is most common to |mount /=home=.

To create a custom pill (bootstrapping object) from the files loaded into the home desk, run .my/pill +solid. Your pill will appear in /path/to/fakezod/.urb/put/my.pill.

To boot a fake ship with a custom pill, use the -B flag:

urbit -F zod -A /path/to/arvo -B /path/to.pill -c fakezod

To run all tests in /tests, run +test in dojo. +test /some/path would only run all tests in /tests/some/path.

Maintainers

Most parts of Arvo have dedicated maintainers.

  • /sys/hoon: @pilfer-pandex (~pilfer-pandex)
  • /sys/zuse: @pilfer-pandex (~pilfer-pandex)
  • /sys/arvo: @jtobin (~nidsut-tomdun)
  • /sys/vane/ames: @belisarius222 (~rovnys-ricfer) & @joemfb (~master-morzod)
  • /sys/vane/behn: @belisarius222 (~rovnys-ricfer)
  • /sys/vane/clay: @philipcmonk (~wicdev-wisryt)
  • /sys/vane/dill: @bernardodelaplaz (~rigdyn-sondur)
  • /sys/vane/eyre: @eglaysher (~littel-ponnys)
  • /sys/vane/ford: @belisarius222 (~rovnys-ricfer) & @eglaysher (~littel-ponnys)
  • /sys/vane/gall: @jtobin (~nidsut-tomdun)
  • /sys/vane/jael: @fang- (~palfun-foslup) & @joemfb (~master-morzod)
  • /app/acme: @joemfb (~master-morzod)
  • /app/dns: @joemfb (~master-morzod)
  • /app/hall: @fang- (~palfun-foslup)
  • /app/talk: @fang- (~palfun-foslup)
  • /app/aqua: @philipcmonk (~wicdev-wisryt)
  • /lib/test: @eglaysher (~littel-ponnys)

Contributing

Contributions of any form are more than welcome! Please take a look at our contributing guidelines for details on our git practices, coding styles, how we manage issues, and so on.

You might also be interested in: