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

href fixes

Browse Source
This commit is contained in:
Philip Sargent 2020-07-29 18:13:46 +01:00
parent bdbb171762
commit 0a10cef8f7
2 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
handbook/troggle/trogdjango.html
View File

@ -17,7 +17,7 @@
<h4>Major, minor and releases</h4>
<p>Django release 1.11.29 is major-version 1, minor-version 11, and patch-release 29. 1.11 is the "feature release".
<p>Things <em>will break</em> between <a href="https://docs.djangoproject.com/en/3.0/internals/release-process/">django minor-versions</a> which come out every 8 months.
<p>Things <em>will break</em> between <a href="https://docs.djangoproject.com/en/3.0/internals/release-process/">django minor-versions</a> (feature releases) which come out every 8 months.
<h4>Django versions and deprecation</h4>
<a href="https://www.djangoproject.com/download#supported-versions">
@ -34,7 +34,7 @@
<a href="https://pypi.org/project/django-registration/">PyPi: django-registration 3.1</a><br />
<p>but only one of these (PyPi) gives release history data - which is what you need if you get behind with the django upgrades.
<p>Django plugin documentation cannot be relied upton to tell you which version of django they require. They will complain when you run them if your version of django is too old though. Some experimentation is required.
<p>Django plugin documentation cannot be relied upon to tell you which version of django they require. They will complain when you run them if your version of django is too old though. Some experimentation is required.
<p>Every extra plugin increases the "vulnerability surface" of troggle with respect to django upgrade problems so only install a new plugin if it is really, really necessary. For example, when django-staticfiles broke during one upgrade we discovered that we could use flatfiles as a workaround, so we are not planning on reinstalling staticfiles ever again.
@ -115,6 +115,8 @@ pytz==2020.1
Unidecode==1.1.1</code></pre>
<p>To upgrade pip istelf, do <var>$ pip install --upgrade pip</var>
<p>We will not need to update the django-registration until we move from django 2.2.15+ to 3.0.9+ which <a href="trog2030.html">we may never do</a>.
<p>Current upgrade status is documented: <a href="trogstatus.html">here</a>.
<hr />
Go on to: <a href="trogarch.html">Troggle architecture</a><br />
Return to: <a href="trogintro.html">Troggle intro</a><br />

3
handbook/troggle/trogindex.html
View File

@ -26,7 +26,8 @@
<li><a href="trogspeculate.html">Troggle Architecture Speculations</a> - as in April 2020<br>
<li><a href="trog2030.html">Troggle in 2025-2030</a> - architectural evolution proposal<br>
</ul>
<a href="serverconfig.html">Troggle server configuration</a> - how to get troggle running on a new machine<br>
<a href="trogstatus.html">Troggle status</a> - Systems status and upgrade progress<br>
<a href="serverconfig.html">Troggle server configuration</a> - how to get troggle running on a new machine (incoimplete!)<br>
<a href="trogdjango.html">Troggle and django</a> - Upgrading to later django versions<br>
<a href="unittests.html">Troggle unit tests</a> - test suite for programmers<br>
<a href="trogstatus.html">Troggle & expo systems - status update</a> - where we are now<br>