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

all text now in dropdown sections - online edit of handbook/website-history.html

Browse Source
This commit is contained in:
Expo on server 2024-11-22 18:10:34 +00:00
parent d3d0ab907e
commit 6e6b95da04
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
handbook/website-history.html
View File

@ -240,7 +240,7 @@ Similarly expoweb is full of bloat from fat images and surveys and one 82MB thes
<details>
<summary id='#may2020'>May-July 2020 and Django</summary>
<p>
Wookey has now moved 'expoweb' from mercurial to git largely "as-is". Mark Shinwell has said that he will help on the loser (survex files) migration to git.
During May Wookey moved 'expoweb' from mercurial to git largely "as-is". Mark Shinwell has said that he will help on the loser (survex files) migration to git.
<p>In May we were on django 1.7 and python 2.7.17. Sam continued to work on upgrading django from v1.7 . We wanted to upgrade django as quickly as possible because old versions of django had unpatched security issues.
[Upgrading to later django versions <a href="troggle/trogdjangup.html">is a real pig</a> - not helped by the fact that all the tools to help do it are now out of date for these very old django releases.]
<ul>
@ -273,8 +273,11 @@ In the course of these migrations several unused or partly-used django plugins w
<h4>July 2020</h4>
<p>Wookey upgraded debian on the server from 9 <var>stretch</var> to 10 <var>buster</var> and we got the python3 development of troggle running as the public version (with some http:// and https:// glitches) by 23rd July. <var>Buster</var> will be in-support definitely until June 2024 so we are rather pleased to be on a "not ancient" version of the operating system at last. This concided with a last tweak at improving the full cave data file import so now it runs on the development system in ~80 seconds. Which is considerably more useful than the ~5 hours it was taking earlier this year.
</details>
<h4>April 2021</h4>
<p>Covid lockdown has been good to troggle. During March and April Philip migrated troggle up to
<details>
<summary id='#2021'>April 2021 - July 2022, Covid</summary>
<p>Covid lockdown has been good to troggle. During March and April 2021 Philip migrated troggle up to
<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>
@ -302,6 +305,7 @@ So now the progress of scanning and tunneling survey data can be managed more ea
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.
</details>
<h3>More recent</h3>
<p>