An operating function (Prototype)
Go to file
J c1b259af5b interface, gcp: don't spam the console with 500s
Options here were: make the get-token thread try to return a unit, or
write a different thread to check whether GCP Storage seemed to be
configured and poll on that thread, or move the whole thing into a Gall
app.

The compromise between time-to-implement and overall cleanliness seemed
to be to write a different thread that just checks whether the settings
fields have been poked. Unfortunately this means GcpManager is now a
somewhat hefty JavaScript state machine.

Took out the logic to check whether S3 was configured in GcpManager,
since it was really only there to prevent spamming the console with
500s. If you have both S3 and GCP Storage configured for some reason,
you will now use GCP per the logic in useStorage.
2021-02-26 23:42:57 +00:00
.github meta: update janeway dep in glob action 2021-02-04 03:21:22 +09:00
bin pill: solid 2021-02-23 20:44:18 +00: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 docker-image: Pass -t flag to vere if not in an interactive container 2021-01-16 19:44:04 -05:00
pkg interface, gcp: don't spam the console with 500s 2021-02-26 23:42:57 +00:00
sh sh/poke-gcp-account-json: poke gcp storage values 2021-02-23 21:10:50 +00:00
.gitattributes meta: do not treat arvo JS files as binary 2020-10-08 13:08:00 +10:00
.gitignore build: reorganising top-level .gitignore and add nix ignores 2020-10-27 14:28:07 +01: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
CONTRIBUTING.md meta: add dev ship instructions from master 2020-09-28 21:58:35 -04:00
default.nix king: restore king to rightful place in default.nix 2021-01-25 17:34:46 -08:00
LICENSE.txt Restore toplevel LICENSE.txt file. 2020-01-28 13:24:39 -08:00
MAINTAINERS.md meta: update MAINTAINERS for auto-deploy 2021-01-06 12:34:39 -05:00
Makefile nix: don't install urbit-debug by default. 2020-12-07 10:35:36 -05:00
README.md build: document use of ares.cachix.org in the top-level README 2020-12-14 09:22:40 +01:00
shell.nix build: github actions workflow configuration 2020-11-15 15:05:13 +01: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

License Build Nix Cachix

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.