ilyakooo0/urbit
1
0
Fork 0
mirror of https://github.com/ilyakooo0/urbit.git synced 2024-12-14 17:41:33 +03:00
Code Issues Packages Projects Releases Wiki Activity
An operating function
20,262 Commits 6 Branches 0 Tags 164 MiB
hoon 79.3%
TypeScript 16.7%
JavaScript 2.3%
CSS 0.4%
Python 0.4%
Other 0.8%
2af18a6659
Go to file
Joe Bryan 2af18a6659 Merge branch 'release/next-vere' into jb/stir-tail 
* release/next-vere: (317 commits)
  u3: improves error output on c3_assert()
  vere: improves error messages on ipc EOF
  vere: fixes %trim effect handler
  vere: fix crash on u3_pier_bail()
  king: move most things from debug log level to info
  vere: support rendering +stub as ansi escape codes
  king: change logging from tracing to info in Wai.hs
  king dawn: export functions used in tests
  king dawn: nits
  king dawn: remove stray marks
  king dawn: instead of crashing, return an error
  king dawn: replace web3 usage with hand rolled jsonrpc messages.
  vere: v0.10.9-rc1
  vere: more correct lane cache commentary
  vere: reset instead of decrement scry fail counter
  vere: ames.c stylistic improvements
  vere: only touch forward queue counter if scrying
  vere: cache lanes for stateless forwarding
  vere: give up ames scry after successive failures
  vere: properly clean up dropped laneless packets
  ...
2020-09-11 12:53:30 -07:00
.github/ISSUE_TEMPLATE ISSUE_TEMPLATEs: use +trouble instead of .^(@uv %cz /=base=) 2020-08-01 09:39:36 -05:00
bin glob: update to 0v2.pbthv.gd1q2.h2ura.5esrn.d361c 2020-08-11 22:14:07 -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/stir-tail 2020-09-11 12:53:30 -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 meta: update CONTRIBUTING, MAINTAINERS 2020-03-16 11:32:55 +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 Updated nix install command 2020-07-02 20:05:59 -07:00

README.md

Urbit

A personal server operating function.

The Urbit address space, Azimuth, is now live on the Ethereum blockchain. You can find it at 0x223c067f8cf28ae173ee5cafea60ca44c335fecb or azimuth.eth. Owners of Azimuth points (galaxies, stars, or planets) can view or manage them using Bridge, and can also use them to boot Arvo, the Urbit OS.

Install

To install and run Urbit, please follow the instructions at urbit.org/docs/getting-started/. 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 Urbit, 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.

You might also be interested in: