expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-12-08 23:04:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

De-tortoising the handbook

Browse Source
This commit is contained in:
Philip Sargent
2020-04-24 21:20:40 +01:00
parent 5a3cd2099c
commit 31ffca841b
7 changed files with 19 additions and 64 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
handbook/computing/basiclaptop.html
View File

@@ -16,7 +16,7 @@
<ol>
<li>Register an SSH key</a> with an expo nerd i.e 'get a login'. (see "Key Configuration" below)</li>
<li>Install <a href="#software">git version control software</a> to download ("clone"), view and edit caving data.</li>
<li>Clone three <a href="manual.html#repositories">expo repositories</a> so you have the files on your machine.</li>
<li>Clone three <a href="manual.html#repositories">expo repositories</a> <var>loser, drawings</var> and <var>expoweb</var> so you have the files on your machine. (Use the <a href="qstart-git.html">git reminder</a> for how to do this, e.g. <em>git clone ssh://expo@expo.survex.com:/home/expo/expoweb</em></li>
<li>Install survex, and therion or tunnel for editing cave data.
</ol>

10
handbook/computing/keyexchange.html
View File

@@ -80,12 +80,10 @@ Be <b>extremely careful</b> to type ">>" and not ">" in the fourth line below ot
<br /><font color=blue">expo@expo:~$</font> cd .ssh
<br /><font color=blue">expo@expo:~$</font> cp -p authorized_keys authorized_keys.backup
<br /><font color=blue">expo@expo:~/.ssh$</font> cat keys/id_rsa.pub >>authorized_keys
<br /><font color=blue">expo@expo:~/.ssh$</font> ./list-keys.sh
<br /><font color=blue">expo@expo:~/.ssh$</font> cat list-of-key-owners
<br /><font color=blue">expo@expo:~/.ssh$</font> tail -n 1 authorized_keys
</tt>
This adds your key on to the end of the authorized keys list, runs a little script to extract the names of all the people who have added keys (24 keys as of Jan.2020) and prints out the list. You should see that the last line says:<br />
<span style="font-family:monospace; size=x-small; background-color: lightgray">anathema.device@crowley</span>
<li>Now your public key is installed for your second machine. You check that it works by logging into the expo server using ssh from your second machine.
This adds your key on to the end of the authorized keys list and prints the last line - which should be your key that you just added.
<li>Now your public key is installed for your second machine. You check that it works by logging into the expo server using ssh from your second machine: <em>ssh expo@expo.survex.com </em>.
</p>
<p>Note that by using sFTP like this we avoid having to use a text editor over ssh. If you know what you are doing you can do this of course, but the above process is less likely to cause problems for a Windows user setting up their phone as a second device where they are not experienced with vi or nano.
@@ -93,7 +91,7 @@ This adds your key on to the end of the authorized keys list, runs a little scri
</ol>
<hr />
Return to <a href="basiclaptop.html">Setting up a basic laptop</a>
<div id="menu">
<ul id="links">
<li><a href="../index.htm">Handbook</a>