593c68e · urbit.org · git.iko.soy

git.iko.soy/urbit.org

Merge pull request #530 from ritfed-tabryg/v0.10-memory-hole

593c68epoprox6 years ago

content/using/install.md+15−51

@@ -80,11 +80,7 @@ Comets are disposable, free identities that can be used to quickly join the netw

80To boot a comet, go into the command line and run the following command from the `urbit` directory you created during [Urbit installation](#installing-urbit):

82```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

88```

84```

90Since 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:

86Since 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.

104To start your ship up again, run the following from your `urbit` directory (note the lack of `-c` argument):

100To start your ship up again, run the following from your `urbit` directory (note the lack of `-c` argument):

105

101

106```sh

102```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

112```

104```

113

105

114### The Dojo

106### The Dojo

@@ -222,21 +214,13 @@ Once you're inside, run the command below, except with `sampel-palnet` replaced

222Urbit identity, and `path/to/my-planet.key` replaced with the path to your keyfile:

214Urbit identity, and `path/to/my-planet.key` replaced with the path to your keyfile:

223

215

224```sh

216```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

230```

218```

231

219

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:

233

221

234```sh

222```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

240```

224```

241

225

242Either command will create a directory called `sampel-palnet/` and begin building your ship. It may take a few minutes.

226Either 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

246To shut down your ship, use `Ctrl-D`. To start your ship up again, run the following from your `urbit` directory:

230To shut down your ship, use `Ctrl-D`. To start your ship up again, run the following from your `urbit` directory:

247

231

248```sh

232```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

254```

234```

255

235

256Note 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**.

236Note 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

271

251

272To update to the latest binary, download and extract it to replace your existing one. Then run it as before.

252To update to the latest binary, download and extract it to replace your existing one. Then run it as before.

273

253

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`).

277```

255```

278|exit

256|exit

279```

257```

280

258

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−

293Next download and extract the most recent binary from inside your `urbit` directory:

259Next download and extract the most recent binary from inside your `urbit` directory:

294```sh

260```sh

295#macOS:

261#macOS:

296−curl -O https://bootstrap.urbit.org/urbit-v0.10.8-darwin.tgz

262+wget --content-disposition https://urbit.org/install/mac/latest

297−tar xzf urbit-v0.10.8-darwin.tgz

263+tar zxvf ./darwin.tgz --strip=1

298

264

299#Linux:

265#Linux:

300−curl -O https://bootstrap.urbit.org/urbit-v0.10.8-linux64.tgz

266+wget --content-disposition https://urbit.org/install/linux64/latest

301−tar xzf urbit-v0.10.8-linux64.tgz

267+tar zxvf ./linux64.tgz --strip=1

302```

268```

303

269

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+

304Start up your ship with the new binary from your `urbit` directory:

272Start up your ship with the new binary from your `urbit` directory:

305```sh

273```sh

306−#macOS:

274+./urbit sampel-palnet

307−./urbit-v0.10.8-darwin/urbit mycomet

308−

309−#Linux:

310−./urbit-v0.10.8-linux64/urbit mycomet

311```

275```

312

276

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!

314

278

315### Breaches {#breaches}

279### Breaches {#breaches}

316

280

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

106 $ ssh your_user@your_domain

107 $ mkdir urbit

108 $ cd urbit

109− $ curl -O https://bootstrap.urbit.org/urbit-v0.10.8-linux64.tgz

109+ $ wget --content-disposition https://urbit.org/install/linux64/latest

110− $ tar xzf urbit-v0.10.8-linux64.tgz

110+ $ tar zxf ./linux64.tgz --strip=1

111− $ cd urbit-v0.10.8-linux64

112 $ sudo setcap 'cap_net_bind_service=+ep' urbit

111 $ sudo setcap 'cap_net_bind_service=+ep' urbit

113 ```

112 ```

114 - Now we're going to tar up your local ship and send it to your server, from your local machine's urbit directory:

113 - Now we're going to tar up your local ship and send it to your server, from your local machine's urbit directory:

115 ```

114 ```

116 $ tar -zcvf <ship_dir_name>.tar.gz <ship_dir_name>

115 $ 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

118 ```

117 ```

119 - Back on your server let's untar your ship and start it up with the Ames port we allowed through the firewall:

118 - Back on your server let's untar your ship and start it up with the Ames port we allowed through the firewall:

120 ```

119 ```

121 $ ssh your_user@your_domain

120 $ ssh your_user@your_domain

122 $ cd urbit

121 $ cd urbit

123 $ tar -zxvf <ship_dir_name>.tar.gz

122 $ tar -zxvf <ship_dir_name>.tar.gz

124− $ ./urbit-v0.10.8-linux64/urbit <ship_dir_name>

123+ $ ./urbit <ship_dir_name>

125 ```

124 ```

126 - Now we run a few commands in Dojo to request a Let’s Encrypt cert for your

125 - Now we run a few commands in Dojo to request a Let’s Encrypt cert for your

127 domain. Replace `tld` with whatever your top-level domain is e.g. `com` in

126 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

142 ```

141 ```

143 - This will start a screen session, we can now start up the Urbit ship from the `urbit` directory in this session:

142 - This will start a screen session, we can now start up the Urbit ship from the `urbit` directory in this session:

144 ```

143 ```

145− $ ./urbit-v0.10.8-linux64/urbit <ship_dir_name>

144+ $ ./urbit <ship_dir_name>

146 ```

145 ```

147 - Then we can disconnect from the screen session and leave the ship running with `control-a d`

146 - Then we can disconnect from the screen session and leave the ship running with `control-a d`

148 - To get back into the screen session:

147 - To get back into the screen session: