@@ -17,12 +17,8 @@ This guide uses Digital Ocean as the cloud provider, but others can be used.
1717## Create a Digital Ocean droplet
1818 - Create an account on [Digital Ocean][Digital Ocean].
1919 - Create a droplet with the following settings:
20− - **Image**: Ubuntu 18.04 x64
21− - **Plan**: Standard
22− - **Size**:
23− - **Minimum**: $10 (2GB/1CPU)
24− - **Recommended**: $15 (3GB/1CPU)
25− - **Bonus**: $20 (4GB/2CPU)
20+ - **Image**: Ubuntu 20.04 x64
21+ - **Plan**: 4GB RAM
2622 - **Add block storage**: Skip
2723 - **Datacenter Region**: Choose the region closest to you.
2824 - **VPC Network**: No VPC
@@ -43,16 +39,18 @@ There are a lot of domain name registrars you can use, this guide suggests [gand
4339Once 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.
4440 - Click Domain on the left panel
4541 - Click the domain you're going to use for Urbit
46− - Click "Gandi's LiveDNS nameservers" under name servers on the overview page
42+ - Click "Gandi's LiveDNS" under Nameservers in the Domain configuration section of the overview page
4743 - Click Change
48− - Remove Gandi servers and add the Digital Ocean ones instead:
44+ - Click External
45+ - Add the Digital Ocean nameservers:
4946 - `ns1.digitalocean.com`
5047 - `ns2.digitalocean.com`
5148 - `ns3.digitalocean.com`
5249 - 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).
50+ - - It can take 12-24 hours for this change to propagate.
5451 - 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.
52+ - - Back on the DO site, click Networking from the left panel and then enter the domain you registered.
53+ - Click on that domain and add an A record that directs to the IP of your droplet (found on your droplet's page).
5654
5755## Creating your non-root user
5856With our domain in place we're now ready to actually log into the box and start to configure the server itself.
@@ -106,6 +104,8 @@ Finally we're ready to install Urbit on your very own server. This part is actua
106104 - Next we're going to install Urbit on the server and permit it to bind to the web port:
107105 ```
108106 $ ssh your_user@your_domain
107+ $ mkdir urbit
108+ $ cd urbit
109109 $ curl -O https://bootstrap.urbit.org/urbit-v0.10.8-linux64.tgz
110110 $ tar xzf urbit-v0.10.8-linux64.tgz
111111 $ cd urbit-v0.10.8-linux64
@@ -114,14 +114,14 @@ Finally we're ready to install Urbit on your very own server. This part is actua
114114 - Now we're going to tar up your local ship and send it to your server, from your local machine's urbit directory:
115115 ```
116116 $ 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
117+ $ scp <ship_dir_name>.tar.gz your_user@your_domain:/home/your_user/urbit
118118 ```
119119 - Back on your server let's untar your ship and start it up with the Ames port we allowed through the firewall:
120120 ```
121121 $ ssh your_user@your_domain
122− $ cd urbit-v0.10.8-linux64
122+ $ cd urbit
123123 $ tar -zxvf <ship_dir_name>.tar.gz
124− $ ./urbit <ship_dir_name>
124+ $ ./urbit-v0.10.8-linux64/urbit <ship_dir_name>
125125 ```
126126 - 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`:
127127 ```
@@ -137,12 +137,12 @@ Finally, to leave your Urbit running after you disconnect we can leave it in a S
137137 ```
138138 $ screen -S urbit
139139 ```
140− - This will start a screen session, we can now start up the Urbit ship in this session:
140+ - This will start a screen session, we can now start up the Urbit ship from the `urbit` directory in this session:
141141 ```
142− $ ./urbit <ship_dir_name>
142+ $ ./urbit-v0.10.8-linux64/urbit <ship_dir_name>
143143 ```
144144 - 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:
145+ - To get back into the screen session:
146146 ```
147147 $ screen -r
148148 ```