mirror of
https://expo.survex.com/repositories/troggle/.git
synced 2024-11-21 23:01:52 +00:00
85 lines
3.4 KiB
Plaintext
85 lines
3.4 KiB
Plaintext
Troggle is an application for caving expedition data management, originally created for use on Cambridge University Caving Club (CUCC)expeditions and licensed under the GNU Lesser General Public License.
|
|
|
|
Troggle has been forked into two projects. The original one is maintained by Aron Curtis and is used for Erebus caves. The CUCC variant uses files as the definitive data, not the database and lives at expo.survex.com/troggle.
|
|
|
|
Troggle setup
|
|
==========
|
|
|
|
Python, Django, and Database setup
|
|
-----------------------------------
|
|
Troggle requires Django 1.4 or greater, and any version of Python that works with it.
|
|
It is currently (Feb.2020) on django 1.7.11 (1.7.11-1+deb8u5).
|
|
Install Django with the following command:
|
|
|
|
sudo apt install python-django (on debian/ubuntu) -- does not work now as we need specific version
|
|
|
|
Install like this:
|
|
sudo apt install pip
|
|
pip install django==1.7
|
|
pip install django-tinymce=2.0.1
|
|
sudo apt install libfreetype6-dev
|
|
pip install --no-cache-dir pillow==2.7.0
|
|
pip install django-registration==2.0
|
|
pip install unidecode
|
|
|
|
If you want to use MySQL or Postgresql, download and install them. However, you can also use Django with Sqlite3, which is included in Python and thus requires no extra installation.
|
|
|
|
|
|
|
|
Troggle itself
|
|
-------------
|
|
Choose a directory where you will keep troggle, and git clone Troggle into it using the following command:
|
|
|
|
git clone git://expo.survex.com/troggle
|
|
or more reliably
|
|
git clone ssh://expo@expo.survex.com/home/expo/troggle
|
|
|
|
|
|
If you want to work on the source code and be able to commit, your account will need to be added to the troggle project members list. Contact wookey at wookware dot org to get this set up.
|
|
|
|
Next, you need to fill in your local settings. Copy either localsettingsubuntu.py or localsettingsserver.py to a new file called localsettings.py. Follow the instructions contained in the file to fill out your settings.
|
|
|
|
|
|
Setting up tables and importing legacy data
|
|
------------------------------------------
|
|
Run "python databaseReset.py reset" from the troggle directory.
|
|
|
|
|
|
Once troggle is running, you can also log in and then go to "Import / export" data under "admin" on the menu.
|
|
|
|
Adding a new year/expedition requires adding a column to the
|
|
folk/folk.csv table - a year doesn't exist until that is done.
|
|
|
|
|
|
Running a Troggle server
|
|
------------------------
|
|
For high volume use, Troggle should be run using a web server like apache. However, a quick way to get started is to use the development server built into Django. This is limited though: directory
|
|
redirection needs apache.
|
|
|
|
To do this, run "python manage.py runserver" from the troggle directory.
|
|
|
|
|
|
Running a Troggle server with Apache
|
|
------------------------------------
|
|
Troggle also needs these aliases to be configured. These are set in
|
|
/home/expo/config/apache/expo.conf
|
|
on the expo server.
|
|
|
|
At least these need setting:
|
|
DocumentRoot /home/expo/expoweb
|
|
WSGIScriptAlias / /home/expo/troggle/wsgi.py
|
|
Alias /expofiles /home/expo/expofiles
|
|
Alias /photos /home/expo/webphotos
|
|
Alias /map /home/expo/expoweb/map
|
|
Alias /javascript /usr/share/javascript
|
|
Alias /static/ /home/expo/static/
|
|
ScriptAlias /repositories /home/expo/config/apache/services/hgweb/hgweb.cgi
|
|
|
|
(The last is just for mercurial which will be remoived during 2020).
|
|
|
|
Unlike the "runserver" method, apache requires a restart before it will use
|
|
any changed files:
|
|
|
|
apache2ctl stop
|
|
apache2ctl start
|