An operating function
Go to file
Joe Bryan c5394b775f Merge branch 'release/next-vere' into jb/restage-leer
* release/next-vere: (57 commits)
  u3: initializes head/tail in u3i_defcons() (under U3_MEMORY_DEBUG)
  king: actually try shutting down the piers
  king: --serf="" is a host option, not a per ship option.
  u3: optimizes +wyt:in jet, gated by compile-time assertion
  u3: further optimizes +lent jet, gated by compile-time assertion
  u3: refactors allocator constants, adds u3a_cells and u3a_maximum
  u3: optimizes +lent jet, avoiding u3i_vint() while possible
  u3: moves cell allocation counter into u3a_celloc()
  u3: fixes memory leak introduced in +murn jet
  u3: fixes mismatches in +div and +dvr jets
  u3: fixes memory leaks in +dvr and +sqt jets
  u3: rewrites +flop jet using new list iteration idiom
  u3: rewrites +weld jet using u3i_defcons()
  u3: rewrites +scag jet using u3i_defcons()
  u3: rewrites +murn jet using u3i_defcons()
  u3: rewrites +turn jet using u3i_defcons()
  u3: adds u3i_defcons(), deferred cell constructor
  vere: add missing function comment
  vere: use h2o functions for finding cookie header
  vere: put runtime http bindings under /~_~
  ...
2020-10-07 19:48:58 -07:00
.github/ISSUE_TEMPLATE meta: add issue links to landscape, urbit-dev 2020-08-31 21:34:15 -04:00
bin glob: update to 0v3.u1ets.ipgbo.eo23m.md70h.djpj0 2020-09-16 00:32:23 -04:00
doc/spec Misc cleanup blocking CC-Release. (#1249) 2019-04-24 17:27:27 -07:00
extras Misc cleanup blocking CC-Release. (#1249) 2019-04-24 17:27:27 -07:00
nix libsigsegv: disable stack vma check on arm 2020-07-27 23:33:14 -05:00
pkg Merge branch 'release/next-vere' into jb/restage-leer 2020-10-07 19:48:58 -07:00
sh Merge branch 'master' into jb/ipc-redux 2020-06-26 13:33:00 -07:00
.gitattributes gitattributes: export-ignore test directories [ci skip] 2020-02-01 12:07:13 +04:00
.gitignore gitignore: re-add mystery lines [ci skip] 2020-03-01 23:19:01 +04:00
.ignore Can now |hi to King Haskell over Ames! (and merged Master) 2019-07-31 22:16:02 -07:00
.mailmap mailmap: add pkova [ci skip] 2020-01-30 15:53:19 +04:00
.stylish-haskell.yaml stylish-haskell 2019-07-12 12:27:15 -07:00
.travis.yml Squashed commit of the following: 2020-06-25 03:25:31 -04:00
CONTRIBUTING.md CONTRIBUTING: add link to maintainers in pkg/arvo 2020-08-31 21:35:52 -04:00
default.nix Nix Build + Monorepo Structure (#1196) 2019-03-04 16:43:53 -08:00
LICENSE.txt Restore toplevel LICENSE.txt file. 2020-01-28 13:24:39 -08:00
MAINTAINERS.md MAINTAINERS: update for versioned JS bundles 2020-08-03 10:15:21 +10:00
Makefile Build Linux static executables. (#2120) 2019-12-19 08:11:59 -08:00
README.md README: general legibility changes 2020-08-31 21:35:04 -04:00

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:

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

Build Status

Urbit uses Nix to manage builds. On Linux and macOS you can install Nix via:

curl -L https://nixos.org/nix/install | sh

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.