Version 1 (modified by jbenito, 4 years ago) (diff)


1. Extra Apache Configuration

Enabling gzip compression

To turn this feature on, just add the following code to the apache configuration file:

AddOutputFilterByType DEFLATE text/html text/plain text/xml 

In this case, it will compress html, xml and plain text. If you want to compress more types just add them.

You may use this code in your .htaccess file as well, just choose between one of them. Take in account that the DEFLATE filter is always inserted after RESOURCE filters like PHP or SSI. It never touches internal subrequests.

For further information:
To check whether gzip compression is working properly:

  • In your browser: Information -> View Document Size
  • View the headers: If you can find a line that says “Content-encoding: gzip” that means that this feature is working correctly.

2. Event Styles

Meeting and lecture displays, as well as conferences "Timetable view" are created by a XSL transformation produced from the Indico event XML export. The stylesheets applied to this XML are .xsl files and can be found into the MaKaC/webinterface/stylesheets directory in the Indico package (and in /where/is/python/lib/site-packages/MaKaC/webinterface/stylesheets directory once installed).

Here some of the basic rules if you want to add your own style (XSL) to the events:

  • Each .xsl must have its own .css file named after itself (eg. there must be a standard.xsl file and a standard.css file)
  • In order to add a new style, create an XSL file and its CSS, and add the files to the above mentioned directory.
  • Your style should then appear in the list of available styles:
  • From the previous link, you can choose to add it for lectures, meetings and/or conferences.

3. Adding a Search Engine to Indico

Indico does not have a built-in search engine but can easily export all of its public data to any external search engine using an OAI gateway. You can then setup search forms in Indico pages which will redirect the request to the external search engine for a transparent integration. If you want to see a demo, try ours

  • Step 1: which external search engine to choose
    • You should select a search engine which complies to your needs but more important and mandatory which has OAI harvesting capabilities. CERN currently uses Invenio as its search engine
    • Make sure an Indico plugin exists for the search engine you selected (or write one). Currently Indico has a plugin for Invenio only
  • Step 2: setup Indico OAI-gateway
    • It's available by default when installing Indico
  • Step 3: setup the external search engine to regularly harvest Indico and to correctly serve the information to users.
    • This point is outside the scope of this tutorial
  • Step 4: enable Indico search boxes and redirect the requests to the external engine
    • edit the "indicoSearch" section of Indico's config.xml
IndicoSearchServer =
indicoSearchClass =

3. Task Daemon

Indico can run many tasks off-line and in order to do that it uses a "task daemon". You should enable it if you want Indico to send alerts, to show statistics or to run any other off-line tasks. In order to enable it, one just need to run this command:

$ taskDaemon start