7b7e9e3104
Four changes: - implement +validate-u to allow %u requests over the network - make +validate-x use our local marks to make %x requests generally work over the network - in +start-request, if a foreign ship is making a request that we shouldn't send over the network, ignore it. This closes a DOS vector. - in +duce, if we're about to make a request to a foreign ship which they won't be able to answer, crash the event. Combined, these fix many of the common cases of weirdness around foreign clay requests. Notably absent is a fix for reading `%a` across the network, which I still maintain should happen against the foreign hoon/zuse. fixes #4834 see also #4307 |
||
|---|---|---|
| .. | ||
| app | ||
| gen | ||
| lib | ||
| mar | ||
| sur | ||
| sys | ||
| ted | ||
| tests | ||
| .gitattributes | ||
| .ignore | ||
| LICENSE.txt | ||
| README.md | ||
| TESTING.udon | ||
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 %/tests in dojo. To run only the tests in /tests/some/path, use -test %/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: @joemfb (~master-morzod)/sys/vane/ames: @belisarius222 (~rovnys-ricfer) & @philipcmonk (~wicdev-wisryt)/sys/vane/behn: @belisarius222 (~rovnys-ricfer)/sys/vane/clay: @philipcmonk (~wicdev-wisryt) & @belisarius222 (~rovnys-ricfer)/sys/vane/dill: @fang- (~palfun-foslup)/sys/vane/eyre: @fang- (~palfun-foslup)/sys/vane/gall: @philipcmonk (~wicdev-wisryt)/sys/vane/jael: @fang- (~palfun-foslup) & @philipcmonk (~wicdev-wisryt)/app/acme: @joemfb (~master-morzod)/app/dns: @joemfb (~master-morzod)/app/aqua: @philipcmonk (~wicdev-wisryt)/app/hood: @belisarius222 (~rovnys-ricfer)/lib/hood/drum: @fang- (~palfun-foslup)/lib/hood/kiln: @philipcmonk (~wicdev-wisryt)
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:
- joining the urbit-dev mailing list.
- applying to Hoon School, a course we run to teach the Hoon programming language and Urbit application development.