00f7407a5e
unix cannot represent the file with empty name, and it has special mappings for '.' and '..'. as these three are all valid arvo `+knot`s, we need to escape them if we come across them. the method we use to escape is: if we encounter any of those three `+knot`s, or any `+knot` starting with '~', we prepend its filename with a '~'. and when going from filename to `+knot`, we do the reverse; i.e. we ignore a '~' if it is the first character of a filename. the current implementation just crashes if it encounters a `+knot` containing '/' or '\\', neither of which are valid under the current implementation of `@ta` (which only accepts numbers, lowercase, '-', '~', '.', and '_'.) it also crashes if it encounters a file containing '\\'. something else should happen here; most likely vere should just ignore the file. |
||
---|---|---|
.github | ||
bin | ||
doc/spec | ||
extras | ||
nix | ||
pkg | ||
sh | ||
.eslintrc.js | ||
.gitattributes | ||
.gitignore | ||
.ignore | ||
.mailmap | ||
.stylish-haskell.yaml | ||
.vercelignore | ||
CONTRIBUTING.md | ||
default.nix | ||
lerna.json | ||
LICENSE.txt | ||
MAINTAINERS.md | ||
Makefile | ||
package-lock.json | ||
package.json | ||
README.md | ||
shell.nix |
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 OS
- herb, a tool for Unix control of an Urbit ship
- Source code for Landscape's web interface
- Source code for the vere virtual machine.
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/using/install. You'll be on the live network in a few minutes.
If you're interested in Urbit development, keep reading.
Development
Urbit uses Nix to manage builds. On Linux and macOS you can install Nix via:
curl -L https://nixos.org/nix/install | sh
You can optionally setup Nix to pull build artefacts from the binary cache that continuous integration uses. This will improve build times and avoid unnecessary recompilations of common dependencies. Once Nix has been installed you can setup Cachix via:
nix-env -iA cachix -f https://cachix.org/api/v1/install
cachix use ares
The Makefile in the project's root directory contains useful phony targets for building, installing, testing, and so on. You can use it to avoid dealing with Nix explicitly.
To build the Urbit virtual machine binary, for example, use:
make build
The test suite can similarly be run via a simple:
make test
Note that some of the Makefile targets need access to pills tracked via git LFS, so you'll also need to have those available locally:
git lfs install
git lfs pull
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.
For instructions on contributing to Landscape, see its guidelines.
You might also be interested in joining the urbit-dev mailing list.