Support

Commercial support (installation, hosting, customization, training) is offered
by the Liquid Democracy e.V. - you can reach us at info(at)liqd(dot)de.

Adhocracy installation

Adhocracy makes heavy use of
buildout, a Python build
tool. It downloads, configures and builds nearly all dependencies to
create a repeatable and isolated environment. In addition it sets up the
supervisord service manager, which allows to easily start and stop the
services which Adhocracy needs to run:

adhocracy (http server that runs Adhocracy with Spawning/WSGI)

adhocracy_worker (background queue processing)

solr (searching)

memcached (key-value cache)

redis (internal messaging queue)

Adhocracy is known to work on all modern Linux distributions, but should
also run on OS X and FreeBSD with minor modifications.

There are two supported ways of installing Adhocracy:

A fully automatic installation, which downloads and sets up
everything, is available for Debian, Ubuntu and Arch Linux. This is
basically a wrapper around buildout.

The manual installation, which directly uses the buildout commands.

Both are described in the following.

Automatic installation on debian, Ubuntu or Arch Linux with build.sh

On debian, Ubuntu, or Arch you can simply execute the following in a
terminal:

2.1.1 (2014-02-04)

This is a patch release which actually allows upgrading to 2.1.x with the
instructions given below in the 2.1.0 sections. When upgrading from 2.0.0
to 2.1.x, simply jump to 2.1.1 directly by doing git checkout 2.1.1.

Changes:

Make sure the src/adhocracy/alembic/versions directory actually exists in
order to make bin/paster setup-app … work.

Update some dependencies.

Fix search box placeholder for instances with quotes in title. (#740)

2.1.0 (2014-02-04)

This upgrade only splits the SQLAlchemy-related changes from the 2.0.0 release
in order to make sure all migrations are executed and the database remains in
a consistent state.

Changes:

Update SQLAlchemy from 0.7.10 to 0.9.1.

Switch from sqlalchemy-migrate to Alembic. (#219)

Upgrade instructions:

If you haven’t upgraded for a long time (say six months or more), it’s best to
delete parts, eggs, python/python-2.7 and python/parts
directories and rebuild everything according to INSTALLATION.rst.

In any case, don’t upgrade to 2.1.0 in one go, but upgrade to 2.0.0 first by
running:

This makes sure the remaining sqlalchemy-migration based migrations are
executed in the first step, and the Alembic environment is initialized properly
in the second step.

2.0.0 (2014-02-03)

Start doing releases using semantic versioning (#77). This release’s
changelog contains many changes from the past two years, but rather
incomplete.

Allow to list norms in a tiled fashion. (#714)

Add container pages. These special norms act as containers of other norms.
(#709)

Proposal descriptions can now be shown directly in proposal lists. (#733)

It is now possible to translate the English source strings through Transifex
as it is done in all other languages. In Transifex, the en_GB language
is used as the “translated” English langauage in contrast to the “source”
English langauage and doesn’t imply that british English shall be used.
(#102)

Replace RabbitMQ/amqp with redis/rq (#220). This means that you have to
provide a working redis instance if you want to use asyncronous
jobs (highly recommended in production).
The background process that processes the jobs is renamed from
‘background’ to ‘worker’. You can call it with
bin/paster –plugin=adhocracy worker -c etc/adhocracy.ini

Configuration changes:

dropped: adhocracy.amqp.* settings are not required anymore.

new: adhocracy.redis.host: An IP address redis can bind to
(not a hostname!)

new: adhocracy.redis.port: The port redis will open

new: adhocracy.redis.queue: The queue name

Mandatory email validation. (#142)

Invisible badges. (#116)

Instance-based user rating sorting. (#190)

Disallow multiple usernames with only case differences. (#171)

Dashboard style instance overview page. (#90)

Support path based instances instead of subdomain only. (#62)

Feedback instance pull in form. (#88)

Lamson mailserver dummy for development purposes.

Added facet search to the instance listing. The listing is based on solr now,
please reindex. [joka]

Instances can have badges now. To create instance badges use the
site-administration -> badges form. To assign badges use the
instance listing. [joka]

New config option “adhocracy.registration.email.blacklist” that
accepts a whitespace seperated list of email address and
blocks registrations with those. Dots will be stripped before
the test (to catch gmail addresses where dots are ignored by gmail).
[csenger]

Permission change: When we test the ‘norm.create’ permission
(permission to create Norms/Topics/Themen we do no longer
restrict it to users who also have ‘instance.admin’. The main
permission we check now is ‘page.create’.

Give the users the option to permanently activate the twitter,
facebook or google+ buttons. Save the setting in a wildcard
subdomain cookie so it is valid across all instances.

This requires a updated js.socialshareprivacy to work with
our auth cookie. [csenger]

Add the possibility to overwrite templates in <adhocracy.site>/templates
directory (like it’s possible for static resources and static pages already.
New templates there need a server restart to be picked up.
[csenger]

Deliver (almost) all resources with fanstatic. [csenger]

Delegateables can have category badges. [joka]

Instances can have badges, they are only valid inside that instance. [joka]