This is meant to serve as a backend for future turnkey Urbit appliances or IoT hubs by providing a collection of scripts, config files, and supporting infrastructure to enable the generation of custom Armbian Linux images with Urbit ready to run as service out of the box.
“An epiphyte uses a tree for physical support but does not drawn nourishment from it.”
I’ve been running Urbit on various ARM powered devices since November 2019 and have seen Urbit on ARM evolve from a curious toy into a viable platform for daily Urbit usage, ready to be used on the cloud or a credit card sized microserver hidden in the corner of a room.
As Urbit has matured, the flaws with some of those credit card sized devices have become increasingly apparent. On the dominant platform, the Raspberry Pi, the default 32-bit software and limited storage interfaces have made running Urbit on them sometimes difficult even for the hardy explorers that Urbit attracts.
Urbit is often explained as an “overlay OS” but this term encourages an idealism that neglects the importance of what is underneath Urbit. A more complete term might be “epiphyte OS”, which prompts thoughts about what is supporting Urbit and allowing it to reach its heights.
In order for Urbit to thrive on small, cheap, and locally hosted devices a more solid foundation needs to be built, one that will allow for flexible experimentation with devices bought for the purpose of running Urbit - not just some neglected Raspberry Pi pressed into service on a whim.
This is a first attempt at building such a base.
This is a package of scripts and configuration files intended to be used in a userpatches overlay for Armbian. Though deliverables include an image intended for a particular device (the NanoPi M4V2) the advantage of Armbian over other methods of creating an embedded Linux image is the ease of targeting a diverse set of devices without time consuming setup.
It should be possible to take this overlay and use it with the Armbian build tool to create Urbit ready images for about 38 different platforms with little or no modification. The scripts and configuration files that provide the turnkey Urbit functionality should be universally applicable to most Linux distributions with udev and systemd, and can be installed separately or integrated into other embedded Linux images.
Core functionality will be handled by a service which runs at boot:
Outside infrastructure for this is an APT repository to hold the most up-to-date AArch64 versions of Urbit and other packages required to enable turnkey functionality.
Armbian image to additionally include:
An image file ready to flash to a device (I’ve chosen the NanoPi M4V2) and the files used to generate it, published in a github repository. Service and script files will be published in a separate repository, with additional repositories for the deb package control files and scripts for building the urbit and urbit-scripts .deb packages.
Finally, a rough example of a rudimentary frontend will be demonstrated in a blog post style write-up with screenshots/pictures/videos as necessary to illustrate: the process of creating an image with the Armbian build tool, flashing it to a device, and the device giving information to the user about the process of starting Urbit and where to access landscape after the boot finishes.
This is meant to be the start of a Linux distribution designed for self-hosted Urbit devices, but which provides more than just Urbit.
It has the potential to evolve into a system that makes it easier for users to self host their own S3 buckets with MinIO, run IoT gateways on the device which can communicate with Urbit, and help with the setup of a local bitcoin node.
The development of this backend will support UX experiments with a frontend meant to create a user friendly, turnkey-style Urbit device.