@@ -17,12 +17,9 @@ This guide uses Digital Ocean as the cloud provider, but others can be used.
17## Create a Digital Ocean droplet
17## Create a Digital Ocean droplet
18 - Create an account on [Digital Ocean][Digital Ocean].
18 - Create an account on [Digital Ocean][Digital Ocean].
19 - Create a droplet with the following settings:
19 - Create a droplet with the following settings:
20− - **Image**: Ubuntu 18.04 x64
20+ - **Image**: Ubuntu 20.04 x64
21− - **Plan**: Standard
21+ - **Plan**: Basic
23− - **Minimum**: $10 (2GB/1CPU)
24− - **Recommended**: $15 (3GB/1CPU)
25− - **Bonus**: $20 (4GB/2CPU)
22+ - **Size**: $20 (4GB/2CPU)
26 - **Add block storage**: Skip
23 - **Add block storage**: Skip
27 - **Datacenter Region**: Choose the region closest to you.
24 - **Datacenter Region**: Choose the region closest to you.
28 - **VPC Network**: No VPC
25 - **VPC Network**: No VPC
@@ -43,16 +40,18 @@ There are a lot of domain name registrars you can use, this guide suggests [gand
43Once you've registered your domain you'll need to configure it to use Digital Ocean for DNS. The following steps are done on the Gandi website.
40Once you've registered your domain you'll need to configure it to use Digital Ocean for DNS. The following steps are done on the Gandi website.
44 - Click Domain on the left panel
41 - Click Domain on the left panel
45 - Click the domain you're going to use for Urbit
42 - Click the domain you're going to use for Urbit
46− - Click "Gandi's LiveDNS nameservers" under name servers on the overview page
43+ - Click "Gandi's LiveDNS" under Nameservers in the Domain configuration section of the overview page
47 - Click Change
44 - Click Change
48− - Remove Gandi servers and add the Digital Ocean ones instead:
45+ - Click External
46+ - Add the Digital Ocean nameservers:
49 - `ns1.digitalocean.com`
47 - `ns1.digitalocean.com`
50 - `ns2.digitalocean.com`
48 - `ns2.digitalocean.com`
51 - `ns3.digitalocean.com`
49 - `ns3.digitalocean.com`
52 - Save the change.
50 - Save the change.
53− - It can take some time for this change to propagate, but I found it to be pretty quick (a few minutes).
51+ - - It can take 12-24 hours for this change to propagate.
54 - Now that you've updated the DNS records you can add the domain to your droplet.
52 - Now that you've updated the DNS records you can add the domain to your droplet.
55− - Back on the DO site, click Networking from the left panel and then enter the domain you registered to have it set for your project.
53+ - - Back on the DO site, click Networking from the left panel and then enter the domain you registered.
54+ - Click on that domain and add an A record that directs to the IP of your droplet (found on your droplet's page).
57## Creating your non-root user
56## Creating your non-root user
58With our domain in place we're now ready to actually log into the box and start to configure the server itself.
57With our domain in place we're now ready to actually log into the box and start to configure the server itself.
@@ -106,6 +105,8 @@ Finally we're ready to install Urbit on your very own server. This part is actua
106 - Next we're going to install Urbit on the server and permit it to bind to the web port:
105 - Next we're going to install Urbit on the server and permit it to bind to the web port:
108 $ ssh your_user@your_domain
107 $ ssh your_user@your_domain
109 $ curl -O https://bootstrap.urbit.org/urbit-v0.10.8-linux64.tgz
110 $ curl -O https://bootstrap.urbit.org/urbit-v0.10.8-linux64.tgz
110 $ tar xzf urbit-v0.10.8-linux64.tgz
111 $ tar xzf urbit-v0.10.8-linux64.tgz
111 $ cd urbit-v0.10.8-linux64
112 $ cd urbit-v0.10.8-linux64
@@ -114,14 +115,14 @@ Finally we're ready to install Urbit on your very own server. This part is actua
114 - Now we're going to tar up your local ship and send it to your server, from your local machine's urbit directory:
115 - Now we're going to tar up your local ship and send it to your server, from your local machine's urbit directory:
116 $ tar -zcvf <ship_dir_name>.tar.gz <ship_dir_name>
117 $ tar -zcvf <ship_dir_name>.tar.gz <ship_dir_name>
117− $ scp <ship_dir_name>.tar.gz your_user@your_domain:/home/your_user/urbit-v0.10.8-linux64
118+ $ scp <ship_dir_name>.tar.gz your_user@your_domain:/home/your_user/urbit
119 - Back on your server let's untar your ship and start it up with the Ames port we allowed through the firewall:
120 - Back on your server let's untar your ship and start it up with the Ames port we allowed through the firewall:
121 $ ssh your_user@your_domain
122 $ ssh your_user@your_domain
122− $ cd urbit-v0.10.8-linux64
123+ $ cd urbit
123 $ tar -zxvf <ship_dir_name>.tar.gz
124 $ tar -zxvf <ship_dir_name>.tar.gz
124− $ ./urbit <ship_dir_name>
125+ $ ./urbit-v0.10.8-linux64/urbit <ship_dir_name>
126 - Now we run a few commands in Dojo to request a Let’s Encrypt cert for your domain (replace `tld` with whatever your top-level domain is e.g. `com` in `example.com`:
127 - Now we run a few commands in Dojo to request a Let’s Encrypt cert for your domain (replace `tld` with whatever your top-level domain is e.g. `com` in `example.com`:
@@ -137,12 +138,12 @@ Finally, to leave your Urbit running after you disconnect we can leave it in a S
138 $ screen -S urbit
139 $ screen -S urbit
140− - This will start a screen session, we can now start up the Urbit ship in this session:
141+ - This will start a screen session, we can now start up the Urbit ship from the `urbit` directory in this session:
142− $ ./urbit <ship_dir_name>
143+ $ ./urbit-v0.10.8-linux64/urbit <ship_dir_name>
144 - Then we can disconnect from the screen session and leave the ship running with `control-a d`
145 - Then we can disconnect from the screen session and leave the ship running with `control-a d`
145− - To get back into the screen sesssion:
146+ - To get back into the screen session:
147 $ screen -r
148 $ screen -r