mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2024-11-25 08:41:54 +00:00
Making handbook more consistent
This commit is contained in:
Philip Sargent
parent
e84995a52a
commit
974cb39ad0
@ -6,8 +6,9 @@
|
||||
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
|
||||
</head>
|
||||
<body>
|
||||
<style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
|
||||
<h2 id="tophead">CUCC Expedition Handbook - Online systems</h2>
|
||||
<h1>Expo Data Maintenance - Creating a New Year</h1>
|
||||
<h1>New Expo Maintenance - Creating a New Year</h1>
|
||||
|
||||
<h2><a id="manual">Creating a New Year in the Expo online systems</a></h2>
|
||||
|
||||
@ -66,7 +67,6 @@ system as these are <a href="../computing/repos.html">repositories</a>.
|
||||
|
||||
Return to the main <a href="manual.html">online systems manual</a>.
|
||||
|
||||
<hr />
|
||||
</body>
|
||||
<hr /></body>
|
||||
</html>
|
||||
|
||||
|
||||
@ -6,8 +6,9 @@
|
||||
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
|
||||
</head>
|
||||
<body>
|
||||
<style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
|
||||
<h2 id="tophead">CUCC Expedition Handbook - Online systems</h2>
|
||||
<h1>Expo Data Maintenance - Regular tasks</h1>
|
||||
<h1>Expo Files Maintenance - Regular tasks</h1>
|
||||
|
||||
<h2>Regular operations</h2>
|
||||
|
||||
@ -43,7 +44,6 @@ Look at the <a href="svxvalid.html">valid SVX refs</a> page to check that new sv
|
||||
Annual tasks <a href="newyear.html">New expo year jobs</a>.<br />
|
||||
Return to the main <a href="manual.html">online systems manual</a>.
|
||||
|
||||
<hr />
|
||||
</body>
|
||||
<hr /></body>
|
||||
</html>
|
||||
|
||||
|
||||
@ -5,7 +5,8 @@
|
||||
<title>Handbook Troggle JSON</title>
|
||||
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
|
||||
</head>
|
||||
<body><style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
|
||||
<body>
|
||||
<style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
|
||||
<h2 id="tophead">CUCC Expedition Handbook</h2>
|
||||
<h1>Handbook Troggle JSON</h1>
|
||||
|
||||
@ -29,11 +30,13 @@ In the top left-hand corner is a drop-down menu, 'export as json' is shown selec
|
||||
Select one or more of the objects listed and press the 'Go' button next to the drop-down menu. A JSON-formatted file will be produced 'troggle-ouput.json' in the troggle installation directory (where the troggle code .git file is).
|
||||
<p>There is also an 'export as XML' option.
|
||||
<p>The code which adds this capability into the Troggle Administration control panel is in <var>troggle/core/admin.py</var>.
|
||||
|
||||
<h3>See also</h3>
|
||||
<p><a href="exporttgz.html">Compressed data export</a>.
|
||||
<hr />
|
||||
Go on to: <a href="trogarch.html">Troggle architecture</a><br />
|
||||
Return to: <a href="trog2030.html">Troggle in 2025-2030</a><br />
|
||||
Troggle index:
|
||||
<a href="trogindex.html">Index of all troggle documents</a><br />
|
||||
<hr />
|
||||
</body>
|
||||
<hr /></body>
|
||||
</html>
|
||||
|
||||
@ -5,7 +5,8 @@
|
||||
<title>Handbook all.tgz</title>
|
||||
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
|
||||
</head>
|
||||
<body><style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
|
||||
<body>
|
||||
<style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
|
||||
<h2 id="tophead">CUCC Expedition Handbook</h2>
|
||||
<h1>Handbook all.tgz</h1>
|
||||
|
||||
@ -14,7 +15,7 @@ The old <a href="scriptscurrent.html#makefile">Makefile</a> was an integral part
|
||||
cave data management. These days most files are regenerated whenever a data import is done into troggle, not
|
||||
on a daily basis using the cron-scheduled Makefile.
|
||||
|
||||
<p>The all.tgz archive is not updated regularly, but if it is you wil find it in<br>
|
||||
<p>The all.tgz archive is not updated regularly, and there is no code in place to make it. But someone might have done it manually. If they have, you will find it in<br>
|
||||
<a href="/noinfo/all.tgz">noinfo/all.tgz</a>
|
||||
|
||||
|
||||
@ -23,6 +24,5 @@ Go on to: <a href="trogarch.html">Troggle architecture</a><br />
|
||||
Return to: <a href="trog2030.html">Troggle in 2025-2030</a><br />
|
||||
Troggle index:
|
||||
<a href="trogindex.html">Index of all troggle documents</a><br />
|
||||
<hr />
|
||||
</body>
|
||||
<hr /></body>
|
||||
</html>
|
||||
|
||||
@ -5,7 +5,8 @@
|
||||
<title>Handbook Troggle Intro</title>
|
||||
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
|
||||
</head>
|
||||
<body><style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
|
||||
<body>
|
||||
<style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
|
||||
<h2 id="tophead">CUCC Expedition Handbook</h2>
|
||||
<h1>Troggle - Maintenance Manuals</h1>
|
||||
<p>Troggle is the software which runs the the expo cave survey data management and website.
|
||||
@ -17,10 +18,11 @@
|
||||
<ul>
|
||||
<li><a href="../computing/newyear.html">Annual tasks</a>: preparing for next year, finishing last year.
|
||||
<li><a href="../computing/regular.html">Regular tasks</a>: housekeeping as surveys are digitised.
|
||||
<li><a href="trogdocm.html">Maintain troggle</a> itself. The code is public on repository <a href="../computing/repos.html">:troggle:</a>
|
||||
<li><a href="scriptsother.html">Other scripts</a> - photos, folk, wallets - not integral parts of troggle.
|
||||
<li><a href="trogarch.html">Troggle and database</a> architecture: how it all fits together
|
||||
<li><a href="trogdesign.html">Design decisions</a> inc. troggle replacement e.g. new systems for <a href="menudesign.html">website menus</a>
|
||||
<li><a href="trogdocm.html">Maintain troggle</a> itself. The code is public on repository <a href="../computing/repos.html">:troggle:</a>
|
||||
|
||||
<li><a href="trogdjango.html">Troggle and django</a> - Upgrading to later django versions
|
||||
|
||||
<li><a href="trognotes.html">Uncategorised notes</a> and past speculations
|
||||
@ -47,6 +49,5 @@ Go on to: <a href="trogarch.html">Troggle architecture</a><br />
|
||||
Return to: <a href="trogintro.html">Troggle intro</a><br />
|
||||
Troggle index:
|
||||
<a href="trogindex.html">Index of all troggle documents</a><br />
|
||||
<hr />
|
||||
</body>
|
||||
<hr /></body>
|
||||
</html>
|
||||
|
||||
@ -5,7 +5,8 @@
|
||||
<title>Handbook Troggle Status</title>
|
||||
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
|
||||
</head>
|
||||
<body><style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
|
||||
<body>
|
||||
<style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
|
||||
<h2 id="tophead">CUCC Expedition Handbook</h2>
|
||||
<h1>Troggle & Expo Systems - status update</h1>
|
||||
<p>Troggle is the software which runs the the expo cave survey data management and website.
|
||||
@ -24,7 +25,7 @@ In the course of these migrations several unused or partly-used django plugins w
|
||||
|
||||
|
||||
<h4>April 2021</h4>
|
||||
<p>Lockdown has been good to troggle. During March and April Philip migrated troggle up to Django 2.2.19, excising the ancient and unused user registration system on the way. Django 2.2 LTS is a long-term stable relase which will be in-support by Django until April next year. Wookie discovered and ran the Django system testsuite on the Debian server thus enabling us to use a necessary (but obstensibly outdated) link between Django and the database MariaDB. As of April 9th troggle is now running on software which is actually 'in date'.</p>
|
||||
<p>Lockdown has been good to troggle. During March and April Philip migrated troggle up to Django 2.2.19, excising the ancient and unused user registration system on the way. Django 2.2 LTS is a long-term stable relase which will be in-support by Django until April next year. Wookey discovered and ran the Django system testsuite on the Debian server thus enabling us to use a necessary (but obstensibly outdated) link between Django and the database MariaDB. As of April 9th troggle is now running on software which is actually 'in date'.</p>
|
||||
<p>We plan to stick with this configuration for a year.</p>
|
||||
<p>Next April (2022) we may upgrade to the forthcoming debian stable release 11 <var>bullseye</var>. At that point debian will have python 3.8 as standard. We also hope to migrate to django 3.2 LTS which will be a year old by then and which will be <a href="https://www.djangoproject.com/download/#supported-versions">supported until April 2025</a>.
|
||||
<p>With any luck that will be the last of our involvement with django migrations as we may not move on from using django 3.2 until we stop using django altogether, see <a href="trogspeculate.html">troggle architecture speculations</a>.
|
||||
@ -39,6 +40,5 @@ Troggle index:
|
||||
|
||||
<br />
|
||||
|
||||
<hr />
|
||||
</body>
|
||||
<hr /></body>
|
||||
</html>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user