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

making troggle easier to maintain - online edit of handbook/troggle/trogdesign.html

Browse Source
This commit is contained in:
Philip Sargent
2025-10-27 11:54:22 +00:00
committed by Expo on server
parent 2257373b0c
commit f36335dd5b
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
handbook/troggle/trogdesign.html
View File

@@ -17,7 +17,7 @@
<li><h4><a href="#change">New Things Troggle will need to Manage</a></h4> <li><h4><a href="#change">New Things Troggle will need to Manage</a></h4>
<li><h4><a href="#specific">Specific, Immediate problems</a></h4> <li><h4><a href="#specific">Specific, Immediate problems</a></h4>
</ul> </ul>
<p><em>Updated: 22 October 2025</em> <p><em>Updated: 27 October 2025</em>
<h2 id="fail">Things Troggle Doesn't Do</h2> <h2 id="fail">Things Troggle Doesn't Do</h2>
<p>Mostly these are not just a problem just with troggle, but things where expo procedures have never been <p>Mostly these are not just a problem just with troggle, but things where expo procedures have never been
@@ -103,9 +103,13 @@ expeditions. There are 61 different types of reports produced by troggle, some o
internal structure which would need several API URLs. Nobody has attempted to produce any kind of alternative internal structure which would need several API URLs. Nobody has attempted to produce any kind of alternative
special-purpose front-end yet. special-purpose front-end yet.
<h3>Onboarding new People to Help</h3> <h3>Onboarding new people to help</h3>
<p>This is discussed on <a href="https://app.element.io/#/room/!wTGfwrwfiRMsZvzGZW:matrix.org">Element</a> <p>This is discussed on <a href="https://app.element.io/#/room/!wTGfwrwfiRMsZvzGZW:matrix.org">Element</a>
and there are extensive previous discussions on <a href="https://app.slack.com/client/TQF95LK8T/CSCD0HW3S/thread/CQUM4L3HD-1579458900.001800">Slack</a>. and there are extensive previous discussions on <a href="https://app.slack.com/client/TQF95LK8T/CSCD0HW3S/thread/CQUM4L3HD-1579458900.001800">Slack</a>.
<p>In 2025 Wookey and Philip attempted (with slightly different goals) to make Docker-style containers using Podman. The two goals were for starting up a new server, e.g. when migrating to a new machine, and for creating a new troggle development environment for a new programmer.
<h3>Protocols and guidenlines to make future maintenance easier</h3>
<p>The background to this (why we use Django), and what we are doing to make using Django easier, are in the <a href="/handbook/troggle/trogdjango.html">troggle/django</a> page.
<h3>Expofiles archiving</h3> <h3>Expofiles archiving</h3>
The <a href="/expofiles">expofiles</a> folders are 40 GB of folders with no documented archiving or backup procedures. The <a href="/expofiles">expofiles</a> folders are 40 GB of folders with no documented archiving or backup procedures.
@@ -192,6 +196,7 @@ complete copy, but if universal internet access is coming anyway, any such work
</ul> </ul>
<hr /> <hr />
Go on to: <a href="trogarch.html">Troggle architecture</a><br /> Go on to: <a href="trogarch.html">Troggle architecture</a><br />
Go on to:<a href="trogdjango.html"> Django and Troggle</a><br />
Return to: <a href="trogintro.html">Troggle intro</a><br /> Return to: <a href="trogintro.html">Troggle intro</a><br />
Troggle index: Troggle index:
<a href="trogindex.html">Index of all troggle documents</a><br /> <a href="trogindex.html">Index of all troggle documents</a><br />