2021-10-27 19:25:37 +01:00
<!DOCTYPE html>
2021-10-22 14:18:09 +01:00
< html >
< head >
< meta http-equiv = "Content-Type" content = "text/html; charset=utf-8" / >
< title > Handbook Troggle Laptop< / title >
< link rel = "stylesheet" type = "text/css" href = "../../css/main2.css" / >
< / head >
< body > < style > body { background : #fff url ( /images/style/bg-system.png ) repeat-x 0 0 } < / style >
< h2 id = "tophead" > CUCC Expedition Handbook< / h2 >
< h1 > Troggle - software development laptop< / h1 >
< img src = "https://www.python.org/favicon.ico" width = 64 hspace = "20" align = "right" alt = 'python logo' >
2021-10-27 19:25:37 +01:00
2021-10-22 14:18:09 +01:00
< h2 > Software development machine< / h2 >
< p > For troggle itself, you need a linux machine. We all use Debian or Debian-derived machines (Debian itself, Ubuntu, Xubuntu etc.) but other forms of linux may work. Running Debian or Ubuntu under WSL on Windows 10 works fine.
2021-10-22 19:04:23 +01:00
< p > If you want to work on the troggle source code and be able to commit to the server git repo,
your account will need to be added to the troggle project members list. Contact wookey at wookware dot org to get this set up.
2021-10-22 14:18:09 +01:00
2021-10-27 19:25:37 +01:00
< h3 > Prerequisites< / h3 >
< p > You need to already know really quite a lot about what troggle does, and how it is used in practice. Also you will have installed quite a lot of the software such as tunnel, therion, survex etc. as documented in < a href = "../computing/yourlaptop.html" > your laptop configuration< / a > . In particular read the information there about VS code and git.
2021-10-22 14:18:09 +01:00
< p > This page is a work in progess. Text will be moved here from
2021-10-22 19:04:23 +01:00
2021-10-22 14:18:09 +01:00
< pre >
http://expo.survex.com/repositories/troggle/.git/tree/README.txt
< / pre >
2021-10-22 21:43:02 +01:00
< img src = "https://www.debian.org/logos/openlogo-100.jpg" align = "right" hspace = "20" alt = 'debian logo' >
2021-10-22 14:18:09 +01:00
2021-10-22 19:04:23 +01:00
< h2 id = "os" > Installing linux< / h2 >
2021-12-01 21:12:07 +00:00
< p > If you don't already know how to do this, then you should probably not be attempting to work on the troggle code. But in case you are an experienced linux user who has always had someone else set up the system for them, then Ubuntu is the easiest and more forgiving to install, either directly on the computer or inside WSL. Because we are using fairly old, stable releases of Django, you will want Ubuntu-20.04
2021-10-22 19:04:23 +01:00
< ul >
< li > Install in < a href = "https://docs.microsoft.com/en-us/windows/wsl/install" > WSL on Windows 10< / a > .
< li > Install < a href = "https://ubuntu.com/download/desktop" > Ubuntu 20.04 LTS< / a > .
< / ul >
2021-10-24 14:31:22 +01:00
< p > and 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.
2021-10-22 19:04:23 +01:00
< h3 > WSL on Windows< / h3 >
< p > The standard documentation for Ubuntu or debian below all works, but you should first skim the
2021-12-06 01:01:21 +00:00
< a href = "../computing/winlaptop.html" > Windows expo laptop< / a > configuration too. So far as expo software is concerned, WSL1 and WSL2 behave identically.
2021-10-22 19:04:23 +01:00
2021-12-30 22:21:41 +00:00
< h3 > Why no Docker container?< / h3 >
< p > Yes, it is true that this would greatly speed up on-boarding new programmers.
2022-03-16 12:46:33 +00:00
< p > But there is the significant danger that containers would get copied around and deployed without being properly cleaned up:
resulting in configuration drift and a < a href = "https://martinfowler.com/bliki/SnowflakeServer.html" > snowflake server situation< / a > .
File permissions are a big issue.
< p > We should do both: create a Docker system for getting started, then transition programmers to script-based or recipe-based
provisioning so that systems are rebuilt cleanly. < a href = "http://www.cuyc.org.uk" > CUYC< / a > (who also use Django) have a bash script which sets up a new django
development system. We should copy that in the first instance. Alas, we haven't got around to doing any of this yet.
2021-12-30 22:21:41 +00:00
2021-12-01 21:12:07 +00:00
2021-10-22 19:04:23 +01:00
< h2 id = "python" > Installing python< / h2 >
2021-12-01 21:12:07 +00:00
< a href = "https://xkcd.com/1987/" > < img src = "https://imgs.xkcd.com/comics/python_environment.png" align = "right" hspace = "20" width = "230" alt = 'XKCD python install' > < / a >
2022-03-16 12:46:33 +00:00
< p > Python is not installed by default usually, and in any case we need specific versions to be installed. For Ubuntu 20.04 the
default is python3.9
< p > If you are planning on eventually helping the migration of troggle from debian Bullseye (v11) to
< a href = "https://www.debian.org/releases/" > Bookworm (v12)< / a > to then you will also want the appropriate later versions of python e.g. 3.10 below:
2021-10-22 19:04:23 +01:00
< pre > < code > sudo apt install python3 python3-pip
2021-12-01 21:12:07 +00:00
sudo apt install sqlite3 sqlite3-doc
sudo apt install survex
2021-10-22 21:43:02 +01:00
sudo apt install software-properties-common
sudo add-apt-repository ppa:deadsnakes/ppa
2022-03-16 12:46:33 +00:00
sudo apt install python3.10 python3.10-venv python3.10-doc binutils binfmt-support
2021-10-22 19:04:23 +01:00
cd /usr/bin
sudo ln -s python3 python
sudo ln -s pip3 pip < / code > < / pre >
< p > You will also definitely need sqlite3 even if you are planning to use another
database. Sqlite3 is used by the test harness system.
< p > Note that when you install survex it installs a shed load of packages that it needs.
2021-10-24 14:31:22 +01:00
< p > We do < em > not< / em > install Django at this point. We will be installing Django in a separate virtual
2021-10-22 19:04:23 +01:00
environment (a 'venv'), not in the main linux system.
< h2 id = "links" > Creating folders and soft links< / h2 >
< p > We need to have the folder structure that troggle expects. On your own machine
you will have your own logon id, and you do not need to create an 'expo' user, but
you do need to create folders where and an 'expo' user would have them. Make links there
to wherever you have actually installed the repos. So if you have installed all your repos
in < var > /mnt/c/EXPO/< / var > , then you would need to do this:
< pre > < code > cd ~
cd ..
sudo mkdir expo
cd expo
sudo ln -s /mnt/c/EXPO/expoweb expoweb
sudo ln -s /mnt/c/EXPO/troggle troggle
sudo ln -s /mnt/c/EXPO/loser loser
sudo ln -s /mnt/c/EXPO/drawings drawings
2021-10-23 22:40:12 +01:00
sudo ln -s /mnt/c/EXPO/expofiles expofiles
2021-10-22 19:04:23 +01:00
sudo ln -s /mnt/c/EXPO/expowebcache expowebcache
sudo mkdir expowebcache/3d
cd ..
ls -tlA expo< / pre > < / code >
2022-03-16 12:46:33 +00:00
< h4 id = "EXPOFILESREMOTE" > Remote EXPOFILES< / h4 >
< p > If you do not have a local copy of the 40GB /expofiles/, don't worry. Later on we can set < var > 'EXPOFILESREMOTE = True'< / var > in the
< var > localsettings.py< / var > file and your test system will use the live expofiles on < var > expo.survex.com< / var > (read only).
< p > If you do have < var > 'EXPOFILESREMOTE = True'< / var > then the forms which upload scans and photos to the server will not work as you expect.
They will upload to your local machine, but read the status of the folders from < var > expo.survex.com< / var > . So you will get
confusing and apparently inconsistent behaviour: e.g. you will upload a file but then be unable to see it.
< p > For development, you mostly only need a local copy of the wallets and scanned survey notes and sketches in
< var > expofiles/surveyscans< / var > which is less than 5GB.
2021-10-22 19:04:23 +01:00
< h2 > Installing Django and troggle< / h2 >
2021-10-22 21:43:02 +01:00
< img src = "Django_Logo-420x180.png" align = "right" hspace = "20" width = '210' alt = 'django logo' >
2021-10-22 19:04:23 +01:00
< p > The important point to note
here is that unless you are doing something fairly trivial, or you are a git genius,
2021-10-24 14:31:22 +01:00
it is sensible to set up a python virtual environments to hold duplicate copies of both troggle and Django code.
2021-10-22 21:43:02 +01:00
Then you will be able to check very quickly that your edited version of troggle runs with old, current
2021-10-24 14:31:22 +01:00
and pre-release versions of python and of Django;
and you will more easily be able to manage problems with incompatible versions of Django plugins as installing and upgrading the dependent packages is very fast.
2021-10-22 19:04:23 +01:00
< h3 id = "venv" > Installing a venv< / h3 >
2022-03-16 12:46:33 +00:00
< p > We set up a < var > venv< / var > specifically for python 3.9 (which is the standard version on our server which is running unmodified
Bullseye (debian v11) and < a href = "https://docs.djangoproject.com/en/3.2/releases/3.2/" > Django 3.2.12< / a > . See the < a
href="https://docs.python.org/3.9/library/venv.html">standard python documentation on venv< / a > for python 3.9.10.
Create a new venv for each version of python you are using. Get that venv installed right by explicitly stating the
python version to create it < var > python3.9 -m venv py39d32< / var > . Note that we are creating it as a sibling folder to /expoweb/ .
Note also that up to now we have been using 'sudo ..' but for installing things inside the venv we do not use 'sudo ..':
2021-10-22 19:04:23 +01:00
< pre > < code > cd ~
cd ../expo
2022-03-16 12:46:33 +00:00
python3.9 -m venv py39d32
cd py39d32
2021-10-22 19:04:23 +01:00
source bin/activate
pip list -o< / pre > < / code >
< p > The last command lists the default packages installed in the venv. This is for comparison later, after we
2021-10-24 14:31:22 +01:00
have installed troggle, Django and dependencies. You will get a warning that you have an out of date version of pipbut this is as we want: we are using a version of pip appropriate for the older version of python within
2021-10-22 19:04:23 +01:00
the venv.
2021-10-22 21:43:02 +01:00
< img border = "1" class = "onright" width = "150px" src = 'tricky-troggle.jpg' hspace = "20" alt = 'troggle logo' / > < / a >
2021-10-22 19:04:23 +01:00
2021-10-23 22:40:12 +01:00
< h3 id = "venv" > Installing the troggle dependencies< / h3 >
2021-10-24 14:31:22 +01:00
< p > The first time you do this on a new machine you can't complete the pip installation of Django as you have not yet got the
2021-10-23 22:40:12 +01:00
dependencies appropriate for troggle - because you have not yet cloned the troggle repo. So the first time it is easiest to just create requirements.txt yourself with a text editor. Without using git yourself, you can get the file from the website at < a href = "http://expo.survex.com/repositories/troggle/.git/tree/requirements.txt" > requirements.txt< / a > . If you have already cloned all the repos, then just copy it.
< pre > < code > cp ../troggle/requirements.txt .< / pre > < / code >
2021-10-22 19:04:23 +01:00
where < var > requirements.txt< / var > (note the capitalisation of the listed packages) is:
2022-03-16 12:46:33 +00:00
< pre > < code > asgiref==3.3.4
confusable-homoglyphs==3.2.0
coverage==5.5
Django==3.2
2021-10-22 19:04:23 +01:00
docutils==0.14
gunicorn==20.1.0
pytz==2019.1
sqlparse==0.2.4
2022-03-16 12:46:33 +00:00
typing-extensions==3.7.4.3
2021-10-22 19:04:23 +01:00
Unidecode==1.0.23< / pre > < / code >
2022-03-16 12:46:33 +00:00
This will pick up the latest Django 3.2.x available, but all the other dependencies are pinned. These
2021-10-22 19:04:23 +01:00
dependencies are as-standard on debian Buster (10) and you will want to experiment with upgrading them
for Bullseye (v11).
2021-10-23 22:40:12 +01:00
< p > Once you have the file, install the listed dependencies like this:
< pre > < code > pip install -r requirements.txt
pip list -o< / pre > < / code >
2021-10-22 19:04:23 +01:00
2022-03-16 12:46:33 +00:00
< p > Pillow (not currently in that package list) is an image handling package used to make
2021-10-22 19:04:23 +01:00
the prospecting map (currently disabled,
see < a href = "http://expo.survex.com/prospecting_guide/" > /prospecting_guide/< / a > ).< br >
tinymce is the wysiwyg in-browser
editor (disabled pending reinstatement)
2021-10-24 14:31:22 +01:00
< p > This is also documented in the < a href = "trogdjangup.html" > updating Django for troggle page< / a >
where it describes upgrading and testing with later versions of Django.
2021-10-22 19:04:23 +01:00
< p > If you have not used pip before, read < a href = "https://linuxize.com/post/how-to-install-pip-on-ubuntu-20.04/" > this< / a >
< h3 id = "troginstall" > Installing troggle< / h3 >
2022-03-16 12:46:33 +00:00
< p > The < var > :troggle:< / var > repo is the python source code for troggle. This is what you will be editing. There are over 9,000 lines
of python code (excluding comments and blank lines) and nearly 3,000 lines of HTML/Django template code. This is over 600 files in
over 400 folders, but only 49MB in size (plus a .git repo of 32MB).
2021-10-23 22:40:12 +01:00
< h4 > key exchange< / h4 >
2022-03-16 12:46:33 +00:00
< p > Follow this link to < a href = "../computing/keyexchange.html" > register a key with the expo server< / a > to get git access if you have
not already cloned the < var > :troggle:< / var > repo.
2021-10-22 19:04:23 +01:00
2021-10-23 22:40:12 +01:00
< h4 > git clone troggle< / h4 >
2022-03-16 12:46:33 +00:00
< p > You will do a git clone to create a folder /troggle/ containing all the troggle code. You need to clone the 'python-3' branch, if
you an see multiple branches.< / p >
2021-10-22 19:04:23 +01:00
2021-10-23 22:40:12 +01:00
< pre > < code > cd ~
cd ../expo
git clone ssh://expo@expo.survex.com/home/expo/troggle< / code > < / pre >
< p > Now we create soft links within the venv to all the repo folders and wherever you have a local copy of /expofiles/ and /expowebcache/:
2022-03-16 12:46:33 +00:00
< pre > < code > cd py39d32
2021-10-23 22:40:12 +01:00
sudo ln -s /mnt/c/EXPO/expoweb expoweb
sudo ln -s /mnt/c/EXPO/troggle troggle
sudo ln -s /mnt/c/EXPO/loser loser
sudo ln -s /mnt/c/EXPO/drawings drawings
sudo ln -s /mnt/c/EXPO/expofiles expofiles
sudo ln -s /mnt/c/EXPO/expowebcache expowebcache< / code > < / pre >
< p > If you have not been using git on this machine until now, you will need to identify yourself before you go any further.
< pre > < code > git config --global user.email "you@example.com"
git config --global user.name "Your Name"< / code > < / pre >
2021-10-29 20:16:55 +01:00
< h4 > do the basic Django health checks< / h4 >
2021-10-23 22:40:12 +01:00
< p > This all checks that the installation has completed properly.
2021-10-29 20:16:55 +01:00
< pre > < code > django-admin< / code > < / pre >
2021-10-27 19:25:37 +01:00
< p > The first line < var > django-admin< / var > will complain that it has not got a SETTINGS file, but that's fine.
See < a href = "djangostart.html" > django-admin initial output< / a > for what you should expect to see at this point.
2021-10-29 20:16:55 +01:00
If it crashes though, you have not managed to install the software completely.
If you get an error when running
< pre > < code > django-admin< / code > < / pre >
Then run django-admin like this (using the python version you have installed in the folder underneath /lib/):
< pre > < code > python /usr/local/lib/python3.8/dist-packages/django/bin/django-admin.py< / code > < / pre >
which should fix the paths, but this means that you installed Django directly on your machine and not in a venv. From now on you should be able to run < var > django-admin < / var >
from within any folder on your machine.
< p > Now try
< pre > < code > django-admin --version< / code > < / pre >
The version number is the version of Django you have installed. Double check that it is the one you meant to install and check with < a href = "trogdjangup.html" > our Django versions page< / a > .
< h4 > do the basic troggle health checks< / h4 >
< p > Now try
2021-10-29 20:35:52 +01:00
< pre > < code > python manage.py< / code > < / code > < / pre >
2021-10-29 20:16:55 +01:00
You will get an error: No module named 'localsettings'. Fixing this is described below, but for now try:
< pre > < code > python manage.py check -v 3 --traceback< / code > < / pre > < p > The most important is the < var > python manage.py check< / var > . If this works, then you have installed the software correctly.
< p >
The next task is to edit the SETTINGS files to match your machine and folder structure. So find the appropriate copy of the localsettings in /_deploy/ and copy it into the main troggle folder:
2021-10-23 22:40:12 +01:00
< pre > < code > cp _deploy/wsl/localsettingsWSL.py localsettings.py< / code > < / pre >
2021-10-29 20:35:52 +01:00
The git repo copies have got munged passwords.
localsettings.py is not stored in git, but the copy on the server does have the correct passwords.
So use sFTP to download localsettings.py from expo.survex.com to get these.
< p >
We have at one time made localsettings in /_deploy/ appropriate for
< ul >
< li > debian (server install, not development)
< li > Ubuntu
< li > Ubuntu under WSL (Windows System for Linux)
< li > docker container
< li > potatohut (local network only)
< / ul >
< p >
2021-12-06 01:01:21 +00:00
WARNING: only the WSL and debian variants are current in December 2021. All the others are so old that
2021-10-29 20:35:52 +01:00
they will need serious work to be useable. Copy what you need from WSL and debian variants of
localsettings.py
< p > Now edit localsettings.py and insert useful values for EXPOUSERPASS [e.g. cavey:beery], EXPOADMINUSERPASS [e.g. beery:cavey], SECRET_KEY. SECRET_KEY can be anything, it just has to be unique to each installation and invisible to anyone not a developer.
2022-03-16 12:46:33 +00:00
< p > Set < a href = "https://docs.djangoproject.com/en/4.0/topics/email/#s-configuring-email-for-development" > EMAIL_HOST and EMAIL_HOST_PASSWORD< / a > to an email account you control that can send email. Then troggle can email you when some things go wrong. This may mean having to set EMAIL_PORT and MAIL_USE_TLS too (this is not used in troggle currently). Set EXPOUSER_EMAIL and EXPOADMINUSER_EMAIL to your own email address while you are doing software development. All these will be different when troggle is deployed on the public server.
2021-10-23 22:40:12 +01:00
2021-10-29 20:35:52 +01:00
< p >
Now you need to edit the following settings in your localsettings.py file to match your
development machine, e.g. if you have /expofiles/ mounted on another disc:
< pre > < code > FILES = Path('/mnt/f/expofiles/')
EXPOFILES = Path('/mnt/f/expofiles/')< / code > < / pre >
< p >
All the other settings (drawings, expoweb etc.) will work fine if they are parallel directories
to the directory you installed troggle into. The troggle code can find out itself where it
is living.
< p >
If you do not have a local copy of /expofiles/ (40 GB), you can use the expo server copy if
you set:
< pre > < code > EXPOFILESREMOTE = TRUE< / code > < / pre >
2022-03-16 12:46:33 +00:00
and then the FILES and EXPOFILES setings will be ignored. (Except for the upload forms which will 'upload' files
< a href = "#EXPOFILESREMOTE" > to your local disc< / a > . )
2021-10-29 20:35:52 +01:00
2021-10-29 20:16:55 +01:00
< p >
Now try this again:
< pre > < code > python manage.py< / code > < / pre >
2021-10-29 20:35:52 +01:00
and in addition to the [django] command list, you will now gets command lists for [auth],
2021-10-29 20:16:55 +01:00
[contenttypes], [core], and [sessions]. These are the modules (plugins) loaaded into django.
[core] is the core of troggle (but not all of it: the input file parsers are not in [core]).
2021-10-31 08:05:26 +00:00
< p > Now:
< pre > < code > python -Wall manage.py check < / code > < / pre >
This loads the settings files and checks that all the Django packages and python libraries
imports all work. It gives warnings of deprecated Django which should be fixed.
You should not get any warnings on a fresh install on a new machine but you will
see warning and error messages when you are
trying to upgrade troggle to use later versions of Django.
2021-10-29 20:16:55 +01:00
< pre > < code > python manage.py check -v 3 --traceback< / code > < / pre >
Ideally this will list settings imports and then say< br >
< var > System check identified no issues (0 silenced)< / var > .
< p >
If you get an error your python sys.path is probably not set correctly yet. Do
< pre > < code > python -m site< / code > < / pre >
when you are in your troggle directory to see the list of paths python looks
for when it is searching for packages (both django and troggle). < br >
Ensure that the path to the troggle/ directory is in the list.
It should be at the top, which is where the current working directory is.
< p >
Now:
2021-10-31 08:05:26 +00:00
2021-10-29 20:16:55 +01:00
< pre > < code > python manage.py check -v 3 --deploy< / code > < / pre >
2021-10-31 08:05:26 +00:00
which will give security warnings for deployment. You will get various middleware settings
because we have not got https:// properly configured everywhere (we have unresolved issues with
the Django admin control panel and https:// in October 2021) and
2021-10-29 20:16:55 +01:00
a warning not to use DEBUG=true in deployment. We always have DEBUG=True set for troggle
2021-10-31 08:05:26 +00:00
as otherwise the users get useless error messages. This is completely contrary to Django
official security advice.
< details >
< summary > < em > Click triangle to see security warnings in detail< / em > < / summary >
< font color = "brown" > < pre >
?: (security.W001) You do not have 'django.middleware.security.SecurityMiddleware'
in your MIDDLEWARE so the SECURE_HSTS_SECONDS, SECURE_CONTENT_TYPE_NOSNIFF,
SECURE_BROWSER_XSS_FILTER, and SECURE_SSL_REDIRECT settings will have no effect.
?: (security.W012) SESSION_COOKIE_SECURE is not set to True. Using a secure-only
session cookie makes it more difficult for network traffic sniffers to hijack user sessions.
?: (security.W016) You have 'django.middleware.csrf.CsrfViewMiddleware' in your
MIDDLEWARE, but you have not set CSRF_COOKIE_SECURE to True. Using a secure-only
CSRF cookie makes it more difficult for network traffic sniffers to steal the CSRF token.
?: (security.W018) You should not have DEBUG set to True in deployment. < / pre > < / font >
< / details >
2021-10-29 20:16:55 +01:00
2021-10-31 08:05:26 +00:00
< p >
2021-10-29 20:16:55 +01:00
If you got an error traceback with
< pre > < code > python manage.py< / code > < / pre >
then the settings registration of troggle with django is incomplete.
Delete all your cached .pyc files and try again.
You probably have a mistake in your settings.py or localsettings.py files.
< pre > < code > python manage.py diffsettings< / code > < / pre >
This last one shows everything set in global settings, settings and localsettings.
Anything different from global settings (django built-in) has '###' appended.
< pre > < code > python manage.py help migrate
python manage.py migrate< / code > < / pre >
Tests the uptodateness of your sqlite database. The help option
explains what this does and gives extra command line options.
2021-10-23 22:40:12 +01:00
< h4 > check full functionality< / h4 >
2021-10-29 20:16:55 +01:00
< p > Now run the test suite:
< pre > < code > python manage.py test -v 3 --traceback< / code > < / pre >
2022-03-16 12:46:33 +00:00
< p > This will run the entire troggle test suite of ~80 tests (it takes only a few seconds).
2021-10-29 20:16:55 +01:00
2021-10-31 20:48:05 +00:00
< p >
If you get an error, and you probably will, have a look in the source code of the test, e.g. for this error:
< pre > < code > FAIL: test_page_folk (troggle.core.TESTS.tests.PageTests) < / code > < / pre >
look in the file
< var > troggle/code/TESTS/tests.py< / var > in the class < var > PageTests< / var > .
2021-10-29 20:16:55 +01:00
It will also say:
2021-10-31 20:48:05 +00:00
< pre > < code > File "/mnt/c/EXPO/troggle/core/TESTS/tests.py", line 266, in test_page_folk< / code > < / pre >
which means that the asssert failure in on line 266 of < var > troggle/code/TESTS/tests.py< / var >
and that the failure function is test_page_folk() .
2021-10-29 20:16:55 +01:00
If you look at this you will see that line 264 is:
2021-10-31 20:48:05 +00:00
< pre > < code > response = self.client.get('/folk/index.htm')< / code > < / pre >
2021-10-29 20:16:55 +01:00
so this file is missing. Duh. Of course it is. We downloaded troggle from git but we didn't run
2021-10-31 20:48:05 +00:00
the standalone script to generate the folk list.
The quickest thing to do when installing troggle is to simply download a copy from the server:
< pre > < code > wget -O ../expoweb/folk/index.htm expo.survex.com/folk/index.htm< / code > < / pre >
and run the tests again:
2021-10-29 20:16:55 +01:00
2021-10-31 20:48:05 +00:00
< pre > < code > python manage.py test -v 2< / code > < / pre >
2021-12-01 21:12:07 +00:00
< details > < summary > Click on the triangle to see how to run the < var > folk< / var > script. You don't need to do this now.< / summary >
2021-10-31 20:48:05 +00:00
< font color = "blue" >
The < var > folk< / var > generation script is top of the list in
< var >
http://expo.survex.com/handbook/troggle/scriptscurrent.html#folk< / var >
< p >
2021-10-29 20:16:55 +01:00
So do this:
2021-10-31 20:48:05 +00:00
< pre >
2021-10-29 20:16:55 +01:00
cd ../expoweb/folk
python ../scripts/make-folklist.py < folk.csv > index.htm
cd ../../troggle
2021-10-31 20:48:05 +00:00
< / pre >
< / font >
< / details >
2021-10-29 20:16:55 +01:00
2022-03-16 12:46:33 +00:00
< p > The test suite now tidies up after itself, so there should not be any temporary files left behind or local git commits that you
will need to clean up.
2021-10-29 20:35:52 +01:00
2022-03-16 12:46:33 +00:00
< p > The test suite has ~80 tests but does not cover all of what troggle does and does not use any real data. You need to manually test these too, < em > after< / em > you have done a full < a href = "trogimport.html" > data import< / a > :
2021-10-23 22:40:12 +01:00
< br > - < var > < a href = "http://localhost:8000/pathsreport" > http://localhost:8000/pathsreport< / a > < / var >
< br > - < var > < a href = "http://localhost:8000/stats" > http://localhost:8000/stats< / a > < / var >
2021-10-27 19:25:37 +01:00
< br > - < var > < a href = "http://localhost:8000/people" > http://localhost:8000/people< / a > < / var > (takes a minute or so)
2021-10-23 22:40:12 +01:00
< br > - < var > < a href = "http://localhost:8000/expofiles/surveyscans/2019/walletindex.html" > http://localhost:8000/expofiles/surveyscans/2019/walletindex.html< / a > < / var >
2021-12-01 21:12:07 +00:00
< br > - < var > < a href = "http://localhost:8000/survexfile/caves/" > http://localhost:8000/survexfile/caves/< / a > < / var >
2021-10-23 22:40:12 +01:00
< br > - < var > < a href = "http://localhost:8000/expofiles/training-info/Idiots guide to accessing expo git.pptx" > http://localhost:8000/expofiles/training-info/Idiots guide to accessing expo git.pptx< / a > < / var >
2022-03-18 22:36:54 +00:00
< br > - < var > < a href = "http://localhost:8000/1623/291/291.html" > http://localhost:8000/1623/291/291< / a > < / var >
2021-10-23 22:40:12 +01:00
< br > - < var > < a href = "http://localhost:8000/caves" > http://localhost:8000/caves< / a > < / var >
< br > - < var > < a href = "http://localhost:8000/admin/doc/models/core.expedition/" > ttp://localhost:8000/admin/doc/models/core.expedition/< / a > < / var > (admin login required)
< br > - < var > < a href = "http://localhost:8000/survexfile/204" > http://localhost:8000/survexfile/204< / a > < / var >
2021-10-27 19:25:37 +01:00
< h4 > Check parsing and importing< / h4 >
< p >
Nearly half the code deals with importing and parsing data, so you need to test that a full data import works. Run the full data import < var > troggle$ python databaseReset.py reset R000< / var > . It should take about 5 minutes to import everything. See < a href = "trogimport.html" > Troggle Full Import< / a > for what you should expect to see.
2021-10-23 22:40:12 +01:00
< h4 > Use git to commit your edits< / h4 >
< p > You need to know git. Sorry, but there it is. See < a href = "../computing/repos.html" > our git repositories< / a > and < a href = "../computing/qstart-git.html" > our git cheat sheet< / a > .
2021-10-22 19:04:23 +01:00
2021-10-24 14:31:22 +01:00
< h3 id = "dbtools" > Helpful database tools and scripts< / h3 >
< img class = "onleft" width = "100px" src = "https://mariadb.com/kb/static/images/logo-2018-black.95f5978ae14d.png" >
< img class = "onright" width = "80px" src = "https://sqlite.org/images/sqlite370_banner.gif" >
< p > The public server uses a < a href = "https://mariadb.org/about/" > MariaDB SQL database< / a > and development is usually done using a single-user < a href = "https://sqlite.org/about.html" > sqlite database< / a > which is a standard Django option.
< p >
2021-10-27 19:25:37 +01:00
You will find it very, very useful to see what is going on if you look directly at the data in the database (just a single file in the sqlite case) and browse the data in the tables. This is vital when doing Django migrations between Django versions. A light-weight, simple db browser is < a href = "https://sqlitebrowser.org/" > DB Browser for SQLite< / a > . Connecting directly the the MariaDB database with a control panel or < a href = "https://www.mysql.com/products/workbench/" > workbench< / a > gives even more tools and documentation capabilities. See the < a href = "serverconfig.html" > troggle server documentation< / a > for how to install MariaDB.
2021-10-22 19:04:23 +01:00
2021-10-22 14:18:09 +01:00
< hr / >
Go on to: < a href = "trogarch.html" > Troggle architecture< / a > < br / >
Return to: < a href = "trognotes.html" > Troggle programmers' guide< / a > < br / >
Troggle index:
< a href = "trogindex.html" > Index of all troggle documents< / a > < br / >
2021-10-23 22:40:12 +01:00
< hr / >
< / body >
2021-10-22 14:18:09 +01:00
< / html >
