Kotti 0.1a8

A friendly, light-weight web content management system (WCMS). Written in Python, based on Pyramid and SQLAlchemy.

Contents

• Kotti

  • What is Kotti?

    • Try it out

    • Unstable

  • Issue tracker and development

  • Requirements

  • Installation using virtualenv

  • Installation using buildout

  • Configuring Kotti

    • kotti.site_title

    • Mail settings: mail.default_sender, mail.host and friends

    • kotti.templates.master_view and kotti.templates.master_edit

    • kotti.templates.base_css, kotti.templates.view_css, and kotti.templates.edit_css

    • kotti.principals

    • kotti.secret

    • kotti.includes and kotti.base_includes

    • kotti.available_types

    • kotti.configurators

    • kotti.authn_policy_factory and kotti.authz_policy_factory

    • kotti.session_factory

  • Authentication and Authorization

    • ACL

    • Roles and groups

  • Under the hood

  • License

  • Thanks

  • History

    • 0.1a8

    • 0.1a7

    • 0.1a6

    • 0.1a5

    • 0.1a4

Kotti

What is Kotti?

Kotti is a user-friendly web content management system (WCMS).

Features:

• A simple, user-friendly edit interface that hides advanced functionality from less experienced content managers.

• Separation of public site and editor interface allows for easier templating

• Easily extensible with your own look & feel with no programming required

• a WYSIWYG editor

• Advanced user and groups management, Access control lists (ACL) for fine-grained security control

• Support for pluggable authentication modules and single sign-on

• Easy configuration through use of INI files.

• Extensible with your own content types and views

Try it out

You can try out Kotti on Kotti’s demo site.

Unstable

At this point, Kotti is experimental. You’re encouraged to try it out and give us feedback, but don’t use it in production yet. We’re likely to make fundamental changes to both Kotti’s API and its database structure in weeks to come.

Issue tracker and development

Kotti is developed on Github. The issue tracker also lives there.

Kotti’s mailing list for both users and developers is at http://groups.google.com/group/kotti

You can also find us on IRC: join the #kotti channel on irc.freenode.net.

Requirements

Kotti requires Python 2.5 or later to run.

Installation using virtualenv

It’s recommended to install Kotti inside a virtualenv.

Change into the directory of your Kotti download and issue:

$ python setup.py install

To run Kotti with the included development profile then type:

$ paster serve development.ini

To run all tests:

$ python setup.py nosetests

Installation using buildout

Alternatively, you can use the provided buildout configuration like so:

$ python bootstrap.py
$ bin/buildout

To run Kotti with the included development profile then type:

$ bin/paster serve development.ini

To run all tests:

$ bin/test

Configuring Kotti

Kotti includes two Paste Deploy configuration files in production.ini and development.ini.

There are various kotti.* configuration variables that allow you to configure and extend various aspects of Kotti, such as the master templates and CSS files used in Kotti’s UI, the user database implementation, and the list of available content types.

kotti.site_title

Your site’s title.

Mail settings: mail.default_sender, mail.host and friends

Kotti uses pyramid_mailer for its e-mailing. See the configuration options in the pyramid_mailer docs.

kotti.templates.master_view and kotti.templates.master_edit

The default configuration for these two variables is:

kotti.templates.master_view = kotti:templates/view/master.pt
kotti.templates.master_edit = kotti:templates/edit/master.pt

You may override these to provide your own master templates.

kotti.templates.base_css, kotti.templates.view_css, and kotti.templates.edit_css

These variables define the CSS files used by the default master templates. The factory settings here are:

kotti.templates.base_css = kotti:static/base.css
kotti.templates.view_css = kotti:static/view.css
kotti.templates.edit_css = kotti:static/edit.css

kotti.principals

Kotti comes with a default user database implementation in kotti.security.principals. You can use the kotti.principals configuration variable to override the implementation used. The default looks like this:

kotti.principals = kotti.security.principals

kotti.secret

kotti.secret (required) and kotti.secret2 (optional) are used as salts for various hashing functions. Also, kotti.secret is the password of the default admin user. (The admin password you should change immediately after you log in.)

An example:

kotti.secret = qwerty
kotti.secret2 = asdfgh

With these settings, to log in as admin, you would log in as admin with the password qwerty. Do not use these defaults in production.

kotti.secret is used as a salt to the passwords in the default user database. Changing it will result in the user database’s passwords becoming invalid.

kotti.includes and kotti.base_includes

kotti.includes allows for convenient extension of Kotti with additional views, content types and event handlers. An example:

kotti.includes = mypackage.views

You should list here modules that contain an includeme function. A mypackage.views module could have this function, which would register an edit view for a hypothetical event content type:

def includeme(config):
    config.add_view(
        edit_event,
        context=Event,
        name='edit',
        permission='edit',
        )

kotti.base_includes is a list of modules that Kotti itself defines for inclusion. The default:

kotti.includes =
  kotti.events kotti.views.view kotti.views.edit
  kotti.views.login kotti.views.site_setup

Note that it’s also possible to set these options directly from your Python package by use of the kotti.configurators configuration variable.

kotti.available_types

Defines the list of content types available. The default configuration here is:

kotti.available_types = kotti.resources.Document

You may replace or add your own types with this variable. An example:

kotti.available_types =
    kotti.resources.Document
    mypackage.resources.Calendar
    mypackage.resources.Event

kotti.resources.Document is itself a class that’s suitable as an example of a Kotti content type implementation:

class Document(Node):
    type_info = Node.type_info.copy(
        name=u'Document',
        add_view=u'add_document',
        addable_to=[u'Document'],
        )

    def __init__(self, body=u"", mime_type='text/html', **kwargs):
        super(Document, self).__init__(**kwargs)
        self.body = body
        self.mime_type = mime_type

