expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-11-22 07:11:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

laptop config & to-do printing update

Browse Source
This commit is contained in:
Philip Sargent 2020-04-03 21:55:58 +01:00
parent f8d43baa4d
commit e06dafa0af
3 changed files with 148 additions and 104 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
handbook/computing/winlaptop.html
View File

@ -8,9 +8,15 @@
<body>
<h2 id="tophead">CUCC Expedition Handbook - Computers</h2>
<h1>Setting up an Expo laptop - using Microsoft Windows</h1>
<h1>Setting up a Windows expo laptop</h1>
<p>First read the generic instructions for all the software installations you will need:
<br>
<a href="yourlaptop.html">Setting up a machine for Expo</a>
<br>
<a href="basiclaptop.html">Setting up a minimal Expo laptop</a>
</p>
<p>A work in progress.
<p>It used to be quite simple: software equivalents existed for Windows for everything we needed. Since Spring 2018, we unfortunately have to use ssh keys. This has simply added an extra step for most things, but has made one thing (rsync) really quite hard to get working.
<p>What makes this all much more tiresome is that Microsoft are introducing some cool new ways of interacting with Linux systems but these are new and need some effort to get configured correctly. See the end of this page for more details.
<ul>
@ -23,7 +29,7 @@
<li><a href="#hard">Things that are really, really hard</a><br />
- using rsync <br />
- large-scale updating of several folders at once on expofiles without overwriting other people's work (which means using rsync)<br />
- well not "hard" exactly, but complicated with lot of steps that are easy to get wrong and with poor feedback as to whether you have done each step correctlyS
- well not "hard" exactly, but complicated with lot of steps that are easy to get wrong and with poor feedback as to whether you have done each step correctly.
<li><a href="#bold">Things for the bold</a><br />
- using WSL2, Linux virtual machines and Docker containers
</ul>
@ -34,7 +40,7 @@
<h4>Key management using PuTTy</h4>
<p>Most Windows software that we recommend "just works" if you have set up PuTTy and have done the <a href="keyexchange.html">key-pair setup</a> and are running a local ssh agent (pagent) automatically at boot up on your laptop.
<p>Some software, such as the commercial (but free) GitKraken, requires that you click a checkbox to say that you are "using local SSH agent" rather than specifying ssh private keys explicitly (File->Preferences->Authentication in GitKraken).
<p>Some software (such as FIlezilla) defaults to using the local agent and it "just works".
<p>Some software (such as Filezilla) defaults to using the local agent and it "just works".
<h3 id="problems">Things that cause problems</h3>
@ -176,13 +182,5 @@ Now finally you can use all the usual command line tools at yor wsl command line
<hr />
<ul id="links">
<li><a href="../index.htm">Handbook</a>
<li><a href="yourlaptop.html">Your laptop</a>
<li><a href="../../infodx.htm">Main index</a></li>
</ul>
</div>
</body>
</html>

24
handbook/computing/x-todo-styles.css
View File

