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

shell setup scripts additions - online edit of handbook/troggle/troglaptop.html

Browse Source
This commit is contained in:
Expo on server 2022-10-27 12:19:16 +01:00
parent 66da64b51f
commit db8bb39196
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
handbook/troggle/troglaptop.html
View File

@ -50,14 +50,21 @@ http://expo.survex.com/repositories/troggle/.git/tree/README.txt
<li><var>os-trog.sh</var> <li><var>os-trog.sh</var>
<li><var>venv-trog.sh</var> <li><var>venv-trog.sh</var>
</ul> </ul>
<p>You will run <var>os-trog.sh</var> just once to install the basics, but you will run <var>venv-trog.sh</var> every time you fire up a new python version/django version combination or play with the versions of the imported packages as listed in <var>requirements.txt</var>.
<p><var>os-trog.sh</var> takes a few minutes initially, but then about an hour when it installs therion and tunnel as these drag in a huge number of dependencies.
<h3>Files and directories</h3> <h3>Files and directories</h3>
<p>Do familiarise yourself with the directory structure on the expo server, which we will be duplicating (partly) as docmented in <a href="serverconfig.html">The Expo Server</a>. We are not here doing a full install of all the software and scripts on the server, just the minimum to run, test and debug troggle on Django. <p>Do familiarise yourself with the directory structure on the expo server, which we will be duplicating (partly) as docmented in <a href="serverconfig.html">The Expo Server</a>. We are not here doing a full install of all the software and scripts on the server, just the minimum to run, test and debug troggle on Django. These will be setup for you by <var>venv-trog.sh</var>.
<h3>WSL on Windows</h3> <h3>WSL on Windows</h3>
<p>If you are using an old laptop, you may have to run Ubuntu in WSL1 rather than WSL2. WSL2 requires virtualisation features that your hardware may not support if it is more than about 5 years old. <p>If you are using an old laptop, you may have to run Ubuntu in WSL1 rather than WSL2. WSL2 requires virtualisation features that your hardware may not support if it is more than about 5 years old.
<p>The standard documentation for Ubuntu or debian below all works, but you should first skim the <p>The standard documentation for Ubuntu or debian below all works, but you should first skim the
<a href="../computing/winlaptop.html">Windows expo laptop</a> configuration too. <em>So far as expo software</em> is concerned, WSL1 and WSL2 behave identically. <p>...Except for file permissions, which can cost you a day of frustration if you are unlucky. See <a href="https://learn.microsoft.com/en-us/windows/wsl/file-permissions">WSL File Permissions</a>. <a href="../computing/winlaptop.html">Windows expo laptop</a> configuration too. <em>So far as expo software</em> is concerned, WSL1 and WSL2 behave identically. <p>...Except for file permissions, which can cost you a day of frustration if you are unlucky.
The trick is to make sure that all the files in your development folders, e.g. <var>C:\expo\</var> which contains your repos e.g. <var>C:\expo\troggle\</var> are owned in the Windows system by the default Windows user e.g. <var>MACHINENAME\philip</var> and owned in the Linux system e.g. <var>/mnt/c/expo/</var> by the default Linux user, e.g. <var>philip:philip</var> using <br><var>sudo chown -Rhv philip:philip *</var>
<br>
and then <em>reboot your machine</em> as this doesn't seem to properly take effect until you do that.
<p>
See also <a href="https://learn.microsoft.com/en-us/windows/wsl/file-permissions">WSL File Permissions</a>.
<h3>Why no Docker container?</h3> <h3>Why no Docker container?</h3>
<p>Yes, it is true that this would greatly speed up on-boarding new programmers. <p>Yes, it is true that this would greatly speed up on-boarding new programmers.