mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2026-05-01 12:30:02 +01:00
New index to all troggle pages
This commit is contained in:
@@ -142,7 +142,7 @@ more modern look there as well
|
||||
[The effort estimate is similarly a gross underestimate because (a) he assumes one script per page of output, forgetting all the core work to create a central consistent dataset, and (b) he is missing out most
|
||||
of the functionality we use without realizing it because it is built into
|
||||
django's SQL system, such as multi-user operations.
|
||||
<p><span style="color:red">Eventually we will have to <a href="trogdesignx.html">migrate from django</a> of course</span>, as it will eventually
|
||||
<p><span style="color:red">Eventually we will have to <a href="trogdesign.html">migrate from django</a> of course</span>, as it will eventually
|
||||
fail to keep up with the rest of the world. Right now we need to get ourselves onto python3
|
||||
so that we can use an LTS release which has current security updates. This is
|
||||
<a href="https://docs.djangoproject.com/en/3.0/internals/release-process/#supported-versions-policy">more urgent for django</a> than for Linux. In Ubuntu terms we are on 18.04 LTS (Debian 10) which has no free maintenance updates from 2023. <span style="color:red">We should plan to migrate troggle from django to another framework in about 2025. See stroggle below.</span>]
|
||||
@@ -170,8 +170,11 @@ We need a file uploading system to put things in the right place; and this would
|
||||
|
||||
|
||||
<hr />
|
||||
Go on to: <a href="trogarch.html">Troggle architecture</a><br />
|
||||
Return to: <a href="trogdesign.html">Troggle design and future implementations</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>
|
||||
</html>
|
||||
|
||||
Reference in New Issue
Block a user