nik/FreedomBox
1
0
Fork 0
mirror of https://github.com/freedombox/FreedomBox.git synced 2026-05-27 10:44:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

Minor styling and doc updates related to module cleanup

Browse Source
This commit is contained in:
Sunil Mohan Adapa 2014-12-14 17:27:11 +05:30
parent 90203986f2
commit 61fefcff01
3 changed files with 12 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/modules.mdwn
View File

@ -12,11 +12,17 @@ installation is as simple as `aptitude install freedombox-foo`. As an
intermediate step, we'll start scripting module installation. But intermediate step, we'll start scripting module installation. But
until then, we can install them manually. until then, we can install them manually.
A module can be represented inside of Plinth via a django app. A Plinth module is a Django application with some additional Plinth
To enable a module, put a file containing its python path into specific extensions. To enable a module, create a file containing its
`data/etc/plinth/modules-enabled/`. Django is configured to use all Python module path into `data/etc/plinth/modules-enabled/`. During
modules of the `modules-enabled` folder as apps. With the python path installation, this file will be copied to
you can also include modules/apps outside of plinth. `/etc/plinth/modules-enabled/`. The file in `/etc` will be read during
normal execution of Plinth. The file in `data/etc/` in the source code
directory will be used when running Plinth under the run-without-install
mode. Plinth will read the module path from the file in one of these
paths during start-up and configure Django to use it as a Django
application. With this approach, you can install your Plinth module
anywhere on the system and use it in Plinth (just like in Django).
TODO: automatically prune dead links to clear out old module installs. TODO: automatically prune dead links to clear out old module installs.
This is something the install scripts should do. This is something the install scripts should do.

2
plinth/modules/config/templates/config.html
View File

@ -22,7 +22,6 @@
{% block content %} {% block content %}
<form class="form" method="post"> <form class="form" method="post">
{% csrf_token %} {% csrf_token %}
@ -32,5 +31,4 @@
</form> </form>
{% endblock %} {% endblock %}

2
plinth/modules/users/urls.py
View File

@ -39,7 +39,7 @@ urlpatterns = patterns(
url(r'^sys/users/(?P<slug>[\w.@+-]+)/change_password/$', url(r'^sys/users/(?P<slug>[\w.@+-]+)/change_password/$',
login_required(views.UserChangePassword.as_view()), login_required(views.UserChangePassword.as_view()),
name='change_password'), name='change_password'),
# add djangos login/logout urls # Add Django's login/logout urls
url(r'^accounts/login/$', 'django.contrib.auth.views.login', url(r'^accounts/login/$', 'django.contrib.auth.views.login',
{'template_name': 'login.html'}, name='login'), {'template_name': 'login.html'}, name='login'),
url(r'^accounts/logout/$', 'django.contrib.auth.views.logout', url(r'^accounts/logout/$', 'django.contrib.auth.views.logout',