expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-01-18 00:42:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

fixed urls

Browse Source
This commit is contained in:
Philip Sargent 2023-03-30 21:15:32 +01:00 committed by Wookey
parent 5aedb97fc0
commit 07f4d7cc34
1 changed files with 12 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
handbook/troggle/trogdjangup.html
View File

@ -118,7 +118,8 @@ we upgraded debian 10 (buster) to 11 (bullseye).
<var>troggle$ python manage.py check -v 3 --deploy</var><br>
<var>troggle$ python -Wall manage.py check</var><br>
<li>Use our test suite (and if you see errors, run it with <var>-v 3</var>)<br />
<var>troggle$ python manage.py test [-v 3]</var><br>
<var>troggle$ python manage.py test [-v 3] [--parallel auto]</var><br>
The --parallel option runs the tests in parallel on your machine which is much faster.
<li>Read all the release notes for <em>all</em> the intermediate releases. So from 1.1.29 we read <a
href="https://docs.djangoproject.com/en/3.0/releases/">14 sets of notes</a>: for <a
href="https://docs.djangoproject.com/en/3.0/releases/2.0/">2.0</a>, 2.0.1, 2.0.2... up to 2.0.13 .
@ -130,12 +131,14 @@ hidden in there.
</ol>
<h3>Deprecation warnings and python versions</h3>
<p>The individual releases within a minor version don't break anything but do fix bugs. So if you are on 3.1.x there is no point
in getting 3.2.1 to work and you should go straight to the latest available on your machine of the 3.2 feature release, i.e. 3.2.10 on debian 11.
<p>The individual releases within a minor version don't break anything but do fix bugs. So if you are on 4.1.x there is no point
in getting 4.2.1 to work and you should go straight to the latest available on your machine of the 4.2 feature release, e.g. 4.2.5 on debian 13.
<p><var>check --deploy</var> gives django warnings about security issues in your settings as well as django deprecation warnings.<br>
<var>-Wall</var> is a standard python option and gives warnings of deprecated python features used by django and all the current plugins. So it
tells us that django 1.11.29 is using a deprecated python language feature which will be removed from the language in python 3.9 . Python
version compatibilities are documented at the top of each x.0 release note. From Django 4.0 it requires python 3.8.
<var>-Wall</var> is a standard python option and gives warnings of deprecated python features used by django and all
the current plugins. So it tells us that django 1.11.29 is using a deprecated python language feature which will be
removed from the language in python 3.9 . Python version compatibilities are documented at the top of each y.x.0
release note. <a href="https://docs.djangoproject.com/en/4.2/releases/4.2/">From Django 4.2</a> it requires python
3.8, but python 3.11 is recommended.
<h3>The upgrade process</h3>
<h4>Django migrations - prior reading</h4>
@ -152,7 +155,7 @@ version compatibilities are documented at the top of each x.0 release note. From
<h4>Running troggle before and after a Django migration</h4>
<ol>
<li>ensure that you have the exact version of python installed on your machine as is live for troggle on the server, e.g. do <var>$ sudo apt install python3.7.5</var>.
<li>create a venv using the version of python to be used. <br>We have a script to help you do this in <var>:troggle:venv-trog.sh</var>
<li>create a venv using the version of python to be used. <br>We have a script to help you do this in <var>:troggle:venv-trog.sh</var> (but it is fragile and often broken)
<li>do <a href="troglaptop.html">a clean install</a> of django and troggle.
<li>check the versions of plugins using <var>pip list -o</a>
<li>open two terminal windows:
@ -167,7 +170,7 @@ version compatibilities are documented at the top of each x.0 release note. From
<li>testing:
<ul>
<li>run <var>troggle$ python manage.py test</var>
<li>run the full data import <var>troggle$ python databaseReset.py reset R000</var>. It should take about 5 minutes to import everything (11 minutes on a slow core 2 duo laptop).
<li>run the full data import <var>troggle$ python databaseReset.py reset R000</var>. It should take about 5 minutes to import everything (11 minutes on a slow core 2 duo laptop). ("R000" is just a label, use whatever you like.)
<li>start the runserver in the other terminal window and open a web browser to http://localhost:8000 and check important pages which we don't have tests for (yet). These are listed in <a href="troglaptop.html">the troggle laptop installation instuctions</a>.
</ul>
@ -194,7 +197,7 @@ pytz==2021.1
sqlparse==0.4.1
Unidecode==1.2.0</code></pre>
Although the above all work fine, on debian <var>buster</var> we were actually using the standard installs which are older:
Although the above all work fine, on debian <var>buster</var> we were actually using the standard installs on that version of debian which are older:
<pre><code>$ pip freeze
confusable-homoglyphs==3.2.0
Django==2.2.19