mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2024-11-30 05:41:56 +00:00
2022 stuff moved here - online edit of handbook/website-history.html
This commit is contained in:
parent
3fd6376507
commit
b226415c74
@ -277,6 +277,31 @@ In the course of these migrations several unused or partly-used django plugins w
|
|||||||
<a href="../troggle/trogdjangup.html">Django 2.2.19</a>, 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>
|
<a href="../troggle/trogdjangup.html">Django 2.2.19</a>, 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>We plan to stick with this configuration for a year.</p>
|
||||||
|
|
||||||
|
<h4>March 2022</h4>
|
||||||
|
|
||||||
|
<p>On 15th March Wookey upgraded the server to the debian release 11 <var>bullseye</var>.
|
||||||
|
At this point 'debian stable' is bullseye and has python 3.9 as
|
||||||
|
standard. We will quickly migrate to Django 3.2 LTS which is now a year old and which will be <a
|
||||||
|
href="https://www.djangoproject.com/download/#supported-versions">supported until April 2024</a>.
|
||||||
|
<var>Bullseye</var> will be <a href="https://wiki.debian.org/LTS">in support until June 2026</a>.
|
||||||
|
|
||||||
|
<p>Django migrations are not nearly as painful as they used to be, and troggle is already compatible with Django 4.0.3 (though we won't use that).
|
||||||
|
So the presure to migrate from Django is now very greatly lessened. However, see <a href="trogspeculate.html">troggle architecture speculations</a>
|
||||||
|
and possible <a href="trog2030.html">migration from Django</a>.
|
||||||
|
|
||||||
|
|
||||||
|
<p>We should not need to anything until we move from Django 3.2 LTS to 4.2 LTS before April 2024.
|
||||||
|
|
||||||
|
<h4>July 2022</h4>
|
||||||
|
<p>Wookey at last, after much effort, got the loser repository converted from mercurial to git, with much tidying and
|
||||||
|
history-reconfabulation. He says this will need to be done again, but it was good enough for the 2022 Expo. Also the troggle code was
|
||||||
|
changed: survex files edited on a webpage now automatically commit to git with no user involvement.
|
||||||
|
<p>Just before expo, we finished integrating the formerly-separate 'wallets' script.
|
||||||
|
So now the progress of scanning and tunneling survey data can be managed more easily. This
|
||||||
|
has turned out to be unexpectedly powerful. And it works on the data back to 1999 too.
|
||||||
|
<p>Wookey's replacment WiFi antenna (previously we had used Sam's) turned out to be useless, so internet access was not
|
||||||
|
available in the hut this year. This was a real pain.
|
||||||
|
|
||||||
<h3>More recent</h3>
|
<h3>More recent</h3>
|
||||||
<p>
|
<p>
|
||||||
For the current situation see <a href="troggle/trogstatus.html">expo systems status</a>.
|
For the current situation see <a href="troggle/trogstatus.html">expo systems status</a>.
|
||||||
@ -285,6 +310,5 @@ For the current situation see <a href="troggle/trogstatus.html">expo systems sta
|
|||||||
Return to<br />
|
Return to<br />
|
||||||
<a href="computing/onlinesystems.html">expo online systems overbiew</a><br />
|
<a href="computing/onlinesystems.html">expo online systems overbiew</a><br />
|
||||||
|
|
||||||
<hr />
|
<hr /></body>
|
||||||
</body>
|
|
||||||
</html>
|
</html>
|
||||||
|
Loading…
Reference in New Issue
Block a user