bf64e94ca3
For the server case, we add tests for http-first finalization, incorrect eauth tokens, attempt expiration, client abort signalling, and client deletion requests. For the client case, we add a test for approving eauth attempts without being locally authenticated. To this end, we refactor the layout of the eauth tests. The +eauth core now contains the tasks/gifts to be handled by the client/server, but no longer does move checking. This happens within the test arms only. This way, we may trivially re-run parts of the eauth flow under different conditions. |
||
---|---|---|
.github | ||
bin | ||
doc/spec | ||
extras | ||
nix | ||
pkg | ||
sh | ||
tests | ||
.gitattributes | ||
.gitignore | ||
.ignore | ||
.mailmap | ||
.stylish-haskell.yaml | ||
CONTRIBUTING.md | ||
default.nix | ||
LICENSE.txt | ||
MAINTAINERS.md | ||
Makefile | ||
README.md | ||
shell.nix | ||
vere-version |
Urbit
Urbit is a personal server stack built from scratch. It has an identity layer (Azimuth), virtual machine (Vere), and operating system (Arvo).
A running Urbit "ship" is designed to operate with other ships peer-to-peer. Urbit is a general-purpose, peer-to-peer computer and network.
This repository contains the Arvo Kernel
For the Runtime, see Vere. For more on the identity layer, see Azimuth. To manage your Urbit identity, use Bridge.
Install
To install and run Urbit, please follow the instructions at urbit.org/getting-started. You'll be on the live network in a few minutes.
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, and how we manage issues.
You might also be interested in joining the urbit-dev mailing list.
Release
For details about our release process, see the maintainers guidelines