d52b051196
In Publish, users could get in a bad state if they made a post with valid udon, and subsequently edited to contain invalid udon. Furthermore, users subscribed to them would get in the same bad state. This fixes the original bug, and users who are already in the broken state will be able to run a recovery command: :publish %state-surgery which will also fix the downstream broken state of their subscribers. |
||
|---|---|---|
| .. | ||
| .travis | ||
| app | ||
| gen | ||
| lib | ||
| mar | ||
| ren | ||
| sur | ||
| sys | ||
| tests | ||
| .gitignore | ||
| .travis.yml | ||
| 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 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! If something doesn't seem right, and there is no issue about it yet, feel free to open one.
If you're looking to make code contributions, there are a few things you can do:
- Join the urbit-dev mailing list.
- Ask us about Hoon School, a course we run to teach the Hoon programming language and Urbit application development.
- Check out good contributor issues.
- Reach out to support@urbit.org to say hi and ask any questions you might have.