| 'sphene.community.context_processors.navig | | 'sphene.community.context_processors.navig |
| ation', | | ation', |
| ) | | ) |
| | | |
| ## Modifying urls.py | | ## Modifying urls.py |
| | | |
| n | Now you have to wire up the three applications int | n | Now you have to wire up the three applications int |
| o your urls.py so modify simpleproject/urls.py and | | o your urls.py so modify simpleproject/urls.py and |
| add the following to the patterns('', ..) list: | | update it to match the following: |
| | |
|
| | | defaultdict = { 'groupName': 'example' }
|
| | | |
| urlpatterns = patterns('', | | urlpatterns = patterns('', |
| n | url(r'^community/', include('sphene.commun | n | url(r'^community/', include('sphene.commun |
| ity.urls')), | | ity.urls'), defaultdict), |
| url(r'^board/', include('sphene.sphboard.u | | url(r'^board/', include('sphene.sphboard.u |
| rls')), | | rls'), defaultdict), |
| url(r'^wiki/', include('sphene.sphwiki.url | | url(r'^wiki/', include('sphene.sphwiki.url |
| s')), | | s'), defaultdict), |
| ) | | ) |
| n | | n |
|
| | | (the meaning of 'groupName' is described further b |
| | | elow.)
|
| | | |
| ## Synchronizing tables | | ## Synchronizing tables |
| | | |
| After adding the community projects, run syncdb ag | | After adding the community projects, run syncdb ag |
| ain which will create all necessary tables. (Becau | | ain which will create all necessary tables. (Becau |
| se of south you have to use syncdb --all and migra | | se of south you have to use syncdb --all and migra |
| te --fake for the first time. Whenever you upgrade | | te --fake for the first time. Whenever you upgrade |
| SCT you have to run: ./manage.py migrate). | | SCT you have to run: ./manage.py migrate). |
| | | |
| | | |
| For a more complete example you can look into the | | For a more complete example you can look into the |
| [simpleproject example in the subversion repositor | | [simpleproject example in the subversion repositor |
| y](https://github.com/hpoul/sct-communitytools/blo | | y](https://github.com/hpoul/sct-communitytools/blo |
| b/master/examples/simpleproject/sitetemplates/base | | b/master/examples/simpleproject/sitetemplates/base |
| .html). | | .html). |
| | | |
| ## And we are done | | ## And we are done |
| | | |
| t | Now start your project with ./manage.py runserver | t | Now start your project with ./manage.py runserver |
| and head over to http://127.0.0.1/board/ - You sho | | and head over to http://127.0.0.1:8000/board/ - Yo |
| uld see a very *simple* forum application. | | u should see a very *simple* forum application. |
| | | |
| # Community Groups | | # Community Groups |
| | | |
| In SCT everything is based on 'Community Groups' - | | In SCT everything is based on 'Community Groups' - |
| every forum or wiki snip is part of a 'Group' - T | | every forum or wiki snip is part of a 'Group' - T |
| his Group has nothing to do with the user groups w | | his Group has nothing to do with the user groups w |
| hich is basically only for assigning permissions - | | hich is basically only for assigning permissions - |
| a community group is more similar to the concept | | a community group is more similar to the concept |
| of the [Sites Application](http://www.djangoprojec | | of the [Sites Application](http://www.djangoprojec |
| t.com/documentation/sites/) since every community | | t.com/documentation/sites/) since every community |
| Group has one URL assigned. The main difference is | | Group has one URL assigned. The main difference is |
| tough, that Community Groups are ment to be hoste | | tough, that Community Groups are ment to be hoste |
| d on the same django instance with the same config | | d on the same django instance with the same config |
| uration, while Sites have a different configuratio | | uration, while Sites have a different configuratio |
| n for each 'Site'. | | n for each 'Site'. |
| | | |
