expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2026-02-08 08:10:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

rsync docm updates

Browse Source
This commit is contained in:
Philip Sargent
2021-12-20 23:42:57 +00:00
parent f826f7a946
commit 369e8426a2
4 changed files with 44 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
handbook/troggle/scriptsother.html
View File

@@ -40,7 +40,13 @@
<p>There are also scripts running cron jobs on the server to fix file permissions and to periodically tidy <a href="../computing/repos.html">repositories</a>, and example rsync and scp scripts to help manage synchronisation of the expofiles directories which are not under version control.
<p>Apart from these scripts, troggle in full deployment <a href="serverconfig.html#js">on the server</a> also needs <br>- a running mySQL database, <br>- a running apache webserver and <br>- cgit to display git repos.
<p>Apart from these scripts, troggle in full deployment <a href="serverconfig.html#js">on the server</a> also needs (at least)
<br>- a mySQL database,
<br>- a webserver such as apache
<br>- a text seach utility such as xapian
<br>- cgit to display git repos.
<p> See the <a href="serverconfig.html#js">server configuration</a> for the full list,
or the smaller <a href="troglaptop.html">troggle dev</a> setup for just core software development.
<h3 id="inscripts">Old but maybe useful scripts</a></h3>
<ul>

2
handbook/troggle/trogkill.html
View File

@@ -38,7 +38,7 @@ nearly half of it is directly relevant to us:
<li>Always discover why previous modernisations failed <em>first</em>.
<li>Spend a lot of time <em>problem setting</em> before you start to think about <em>problem solving</em>.
<li>Working through a major modernisation is all about managing <em>scope</em>.
<li>Code is much easier to write than it is to read. Modernisaton means a lot of <em>code reading</em>.
<li>Code is much easier to write than it is to read. Modernisation means a lot of <em>code reading</em>.
<li>Human beings are absolutely terrible at estimating probabilities and risk. We always under-estimate the amount of work in a rewrite and over-estimate the likelihood of success.
<li>Success does not come all at once. What are the <em>progressive success criteria</em> during the reengineering?
<li>Use <em>Diagnosis, Policy, Actions</em> where there is little consensus about what success looks like.