ship-deployment-guide

To deploy an Urbit planet on Ubuntu, you must prepare the system, install the Urbit binary, configure network settings like port forwarding, and integrate the ship with systemd for production reliability.

Urbit planets are permanent network identities requiring keyfile management, while comets are free, ephemeral identities. Both deployment processes involve similar system preparation but differ in keyfile acquisition and network validation steps.

Yes, you can use systemd to auto-start your Urbit ship on Debian. The deployment process includes specific steps for creating systemd service files to ensure your planet or comet runs reliably in production.

Configuring networking for an Urbit ship requires setting up firewall rules, configuring port forwarding, and establishing DNS with SSL/TLS to ensure secure and reliable external network connectivity for your server.

Fake ships are used strictly for offline Urbit development and testing. They do not require keyfile management or external network configuration, but they cannot interact with the live Urbit network as a planet or comet would.

Urbit planet deployment can fail during keyfile management if the keyfile is missing, incorrectly formatted, or lacks proper permissions. Following the step-by-step deployment guide ensures correct keyfile installation and validation.