Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
PyLucid is a Open Source web content management system written in Python using the Django Framework.


about PyLucid

PyLucid is an Open Source web content management system written in Python.

This django-cms branch is a completely rewrite.

The current state of the Django-CMS branch is not useable :(

Fork and contribute! ;)

Coverage Status on
Build Status on



The Pillow (PIL fork) doesn't provide binaries for Linux. Make sure you have Python’s development libraries installed. e.g.:

$ sudo apt-get install python3-dev libjpeg-dev libfreetype6-dev

more info here:

bootstrap PyLucid

# download bootstrap file:
/home/FooBar$ wget

# Create virtualenv with all needed packages:
/home/FooBar$ python3 ~/PyLucid_env

Now you have a virtual environment with all existing packages.

create page instance

You can create a new page instance with the pylucid_installer cli programm:

# Go into created virtualenv:
/home/FooBar$ cd ~/PyLucid_env

# activate the env:
~/PyLucid_env $ source bin/activate

# Create a page instance:
(PyLucid_env) ~/PyLucid_env $ pylucid_installer --dest=~/page_instance --name=MyCoolSite

# Go into created page instance
(PyLucid_env) ~/PyLucid_env $ cd ~/page_instance/

# init django
(PyLucid_env) ~/page_instance $ ./ syncdb

# run dev. server:
(PyLucid_env) ~/page_instance $ ./ runserver

Info: You can also create more than one page instance! All page instance will use the same environment.

optional packages

Before any pip install, go to your virtual env and activate it! e.g.:

/home/FooBar$ cd ~/PyLucid_env
~/PyLucid_env $ source bin/activate

MySQL DB API Driver:

(PyLucid_env) ~/PyLucid_env $ pip install mysqlclient

see also: Django database docs.

FastCGI wrapper for WSGI applications:

(PyLucid_env) ~/PyLucid_env $ pip install flipflop

see also:


# go to your virtual env and activate it:
/home/FooBar$ cd ~/PyLucid_env
~/PyLucid_env $ source bin/activate
(PyLucid_env) ~/PyLucid_env $ cd src/pylucid/

# run the tests:
(PyLucid_env) ~/PyLucid_env/src/pylucid $ ./ test

PyLucid v1 migration

Use use the Multiple databases feature to migrate a old v1 installation: e.g.:

    'default': { # New, empty database for PyLucid v2 data
    'legacy': { # Your old database with existing PyLucid v1 data

You must activate some settings:

  • pylucid_migration, pylucid_todo in INSTALLED_APPS
  • Activate a 'legacy' named second database with the old PyLucid v1 data

(All parts exists in the example project settings ;) )

commands for migration, e.g.:

# migrate old pages to django-cms:
(PyLucid_env) ~/page_instance $ ./ migrate_pylucid --inline_script

# migrate old blog entries to djangocms-blog:
(PyLucid_env) ~/page_instance $ ./ migrate_blog --inline_script

# export existing designs into filesystem
(PyLucid_env) ~/page_instance $ ./ export_designs

NOTE: With the argument --inline_script all <script> areas would be migrate to a html-markup entry. So all <script> areas are active after migration. Without --inline_script all <script> areas will be result in escaped text.

All unsupported lucidTag entries will be migrate to the "ToDoPlugin". SO the origin code is not away, but will be not visible for anonymous users.

dev info

Currently the base files are a mix of:



Development history visible / backward-incompatible changes
IRC #pylucid on
Google code
Something went wrong with that request. Please try again.