Tag Archives: django

Rebooting the community

This year Kiberpipa will be 10+ years old and its’ event lineup is incredible. Over 350 events a year involving various talks, meetups, screening and everything. During this time a bunch of new technologies showed and demand for jobs as well as our interest shifted and I/we stared creating bigger and more exclusive events (as in: you can only attend if you speak).

Django Meet Ljubljana, 6. julij 2011

It mostly worked, with limited success. What happens is that while the core members Kiberpipa and related communities are used to speaking and working out in the open, not everyone is. And we didn’t give new members of community a chance to slowly build up their involvement.

With this in mind, I’m hoping that we can get a few more meetups and events going where minimum level of involvement is a 15-min talk instead of a full 45-min lecture with all eyes on you.

Assumptions of your ecosystem


I’ve recently started helping out with limesurvey project, more specifically, their rewrite to CakePHP. One of the latest tickets I help with was to add optional table prefix, so you could have separate installations using the same database.

This is something you would never see in Django world, where everyone can afford as many databases as they have apps and you don’t have such artificial limits.

After discussing the topic of adding support for this, with all the problems it comes with, the reality is pretty grim – while we might have access to a number of servers, most of the [limesurvey] users are on cheap or simply outdated PHP hosting plans and still need this hack.

This is important because if we want to build great open-source application, we have to consider our end users and with it, their ecosystem of apps that they use. If you’re building a PHP software, you just can’t afford to not have table prefixes.

Python SMTP sink server

Debugging email sending in your Web application is always tricky as you need a working SMTP and you also need to watch out that you don’t accidently spam real users (if you’re working on a local copy of real database).

There is a neat one liner that acts as a “sink smtpd” server, meaning that it implements SMTP protocol, so you app can communicate with it, while printing everything it receives on screen:

sudo /usr/lib/python2.6/smtpd.py -n -c DebuggingServer localhost:25

(via Django Snippets)