expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-12-09 07:14:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

Revised all WSL documentaiton

Browse Source
This commit is contained in:
Philip Sargent
2022-12-22 15:10:14 +00:00
parent 01a821002e
commit 1be6e5cbfe
4 changed files with 213 additions and 176 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
handbook/computing/bulkupdatelaptop.html
View File

@@ -8,7 +8,7 @@
<body>
<h2 id="tophead">CUCC Expedition Handbook - Bulk Update laptop</h2>
<h1>Cave data - Bulk Updates</h1>
<h1>Cave data - Bulk Update Laptop</h1>
<p>You will already have explored what your laptop can do in the
<a href="basiclaptop.html">basic Expo laptop</a> guide,
@@ -62,11 +62,7 @@ raw survey notes (surveyscans), scanned cave centre-line plots and everything el
<p>You need to <a href="keyexchange.html">register a key with the expo server</a> to get upload (i.e. read/write) access. Do this first, Without it none of git, scp, ftp or rsync will work.
You can do this entirely on your own if you have access to the <i>expo laptop</i> to upload and install the public key generated by your laptop.</p>
<h4>QMs and scripts</h4>
<p>You may not need a full troggle software development machine if you are only fixing a small script. If you are, you need
<ul>
<li>python - maybe - but only if you are working on the <a href="../troggle/scriptsother.html">scripts in expoweb/noinfo/</a> such as <var>make-folklist.py</var> or some of the <a href="../troggle/scriptsqms.html">standalone QM scripts</a> - but not on troggle itself - then please use the as close to the same setup as you can to <a href="../troggle/troglaptop.html">the setup we use for troggle</a>. <img src="https://www.python.org/favicon.ico" width=64 hspace="20" align="right">
</ul>
<h3>Your own Bulk Update laptop</h3>
@@ -99,6 +95,29 @@ You can do this entirely on your own if you have access to the <i>expo laptop</i
<p>Read the <a href="winlaptop.html">Detailed Windows Configuration Instructions</a> for foconfiguring a Windows Bulk Update machine.
<h4>QMs and scripts</h4>
<p>You may not need a full troggle software development machine if you are only fixing a small script. If you are, you need
<ul>
<li>python - maybe - but only if you are working on the <a href="../troggle/scriptsother.html">scripts in expoweb/noinfo/</a> such as <var>make-folklist.py</var> or some of the <a href="../troggle/scriptsqms.html">standalone QM scripts</a> - but not on troggle itself - then please use the as close to the same setup as you can to <a href="../troggle/troglaptop.html">the setup we use for troggle</a>. <img src="https://www.python.org/favicon.ico" width=64 hspace="20" align="right">
</ul>
<h3>The Expo Laptop(s)</h3>
<p>[These notes are to remind nerds when configuring or updating a replacement <var>expo laptop</var>.]
<p>The <var>expo laptop</var> is configured as a "Bulk Update" laptop (including al the "Survey laptop" tools), but has a few extras.
<ul>
<li>Create a user 'expo'
<li>Add user 'expo' to <a href="https://www.how2shout.com/linux/2-ways-to-add-users-to-sudoers-group-in-debian-11/">the sudoers list</a> or alternatively <a href="https://vitux.com/how-to-make-a-user-an-administrator-in-debian/">use the gui</a> to do the same thing.
<li>Log in as user 'expo' again (so that ~/ = /home/expo/)
<li>Set up the expo Gmail account in Firefox
<li>Install Firezilla FTP software and <a href="fzconfig.html">download zilla-uploads.xml</a> to configure it
<li>Copy ~/.ssh/* from the previous install or from the other <var>expo laptop</var>
<li>Copy ~/expofiles from from the previous install or from the other <var>expo laptop</var>
<li>Run <a href="qstart-rsync.html">rsync</a> to ensure /expofiles is correctly identical to the server
<li>Configure git as user 'expo laptop' (or 'azirophale' or 'crowley') - see below, with expo Gmail address
<li><a href="qstart-git.html">git clone</a> the four repositories
<li>Check that you have a GPS trck editor installed, e.g. GPSprune
</ul>
<h2 id="git">Configuring git</h2>
<p>On a new machine you need to configure your git identity: