Projects

South

South is a database migration framework for Django applications.

The NOC Project

NOC Project is an Operation Support System (OSS) for telecom companies, service providers, and enterprise Network Operation Centers (NOC). Areas covered by NOC include: * service activation/provisioning * multi-VRF address space management (IPAM) * multi-vendor configuration management * fault ... [More] management * performance management * VC management * DNS provisioning * knowledge base * peering management * RPSL and BGP filter generation * Reporting. NOC is open source and released under the terms of BSD LICENSE [Less]

Django Evolution

When you run ./manage.py syncdb, Django will look for any new models that have been defined, and add a database table to represent those new models. However, if you make a change to an existing model, ./manage.py syncdb will not make any changes to the database. This is where Django Evolution ... [More] fits in. Django Evolution is an extension to Django that allows you to track changes in your models over time, and to update the database to reflect those changes. [Less]

django-firebird

Firebird backend for Django. Original project: http://code.google.com/p/django-firebird GitHub fork (with Django 1.2+ support and more): http://github.com/idlesign/django-firebird

deseb

Django External Schema Evolution Branch Django, via the command ./manage syncdb, can automatically build a database schema based on your applications models.py file. However, after you've done this once, it leaves you with two unpleasant follow-up options if you ever make any changes to your ... [More] model structure: 1. destroy your existing schema (along with all your data) and let ./manage syncdb rebuild it for you 2. manage your own schema upgrades by writing your own SQL Project deseb aims to fill this void by providing s third option: 3. generate schema upgrades via the command: ./manage evolvedb [Less]

django-treebeard

django-treebeard is a library that implements efficient tree implementations for the Django Web Framework 1.0+, written by Gustavo Picón and licensed under the Apache License 2.0. django-treebeard is: - Flexible: Includes 3 different tree implementations - with the same API: 1. ... [More] Adjacency List 2. Materialized Path 3. Nested Sets - Fast: Optimized non-naive tree operations (see Benchmarks). - Easy: Uses Django Model Inheritance with abstract classes to define your own models. - Clean: Testable and well tested code base. Code/branch test coverage is above 96% [Less]

pgmigrate

The pgmigrate tool is developed for managing changes in database structure between a project members. It does so by managing so called 'patches'. Small pieces of SQL or Python code which modifies database schema. So far it supports only PostgreSQL. Starting from 1.2.0 can be easily integrated with Django to solve schema migration issue.

django-reports

A django application to build flexible, extensible reports through the web or as part of your views. This project has been started due to interest on the django-users mailing list and very much subscribes to the "release early and often" philosophy. It is definitely not production ready ... [More] , but this is an app that I think that users of django could benefit from, especially for those who are interfacing with legacy databases or in some sort of enterprise setting. The idea is a central register which can easily tell you which fields are available for reports, and allows you to add to define your own reports in a sub-directory of your apps (much like the existing templatetags works). Here's an example from one of my app's report.py: from nokia.reporting.helpers import FieldRegister from datetime import timedelta reg = FieldRegister() @reg.register('Adjusted MTTR','Ticket','mttr') def adjusted_mttr(ticket): """The mean time to repair of the ticket""" ... rest of code body hereIn addition to the register, there are also a couple of Models (one for holding information on all the available fields, and one for your persistent Report objects) and these between them generate Reporter objects, which can produce CSV. I'm not convinced that I've taken the right approach in all areas of the application, and I'd very much like feedback and ideas, specifically: The right way to persist the report objects, their construction is not really consistent and perhaps a relational database structure isn't the best means of storage. I'm thinking that RDF or something similar (XML of some other sort) might be better? Testing... I'm not really familiar with how to go about TDD, but i'd like to learn! User interface, I'm designing this to be brain dead (think dilbert manager ;-) ) simple to use. Presently this UI is dependant on Prototye, and I think this might hinder integrating it into admin views in the future. Example code: >>> fld_reg = FieldRegister() >>> usr = fld_reg.User >>> #usr now has a representation of all of the fields the auth.User has, uncluding a >>> #count field for all of the FK and M2M relations and reverse relations: >>> usr > >>> usr._fields #This is all of the User._meta.fields [, ........ ] >>> usr.message_set >>> usr.message_set.title 'Count of Message Set'The best way to get to know the app is probably to install it, run syncdb, run generate_fields() (which is in helpers.py), and then have a play using ./manage.py shell. If you're using IPython you'll be up and running in no time. [Less]

Newsmemory

Import, store and retrieve news from the web. - use provided websites importers or build your own very easily - newsmemory will parse the web and store the articles periodically - a web interface lets you browse the news or search the database - flag a newsitem, the others users will see it as flagged

django-zodb

Using Django and ZODB together.