Sphene Community Tools

almost .. the subfolder auf sphenecoll has to be symlinked - something like ln -s /path/to/communitytools/sphenecoll/sphene /path/to/python/site-packages/

or you could do the same as CommunityDraft in settings.py:

import os
ROOT_PATH = os.path.dirname(os.path.abspath(__file__))
# SCT library path.
LIB_PATH = os.path.join(ROOT_PATH,'..','..','communitytools', 'sphenecoll')

(btw. if you are new to django and you just want to get SCT up and running i would suggest to use CommunityDraft - just checkout 'communitytools' and 'communitydraft' into the same folder and follow the documentation in CommunityDraft - or download the latest release - which contains both projects already)

anonymous said @ 2008-10-26 11:35:51:

The second part, does that mean static/ needs to be within my django project dir (also symlink)? or within my site-packages/django/ ?

communitytools/static/sphene has to be served under {{ MEDIA_URL }}sphene - this means in development you should add a simple url config:

  ## for development only ...
  (r'^static/sphene/(.*)$', 'django.views.static.serve', 
    {'document_root': '/path/to/communitytools/static/sphene' }),

and when deploying it you either symlink it, or configure an Alias for /static/sphene in your apache..

--- Last Edited by Herbert Poul at 2008-10-26 11:54:38 ---