on master help sign in
Merge pull request #530 from ritfed-tabryg/v0.10-memory-hole

Remove references to v0.10.8 & fix binary paths

commit593c68e9123b6c31023b3211db9b37edeeaae79c authorpoprox <51337059+syzygyzer@users.noreply.github.com> dateTue 15 Dec 2020, 11:15 (6 years ago) parentb36353e533bce1
2 files changed+20−57
content/using/install.md+15−51 content/using/operations/hosting.md+5−6
content/using/install.md+15−51
@@ -80,11 +80,7 @@ Comets are disposable, free identities that can be used to quickly join the netw
8080To boot a comet, go into the command line and run the following command from the `urbit` directory you created during [Urbit installation](#installing-urbit):
8181
8282```sh
83−#macOS:
84−./urbit-v0.10.8-darwin/urbit -c mycomet
85−
86−#Linux:
87−./urbit-v0.10.8-linux64/urbit -c mycomet
83+./urbit -c mycomet
8884```
8985
9086Since your identity on the network is not verified, it may take up to an hour to generate your comet. As it boots, will spin out a bunch of boot messages and create a directory called `mycomet`. Toward the end of the boot process, you'll see something like:
@@ -104,11 +100,7 @@ To exit Urbit, use `Ctrl-D` or enter `|exit` into Dojo.
104100To start your ship up again, run the following from your `urbit` directory (note the lack of `-c` argument):
105101
106102```sh
107−#macOS:
108−./urbit-v0.10.8-darwin/urbit mycomet
109−
110−#Linux:
111−./urbit-v0.10.8-linux64/urbit mycomet
103+./urbit mycomet
112104```
113105
114106### The Dojo
@@ -222,21 +214,13 @@ Once you're inside, run the command below, except with `sampel-palnet` replaced
222214Urbit identity, and `path/to/my-planet.key` replaced with the path to your keyfile:
223215
224216```sh
225−#macOS:
226−./urbit-v0.10.8-darwin/urbit -w sampel-palnet -k path/to/my-planet.key
227−
228−#Linux:
229−./urbit-v0.10.8-linux64/urbit -w sampel-palnet -k path/to/my-planet.key
217+./urbit -w sampel-palnet -k path/to/my-planet.key
230218```
231219
232−Or, if you'd prefer to copy your key in, you can run:
220+Or, if you'd prefer to copy-paste your key, you can run:
233221
234222```sh
235−#macOS:
236−./urbit-v0.10.8-darwin/urbit -w sampel-palnet -G rAnDoMkEy
237−
238−#Linux:
239−./urbit-v0.10.8-linux64/urbit -w sampel-palnet -G rAnDoMkEy
223+./urbit -w sampel-palnet -G rAnDoMkEy
240224```
241225
242226Either command will create a directory called `sampel-palnet/` and begin building your ship. It may take a few minutes.
@@ -246,11 +230,7 @@ When your ship is finished booting, you will see either the `~sampel-palnet:dojo
246230To shut down your ship, use `Ctrl-D`. To start your ship up again, run the following from your `urbit` directory:
247231
248232```sh
249−#macOS:
250−./urbit-v0.10.8-darwin/urbit sampel-palnet
251−
252−#Linux:
253−./urbit-v0.10.8-linux64/urbit sampel-palnet
233+./urbit sampel-palnet
254234```
255235
256236Note that `sampel-palnet/` is the path of a folder, which we just created in your `urbit` directory. This folder is called your ship's **pier**.
@@ -271,46 +251,30 @@ Most updates to Urbit are downloaded and applied automatically as OTA (Over the
271251
272252To update to the latest binary, download and extract it to replace your existing one. Then run it as before.
273253
274−For example, if in your current `urbit` directory you have an `urbit-v0.10.7-<OS>` directory along with a ship directory called `mycomet`, and a new `urbit-v0.10.8-<OS>` binary was just released, then you'd run the following commands from your `urbit` directory:
275−
276−First shut down your ship, by running the following in dojo (or `Ctrl-D`).
254+First shut down your ship, by running the following in dojo (or with `Ctrl-D`).
277255```
278256|exit
279257```
280258
281−**NOTE**: Your ship itself can be reused, only the binary needs to be changed. This is why we have the directory structure configured as an `urbit` directory that contains your ship and your binary. This structure makes it easy to swap in new binaries. If you have your ship *inside* the `urbit-vX.XX.X` directory, move it out before deleting that directory.
282−
283−Delete the old binary directory from your `urbit` directory:
284−
285−```sh
286−#macOS:
287−rm -rf urbit-v0.10.7-darwin
288−
289−#Linux:
290−rm -rf urbit-v0.10.7-linux64
291−```
292−
293259Next download and extract the most recent binary from inside your `urbit` directory:
294260```sh
295261#macOS:
296−curl -O https://bootstrap.urbit.org/urbit-v0.10.8-darwin.tgz
297−tar xzf urbit-v0.10.8-darwin.tgz
262+wget --content-disposition https://urbit.org/install/mac/latest
263+tar zxvf ./darwin.tgz --strip=1
298264
299265#Linux:
300−curl -O https://bootstrap.urbit.org/urbit-v0.10.8-linux64.tgz
301−tar xzf urbit-v0.10.8-linux64.tgz
266+wget --content-disposition https://urbit.org/install/linux64/latest
267+tar zxvf ./linux64.tgz --strip=1
302268```
303269
270+**NOTE**: Do not delete the directory named after your ship. Your ship itself can be reused, only the binary needs to be changed. This is why we have the directory structure configured as an `urbit` directory that contains your ship and your binary. This structure makes it easy to swap in new binaries.
271+
304272Start up your ship with the new binary from your `urbit` directory:
305273```sh
306−#macOS:
307−./urbit-v0.10.8-darwin/urbit mycomet
308−
309−#Linux:
310−./urbit-v0.10.8-linux64/urbit mycomet
274+./urbit sampel-palnet
311275```
312276
313−Then you're good to go, in the future you'll just modify the version numbers in the example above to the most recent version.
277+Then you're good to go!
314278
315279### Breaches {#breaches}
316280
content/using/operations/hosting.md+5−6
@@ -106,22 +106,21 @@ Finally we're ready to install Urbit on your very own server. This part is actua
106106 $ ssh your_user@your_domain
107107 $ mkdir urbit
108108 $ cd urbit
109− $ curl -O https://bootstrap.urbit.org/urbit-v0.10.8-linux64.tgz
110− $ tar xzf urbit-v0.10.8-linux64.tgz
111− $ cd urbit-v0.10.8-linux64
109+ $ wget --content-disposition https://urbit.org/install/linux64/latest
110+ $ tar zxf ./linux64.tgz --strip=1
112111 $ sudo setcap 'cap_net_bind_service=+ep' urbit
113112 ```
114113 - Now we're going to tar up your local ship and send it to your server, from your local machine's urbit directory:
115114 ```
116115 $ 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
116+ $ scp <ship_dir_name>.tar.gz your_user@your_domain:urbit
118117 ```
119118 - Back on your server let's untar your ship and start it up with the Ames port we allowed through the firewall:
120119 ```
121120 $ ssh your_user@your_domain
122121 $ cd urbit
123122 $ tar -zxvf <ship_dir_name>.tar.gz
124− $ ./urbit-v0.10.8-linux64/urbit <ship_dir_name>
123+ $ ./urbit <ship_dir_name>
125124 ```
126125 - Now we run a few commands in Dojo to request a Let’s Encrypt cert for your
127126 domain. Replace `tld` with whatever your top-level domain is e.g. `com` in
@@ -142,7 +141,7 @@ Finally, to leave your Urbit running after you disconnect we can leave it in a S
142141 ```
143142 - This will start a screen session, we can now start up the Urbit ship from the `urbit` directory in this session:
144143 ```
145− $ ./urbit-v0.10.8-linux64/urbit <ship_dir_name>
144+ $ ./urbit <ship_dir_name>
146145 ```
147146 - Then we can disconnect from the screen session and leave the ship running with `control-a d`
148147 - To get back into the screen session: