urbit/shrub
1
1
Fork 0
mirror of https://github.com/urbit/shrub.git synced 2024-12-25 04:52:06 +03:00
Code Issues Packages Projects Releases Wiki Activity
An operating function (Prototype)
17,185 Commits 768 Branches 10 Tags 215 MiB
hoon 80.4%
TypeScript 14.6%
JavaScript 3.2%
CSS 0.6%
Python 0.3%
Other 0.8%
be5fb8b9cf
Go to file
Jared Tobin be5fb8b9cf
Merge branch 'king-haskell' (#2107) 
* origin/king-haskell: (411 commits)
  Fix counting bug in event log replay.
  fix progress bar in daemon mode
  Got Linux release builds working again.
  king: style improvements
  king: Build without warnings.
  Fix king-haskell Linux release build.
  Update scripts to point to `urbit-king`.
  Renamed modules Ur.** to Urbit.** to be consistent with urbit-{atom,hob}
  king: Rename `king` package to `urbit-king`.
  Clean up `Urbit.Atom` and move it into it's own package.
  Module structure, doc strings
  Bump stackage version.
  Got docs to build.
  king haskell: automatically connect to terminal when running a ship
  king: add partial-replay and --dry-from
  Make sure we close HTTP sockets on close (or reconfigure).
  Hack around terminfo database problem.
  Fixed bug in HTTP Server (only first block from stream was handled).
  Logging for event sourced responses.
  Cleanup port binding logic.
  ...

Signed-off-by: Jared Tobin <jared@tlon.io>
2020-02-10 18:53:41 +04:00
bin ford: ignore spurious clay responses 2020-01-29 15:11:36 +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 Revert "Merge branch 'jt/urbit-large-log' (#2211)" 2020-01-31 15:26:15 +04:00
pkg Merge branch 'master' of github.com:urbit/urbit into king-haskell 2020-02-05 15:44:11 -08:00
sh Merge branch 'master' of github.com:urbit/urbit into king-haskell 2020-02-05 15:44:11 -08:00
.gitattributes gitattributes: export-ignore test directories [ci skip] 2020-02-01 12:07:13 +04:00
.gitignore Merge branch 'king-haskell' of github.com:urbit/urbit into king-haskell 2019-12-16 15:03:50 -08: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 Update scripts to point to urbit-king. 2020-01-23 21:34:21 -08:00
CONTRIBUTING.md contributing: use alternative rebase tutorial [ci skip] 2019-12-18 08:29:22 -03:30
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 meta: add a basic maintainers' guide [ci skip] 2019-12-21 13:44:01 -03:30
Makefile Build Linux static executables. (#2120) 2019-12-19 08:11:59 -08:00
README.md readme: update bridge URL [ci skip] 2020-01-23 04:38:27 +04: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 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: