Fork of Troggle for complete overhaul of front-end code: Troggle Unchained
Go to file
martin speleo ff199f0d2f [svn] wiki_to_html changes.
Changes views of qm model.
2009-07-04 19:35:06 +01:00
core [svn] wiki_to_html changes. 2009-07-04 19:35:06 +01:00
docsEtc [svn] Draft of paper for ICS. 2009-05-13 05:51:21 +01:00
export [svn] Renaming troggle.expo to troggle.core. To do this, used: 2009-07-02 20:43:18 +01:00
imagekit [svn] Switch from photologue to imagekit. Less bloat. 2009-05-13 06:24:52 +01:00
media [svn] * Adding JS fill in next QM number via ajax. 2009-07-04 08:27:49 +01:00
parsers [svn] Pareser for cave descriptions 2009-07-04 17:19:30 +01:00
profiles [svn] Brief code cleanup. 2009-07-03 05:31:49 +01:00
registration [svn] A few registration updates 2009-05-30 16:17:19 +01:00
templates [svn] 2009-07-04 18:41:48 +01:00
wiki [svn] Edited wiki page through web user interface. 2009-06-11 06:35:18 +01:00
__init__.py [svn] Initial troggle checkin 2009-05-13 05:13:38 +01:00
databaseReset.py [svn] Work on turn html pages into cavedescription models.py. 2009-07-04 16:42:17 +01:00
localsettingsserver.py [svn] survey block object 2009-05-13 05:39:52 +01:00
localsettingsubuntu.py [svn] backup settings 2009-06-09 19:52:32 +01:00
localsettingswindows.py [svn] fix logfile setting 2009-06-09 18:20:55 +01:00
manage.py [svn] Initial troggle checkin 2009-05-13 05:13:38 +01:00
middleware.py [svn] Initial troggle checkin 2009-05-13 05:13:38 +01:00
README.txt [svn] Fix leftover from expo -> core rename, and add databaseReset.py to README.txt 2009-07-02 22:31:28 +01:00
settings.py [svn] Remove old subcave model, along with mptt and feincms. Also move OtherCaveNames admin representation to an inline in Cave. 2009-07-04 19:26:51 +01:00
urls.py [svn] Remove old subcave model, along with mptt and feincms. Also move OtherCaveNames admin representation to an inline in Cave. 2009-07-04 19:26:51 +01:00
utils.py [svn] Work on turn html pages into cavedescription models.py. 2009-07-04 16:42:17 +01:00

Troggle is an application for caving expedition data management, originally created for use on Cambridge University Caving Club expeditions and licensed under the GNU Lesser General Public License.

Troggle setup
==========

Python, Django, and Database setup
-----------------------------------
Troggle requires Django 1.1 or greater, and any version of Python that works with it. As of writing this readme, there was no actual Django 1.1 release, so Troggle required the SVN version of Django. Check Django out to somewhere on your PYTHONPATH with the following command:

svn co http://code.djangoproject.com/svn/django/trunk/

If you have an older installation of Django installed on your system, the easiest way to make sure troggle is using the newest version of Django is to simply checkout into your top troggle directory, into a folder called django.

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 svn check out Troggle into it using the following command:

svn co http://troggle.googlecode.com/svn/

If you want to work on the source code and be able to commit, you will need to use https instead of http, and your google account will need to be added to the troggle project members list. Contact aaron dot curtis at cantab dot net 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.

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.

To do this, run "python manage.py runserver" from the troggle directory.