@ -53,18 +53,21 @@ button:active {
h2, h3, h4 {
color: #39b2e5;
margin-bottom: 0;
line-height: 0.6;
}
dd {
font: 18px Calibri, sanserif;
font-weight: normal;
color: 6083BF;
display: block;
#list-style-type: disc;
line-height: 1.3;
margin-left: 1.0em;
}
dd:before {
content: "- ";
content: "» ";
}
/* Default State */
@ -72,9 +75,8 @@ dt {
font: 20px Calibri, sanserif;
font-weight: bold;
color: 6083BF;
margin-top: 0.4em;
#margin-left: -1.2em;
margin-left: 0;
margin-top: 0.2em;
margin-left: 1.0em;
margin-right: 5em;
#list-style-type: none;
line-height: 1.4;
@ -88,3 +90,17 @@ input[type=checkbox] ~ dl dd {
input[type=checkbox]:checked ~ dl dd {
display: none;
}
@media only print, print)
{
b {
font-size: 10pt;
}
dt, p {
font: 1.0em Calibri, sanserif;
}
dd {
font: 0.8em Calibri, sanserif;
}
}

206
handbook/computing/x-todo.html
View File

@ -1,11 +1,11 @@
<!DOCTYPE html>
<html>
<head>
<title>Expo Systems Exptl. To-Do List</title>
<title>Expo Systems - Experimental To-Do List</title>
<meta charset="utf-8">
</head>
<body>
<h1>Expo Systems Exptl. To-Do List</h1>
<h1>Experimental expo To-Do List</h1>
<link rel="stylesheet" type="text/css" href="x-todo-styles.css" />
<button onclick="window.location.href = 'x-todo.html';">Update this to-do list</button>
<!--
@ -18,135 +18,165 @@
<h2>Experimental</h2>
<p>Click on a sub-heading to hide and reveal the individual to-do items. If a heading is in italics, then there are hidden items.
<p>Edit this page by clicking on the big blue button. It uses the same "Edit this page" function that you may have used before. But this is not working yet. Please do not try as that will currently delete all the Javascript that makes the hide/reveal functions work.
<h2>Taken from file on ::expoweb::/TODO </h2>
<dl>
<dt>Add missing images to logbooks</dt>
<dd>
2000, 2008, 2009, 2011</dd>
<dd>
fix corrupted image in 2001 log</dd>
<p>Printing this page uses a much smaller font. Complain to a nerd if you don't like this behaviour.
<p><span style="text-decoration: line-through;">Edit this page by clicking on the big blue button. It uses the same "Edit this page" function that you may have used before.</span> <em>But that is not working yet. Please do not try as that will currently delete all the Javascript that makes the hide/reveal functions work.</em>
<p>Edit this page using the pull/edit/commit/push version control mechanism.
<h3>Taken from file on ::expoweb::/TODO </h3>
<dl><!--2020-03-29 psargent-->
<dt>Add missing images to logbooks</dt>
<dd>
2000, 2008, 2009, 2011</dd>
<dd>
fix corrupted image in 2001 log</dd>
<dt>2011 logbook:</dt>
<dd>type up via-ferrate & bolt-testing writeups (In paper book, not in scan or HTML)</dd>
<dt>2011 logbook:</dt>
<dd>type up via-ferrate & bolt-testing writeups (In paper book, not in scan or HTML)</dd>
<dt>200? logbook:</dt>
<dd>
Type up "list of GPS locations still to type"</dd>
<dt>200? logbook:</dt>
<dd>
Type up "list of GPS locations still to type"</dd>
<dt>2019 Logbook</dt>
<dd>
transcribe the rest of those blog entries into expoweb/years/2019/logbook.html</dd>
<dd>
copy the photos from the UKCaving blog into expofiles/photos/2019/<MyName>/ -- in fact many of those photos are already there</dd>
<dd>edit in the links to those photos in the right place in 2019/logbook.html</dd>
<dt>2019 Logbook</dt>
<dd>
transcribe the rest of those blog entries into expoweb/years/2019/logbook.html</dd>
<dd>
copy the photos from the UKCaving blog into expofiles/photos/2019/<MyName>/ -- in fact many of those photos are already there</dd>
<dd>edit in the links to those photos in the right place in 2019/logbook.html</dd>
</dl>
<h2>Documentation</h2>
<h3>Documentation</h3>
<dl>
<dt><!--2020-03-29 psargent-->Document this to-do list thing</dt>
<dd><!--2020-03-29 psargent-->explain how clicking works</dd>
<dd><!--2020-03-29 psargent-->explain how clicking works</dd>
<dt><!--2020-03-26 psargent-->Wallets and new-cave</dt>
<dd><!--2020-03-26 psargent-->Explain (in the wallets process) how to view the surveys
online so that <br>&nbsp;&nbsp;(1) you can see an example of how to do your new one,
and <br>&nbsp;&nbsp;(2) so that you can check that you have done it properly when you
have finished.</dd>
<dd><!--2020-03-26 psargent-->Explain how to link a new cave into the other caves in
troggle filesystem</dd>
<dd><!--2020-03-26 psargent-->Explain (in the wallets process) how to view the surveys
online so that <br>&nbsp;&nbsp;(1) you can see an example of how to do your new one,
and <br>&nbsp;&nbsp;(2) so that you can check that you have done it properly when you
have finished.</dd>
<dd><!--2020-03-26 psargent-->Explain how to link a new cave into the other caves in
troggle filesystem</dd>
<dd><!--2020-03-26 psargent-->Explain how to add photos with the correct URL format to sub-HTML files attached to New Caves</dd>
<dt><!--2020-03-26 psargent-->Troggle architecture</dt>
<dd><!--2020-03-26 psargent-->Handbook: explain how troggle works - much better and simpler. Fix
mistakes I wrote. For future system maintainers</dd>
<dd><!--2020-03-26 psargent-->Copy the .wiki material into the documentation somewhere</dd>
<dd><!--2020-03-26 psargent-->Handbook: complete the new troggle architecture documentaiton. For future system maintainers</dd>
<dd><!--2020-03-26 psargent-->Copy the .wiki material into the documentation somewhere</dd>
<dt><!--2020-03-26 psargent-->Surveyscans</dt>
<dd><!--2020-03-26 psargent-->explain where the image files are referenced from: svx, tunnel/therion, and </dd>
<dd>why there are so many broken links</dd>
<dd><!--2020-03-26 psargent-->explain where the image files are referenced from: svx, tunnel/therion, and </dd>
<dd>why there are so many broken links</dd>
<dt>Apache & MySQL configuration
<dd><!--2020-04-03 psargent-->DOCUMENT How to set up a server
<dt>non-troggle scripts
<dd><!--2020-04-03 psargent-->DOCUMENT them all - have we got <a href="../troggle/otherscripts.html">a full list</a>?
</dl>
<h2>Photos</h2>
<h3>Photos</h3>
<dl>
<dt><!--2020-03-26 psargent-->Capitalisation in filenames problem
<dd><!--2020-03-26 psargent-->run the duplicate filename script on the server in
/photos/xml/ as there are files which differ only in
capitalisation of their names.</dd>
<dd><!--2020-03-26 psargent-->Fix such duplicates in the /photos/ folders where this
problem originates</dd>
<dd><!--2020-03-26 psargent-->Document this issue of duplicate photo filenames produced by
multiple cameras running similar software</dd>
<dd><!--2020-03-26 psargent-->somehow fix the photo filenames which use capital letters on
import or upload, or by a cron job</dd>
<dt><!--2020-04-03 psargent-->Fix the BINS package
<dd><!--2020-04-03 psargent-->set up git on the BINS software</dd>
<dd><!--2020-04-03 psargent-->set up a cron job to run BINS</dd>
</dl>
<h2>Surveys data entry</h2>
<dl>
<h3>Surveys data entry</h3>
<dl>
<dt>Write code to extract info about wallets form svx files
<dd><!--2020-04-03 psargent-->use to VALIDATE exitsing contents.json files - produce DISCREPANCY report & fix
<dt><!--2020-03-26 psargent-->2019 surveyscans
<dd><!--2020-03-26 psargent-->edit all the content.json</dd>
<dd><!--2020-03-26 psargent-->try to autocomplete the content.json by parsing .svx files</dd>
<dd><!--2020-03-26 psargent-->Put personal names into canonical form</dd>
<dt>2014 contents.json
<dd><!--2020-04-03 psargent-->parse all the svx files to extract people, dates & svx references
</dl>
<h2>Troggle</h2>
<h2>Expo Server</h2>
<h3>Troggle</h3>
<dl>
<dt>Better import error messages
<dd><!--2020-04-03 psargent-->REPORT if import surveyscan file failure
<dd><!--2020-04-03 psargent-->Why are so many surveyscan foolder missing after import?
<dd><!--2020-04-03 psargent-->WHY are total lengths of surveyed cave different between expo server and WSL server for 2019 and a few other years only ?
</dl>
<h3>Logbooks</h3>
<dl>
<dt>2019 - blog photos
<dd><!--2020-04-03 psargent-->copy & plumb-in the blog photos for the already-copied blog text
<dt>Past logbooks - missing images?
<dd><!--2020-04-03 psargent-->Which previous years HTML logbooks are missing images extracted from scanned PDF copies of the logbooks?
<dt>data model: unfilled fields?
<dd><!--2020-04-03 psargent-->'cave' of location field missing on nearly all logbook entroies. Missing from logbook templates. Where is this used and how can we fill it it in? Is it useful?
<dt>imagemagick convert
<dd><!--2020-04-03 psargent-->Not working for PDFs on current version of xubuntu ! Fix & document. Also not working on WSL ubuntu.
</dl>
<h3>Expo Server</h3>
<dl>
<dt><!--2020-03-26 psargent--> www-data:www-data permissions
<dt><!--2020-03-26 psargent--> document directory structure
<dd><!--2020-03-26 psargent-->Fix permissions so that all files served by troggle have
www-data:www-data ownership and group ownership, otherwise the
"Edit this page" fails with a permissions error, or
</dd>
<dd><!--2020-03-26 psargent-->Or fix group
membership for the process running django so that it can write
files owned by 'expo'
</dd>
</dd>
<dd><!--2020-04-03 psargent-->as per Julian's GitHub list - then close that issue</dd>
<dt>permissions
<dd><!--2020-04-03 psargent-->do we need a cron job or has the group membership fix fixed it ? either way, document it.
</dd>
</dl>
<h2>
<font color="darkviolet">This to-do-list gadget itself</font>
</h2>
<h3>
<font color="fuchsia">This to-do-list gadget itself</font>
</h3>
<dl>
<dt><!--2020-03-26 psargent-->Eventual aim
<dt><!--2020-03-26 psargent-->Eventual aim
<dd><!--2020-03-26 psargent-->to replace GitHub <a href="https://github.com/CaveSurveying/CUCCexposurveyissues/issues">
CUCCexposurveyissues</a> for non-tunnel, non-GIS issues.</dd>
<dd><!--2020-03-26 psargent-->We need two of these: <br>1.for expo systems work (troggle & scripts) - the current priority as we have nowhere currently that Wookey is willing to use
<br>2.for survey data progress/issues (though troggle itself can be used for some of this if cleaned up a bit)
</dd>
<dd><!--2020-03-26 psargent-->to replace GitHub <a href="https://github.com/CaveSurveying/CUCCexposurveyissues/issues">
CUCCexposurveyissues</a> for non-tunnel, non-GIS issues.</dd>
<dd><!--2020-03-26 psargent-->We need two of these: <br>1.for expo systems work (troggle & scripts) - the current priority as we have nowhere currently that Wookey is willing to use
<br>2.for survey data progress/issues (though troggle itself can be used for some of this if cleaned up a bit)
</dd>
<dt><!--2020-03-26 psargent-->Try to automate simple functions in javascript
<dd><!--2020-03-26 psargent-->to control this document
in-place (tick, delete) instead of using the <a
href="https://www.tiny.cloud/docs/general-configuration-guide/use-tinymce-inline/">
tinymce</a> HTML editor in Django</dd>
<dd><!--2020-03-26 psargent-->Maybe restructure whole page as JSON and use
javascript editor to create (edit), re-order and demote items. So long
as the content is inserted into the DOM, it should work ?</dd>
<dd><!--2020-03-26 psargent-->Implement comments on an issue, mimicking GitHub issues wiki</dd>
<dd><!--2020-03-26 psargent-->Use javascript to skip over the _edit page and submit changes
direct to server when updating</dd>
<dd><!--2020-03-26 psargent-->checkboxes so that items can be ticked
(which also does strike-through)</dd>
<dd><!--2020-03-26 psargent-->bin icon to delete an item? Better to have an archive process.</dd><!--2020-03-26-->
<dd><!--2020-03-26 psargent-->to control this document
in-place (tick, delete) instead of using the <a
href="https://www.tiny.cloud/docs/general-configuration-guide/use-tinymce-inline/">
tinymce</a> HTML editor in Django</dd>
<dd><!--2020-03-26 psargent-->Maybe restructure whole page as JSON and use
javascript editor to create (edit), re-order and demote items. </dd>
<dd><!--2020-03-26 psargent-->if using tinymcs, use the INLINE mode. </dd>
<dd><!--2020-03-26 psargent-->Implement comments on an issue, mimicking GitHub issues wiki</dd>
<dd><!--2020-03-26 psargent-->Use javascript to skip over the _edit page and submit changes
direct to server when updating. Needs direct POST and include the javascript in the posted content.</dd>
<dd><!--2020-03-26 psargent-->checkboxes so that items can be ticked (which also does strike-through)</dd>
<dd><!--2020-04-03 psargent-->promotion/demotion options?</dd>
<dd><!--2020-03-26 psargent-->bin icon to delete an item? Better to have an archive process.</dd>
<dt>Local WSL server
<dd><!--2020-04-03 psargent-->Why is it using recuced-capability tinymce, a paths problem ?
<dt>Italics management
<dd><!--2020-04-03 psargent-->Hide ALL DD if any Heading clicked.
<dd><!--2020-04-03 psargent-->Put DL into italics when *any* DD is hidden
</dl>
<h3><font color="fuchsia">Tackle Store Records</font></h3>
<dl>
<dt>No authoritative list of where the expo paper records are!
<dd><!--2020-04-03 psargent-->FIND where all the wallet binders are, and the logbooks.
< <dd><!--2020-04-03 psargent--> Buy A4 plastic boxes for filing cabinet for logbooks getting damp there.
</dl>
<hr>
<!-- ------------------- Do not touch anything below here ------------------------>