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

Troggle status update

Browse Source
This commit is contained in:
Philip Sargent 2020-07-24 01:57:09 +01:00
parent 44cb2b2ca6
commit b090264951
1 changed files with 9 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
handbook/troggle/trogstatus.html
View File

@ -47,19 +47,22 @@ Django: <a href="https://www.djangoproject.com/download/#supported-versions">ful
</ul> </ul>
<p>We planned to upgrade from django 1.7 to django 1.11, then port from python2 to python3 on <p>We planned to upgrade from django 1.7 to django 1.11, then port from python2 to python3 on
the same version of django, then upgrade to as recent a version of django as we could. But we have the same version of django, then upgrade to as recent a version of django as we could. But we have
discovered that django1.7 works just fine with <a href="https://docs.djangoproject.com/en/1.10/topics/python3/">python3</a>, so we will probably move to python3 during June and discovered that django1.7 works just fine with <a href="https://docs.djangoproject.com/en/1.10/topics/python3/">python3</a>, so we will move the development version to python3 during June and
then upgrade the server operating system from Debian <var>stretch</var> to <var>buster</var> before then upgrade the server operating system from Debian <var>stretch</var> to <var>buster</var> before
tackling the next step: thinking deeply about when we migrate from django tackling the next step: thinking deeply about when we migrate from django
<a href="trogdesignx.html">to something else</a>. <a href="trogdesignx.html">to something else</a>.
</p> </p>
<p> <p>
Enforced time at home is giving us a new impetus to writing and restructuring the documentation for everything. Enforced time at home is giving us a new impetus to writing and restructuring the documentation for everything.
<h4>end of June 2020</h4> <h4>June 2020</h4>
<p>Sam was a bit overworked in trying to get an entire university to work remotely and Philip got troggle on django 1.7 to work on python 3.5 and then 3.8. He then did the slog of migrating it through the django versions up to 1.11.29 - the last version before django 2.0 when a new URL routing architecture becomes available. 1.11.29 is an LTS (long term support) version of django. In doing this we had to retreat to python3.7 due to a django incompatibility; which is fine because the server will run python3.7 when it is updated to debian 10 (buster) [Wookey to do]. <p>Sam was a bit overworked in trying to get an entire university to work remotely so Philip [Sargent] got troggle on django 1.7 to work on python 3.5 and then 3.8. He then did the slog of migrating it through the django versions up to 1.11.29 - the last version before django 2.0 . 1.11.29 is an LTS (long term support) version of django. In doing this we had to retreat to python3.7 due to a django incompatibility.
<p> <p>
In the course of these migrations several unused or partly-used django plugins were dropped as they caused migration problems (notably staticfiles) and the plug-ins pillow, django-registration, six and sqlparse were brought up to recent versions. This was all done with pip in a python venv (virtual environment) on a Windows 10 machine running ubuntu 20.04 under WSL (Windows Systems for Linux) v1. Also missing troggle functions were repaired and partly-implemented pages, such as the list of all cavers and their surveyed passages, were finished and made to work. The survex file parsing was completely rebuilt to reduce the excessive memory footprint while parsing. In the course of these migrations several unused or partly-used django plugins were dropped as they caused migration problems (notably staticfiles) and the plug-ins pillow, django-registration, six and sqlparse were brought up to recent versions. This was all done with pip in a python venv (virtual environment) on a Windows 10 machine running ubuntu 20.04 under WSL (Windows Systems for Linux) v1.
<p>We plan to stick with debian 10 (buster), django 1.11.29 and python 3.7.7 (the standard on buster) until spring 2021 when we will upgrade debian to the forthcoming stable release 11. At that point debian will have python 3.8 as standard and we will migrate to django 2.x, hopefully getting as far as django 2.2 which is an LTS and actually in support until April 2022. <p>Missing troggle functions were repaired and partly-implemented pages, such as the list of all cavers and their surveyed passages, were finished and made to work. The logbook parsing acquired a cacheing system to re-load pre-parsed files. The survex file parsing was completely rebuilt to reduce the excessive memory footprint. While doing so the parser was extended to cover nearly the full range of survex syntax and modified to parse, but not store, all the survey stations locations. A great many unused classes and some partly written code ideas were deleted.
<p>With any luck that will be the last of our involvement with django migrations as we will keep using django 2.2 until we stop using django altogether, see <a href="trogspeculate.html">troggle architecture speculations</a>. <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 server in ~200 seconds. Which is considerably more useful than the ~5 hours it was taking earlier this year.
<p>We plan to stick with debian 10 <var>buster</var>, django 1.11.29 and python 3.7.5 (the standard on <var>buster</var>) until spring 2021 when we may upgrade debian to the forthcoming stable release 11 <var>bullseye</var>. At that point debian will have python 3.8 as standard and we will migrate to django 2.x, hopefully getting as far as django 2.2 which is an LTS and actually in support until April 2022.
<p>With any luck that will be the last of our involvement with django migrations as we may not move on from using django 2.2 until we stop using django altogether, see <a href="trogspeculate.html">troggle architecture speculations</a>.
<hr /> <hr />
<img border="1" class="onright" width="150px" src='tricky-troggle.jpg' alt='git logo'/></a> <img border="1" class="onright" width="150px" src='tricky-troggle.jpg' alt='git logo'/></a>
Go on to: <br> Go on to: <br>