SimonBoulier f18aa84f69 Fix #14 (and a bit more) : Correct several spelling/translation errors in the admin interface 7 years ago
..
fixtures 67c59bedae isp_database: remove #illyse-off from fixture, to avoid ordering issues on db.ffdn.org 10 years ago
migrations f18aa84f69 Fix #14 (and a bit more) : Correct several spelling/translation errors in the admin interface 7 years ago
templates 7010718d84 added an inclusion tag to display the address of the isp 10 years ago
templatetags 718aa15589 iban is now more readable on bills 10 years ago
README.md f8daeff82c Add a README for ISP database application 10 years ago
__init__.py 9f8d1c0d4a Basic ISP database application 10 years ago
admin.py a5444e4157 Adapt admin configs to Django 1.8 8 years ago
context_processors.py 2884ef98a3 de-illysification of html templates, using available information from isp_database.ISPInfo 10 years ago
models.py f18aa84f69 Fix #14 (and a bit more) : Correct several spelling/translation errors in the admin interface 7 years ago
tests.py 636bceb6b3 Fix crash on /members/contact when no chatroom specified 8 years ago
views.py 3f497741ef Add a Cache-control header on /isp.json 10 years ago

README.md

ISP database application

The goal of this application is to generate a JSON file describing an ISP, as defined by http://db.ffdn.org/format

Most information about the ISP can be entered through the admin. The number of members and subscribers is computed automatically: you may want to change the way they are computed depending on the way you manage members and subscribers. Additionally, it is possible to change the model so that you manage the number of members and subscribers by hand in the admin, though this is not recommended.

The JSON file is then accessible at /isp.json

How to use

First, add coin.isp_database to your INSTALLED_APPS in settings.py.

Then, add the following in your main urls.py:

from coin.isp_database.views import isp_json

and add

url(r'^isp.json$', isp_json),

in your urlpatterns variable.

Known issues

Grep for "TODO" in the code.

  • the "progress status" field is not user-friendly
  • the model for GPS coordinates is not good (no validation)
  • currently, only one technology is allowed for each covered area
  • describing the geographical shape (polygone) of a covered area is not supported