documents = Table('documents', metadata,
    Column('id', Integer, ForeignKey('nodes.id'), primary_key=True),
    Column('body', UnicodeText()),
    Column('mime_type', String(30)),
)
mapper(Document, documents, inherits=Node, polymorphic_identity='document')

kotti.configurators

Requiring users of your package to set all the configuration variables by hand in pasteserve.ini is not ideal. That’s why Kotti includes a configuration variable through which extending packages can set all other configuration options through Python. Here’s an example of a function that configures Kotti:

# in mypackage/__init__.py
def kotti_configure(config):
    config['kotti.base_includes'] += ' mypackage.views'
    config['kotti.principals'] = 'mypackage.security.principals'

And this is how you’d hook it up in the Paste Serve ini file:

kotti.configurators = mypackage.kotti_configure

kotti.authn_policy_factory and kotti.authz_policy_factory

You can override the authentication and authorization policy that Kotti uses. By default, Kotti uses these factories:

kotti.authn_policy_factory = kotti.authtkt_factory
kotti.authz_policy_factory = kotti.acl_factory

These settings correspond to pyramid.authentication.AuthTktAuthenticationPolicy and pyramid.authorization.ACLAuthorizationPolicy being used.

kotti.session_factory

The kotti.session_factory configuration variable allows the overriding of the default session factory, which is pyramid.session.UnencryptedCookieSessionFactoryConfig.

Authentication and Authorization

We’re currently working on a user interface for user management.

Authentication in Kotti is pluggable. See kotti.authn_policy_factory.

ACL

Auhorization in Kotti can be configured through kotti.authz_policy_factory. The default implementation uses inherited access control lists. The default install of Kotti has a root object with this ACL that’s defined in kotti.security.SITE_ACL:

SITE_ACL = [
    ['Allow', 'system.Everyone', ['view']],
    ['Allow', 'role:viewer', ['view']],
    ['Allow', 'role:editor', ['view', 'add', 'edit']],
    ['Allow', 'role:owner', ['view', 'add', 'edit', 'manage']],
    ]

This makes the site viewable by everyone per default. You can set the ACL on the site to your liking. To lock down the site so that only authenticated users can view, do:

from kotti.resources import get_root
root = get_root(request)
root.__acl__ = root.__acl__[1:] + [('Allow', 'system.Authenticated', ['view'])]

Roles and groups

The default install of Kotti maps the role:admin role to the admin user. The effect of which is that the admin user gains ALL_PERMISSIONS throughout the site.

Principals can be assigned to roles or groups by use of the kotti.security.set_groups function, which needs to be passed a context to work with:

from kotti.security import set_groups
set_groups(bobsfolder, 'bob', ['role:owner'])

To list roles and groups of a principal, use kotti.security.list_groups. Although you’re more likely to be using Pyramid’s security API in your code.

Under the hood

Kotti is written in Python and builds upon on the two excellent libraries Pyramid and SQLAlchemy. Kotti tries to leverage these libraries as much as possible, thus:

• minimizing the amount of code and extra concepts, and

• allowing users familiar with Pyramid and SQLAlchemy to feel right at home since Kotti’s API is mostly that of Pyramid and SQLAlchemy.

For storage, you can configure Kotti to use any relational database for which there is support in SQLAlchemy. There’s no storage abstraction apart from that.

Have a question? Join our mailing list at http://groups.google.com/group/kotti or read this blog post for more implementation details.

License

Kotti is available under the BSD- derived Repoze Public License.

Kotti includes the following third party modules:

• jquery.toastmessage by Daniel Bremer-Tonn, available under the Apache License Version 2.0

Thanks

Kotti thanks the University of Coimbra for their involvement and support.

History

0.1a8

• Add slots/portlets through which thirdy party packages can extend Kotti and put fragments of markup into the site’s HTML. Look at the kotti.views.slots for documentation.

• Enable AJAX forms in the Move screen and add Growl-like notification for messages.

• Fixed silly packaging problem with 0.1a7 release. Install would fail with README.rst: No such file or directory before.

• Fix bug with TinyMCE which would trigger “Are you sure you want to leave this page?” all the time.

0.1a7

• Add a user management screen for adding new users and assigning them to roles and groups globally. Allow new users to set their own passwords.

• Add “forgotten password” button to login screen; sends an e-mail with a reset password link.

• Add a simple user preferences screen.

• Ditch ‘kotti.configuration’ in favour of ‘pyramid.settings’.

0.1a6

• Kotti now has a 100% automated test coverage, testing a total of some 950 lines of code.

• Add a user dropdown menu in the edit interface that display’s the currently logged in user’s name and contains links to Site Setup (in the works) and Logout.

• Require Chameleon < 1.2.999 since higher version cause compatibility issues with pyramid and deform.

• Implemented a simple events system in kotti.events that’s akin to Zope3’s object events. See the module for documentation and examples.

• Add a request_cache cache decorator in kotti.util for memoizing function results in the current request. Cut down number of recursive queries run by kotti.security.list_groups_ext.

0.1a5

• Add sharing screen.

  This allows you to set roles for groups and users on individual folders. This also considers roles that are inherited from higher up in the hierarchy, and those that are inherited from groups that the user belongs to.

• Refined available system roles in kotti.security.ROLES. We now have:

  • Viewer: view

  • Editor: view, add, edit

  • Owner: view, add, edit, manage

  • Admin: all permissions

0.1a4

• Added login form.

  With the development profile in development.ini, log in with user ‘admin’ and password ‘qwerty’. User management and sharing tab is a TODO.

• Add a default user database implementation in kotti.security.Principals.

  Override with kotti.principals configuration setting.

• Add inheritbale, nested groups support.

  Groups are stored in Node.__groups__. The API is kotti.security.list_groups and kotti.security.set_groups.