Tiki Suite 2013 deployment plan

This has been done, was a success, and we make adjustments, and is available from Tiki Suite Demo and of course: Tiki Suite Install


A plan to deploy Tiki Suite "as is" for a company of 10-20 employees. Document everything along the way, and gather experience on interoperability and additional components. This company will dogfood internally, with the goal of offering as a service to their customers.


  • October-November 2013


  • How many employees in the test phase?
    • Will this be their main mail account and we transfer mails or we do this under a new domain, and this is progressive?


Absolute minimum

Install and configure the base packages "as-is", without 3rd party packages. We configure all three systems with built-in features and configure them to all work nicely together. We train users on these tools for their main use cases.

These three packages have so many features, it's just insane :-)

They also manage internally the complexity of interoperability of a huge number of components, libraries, etc

We need 4 root servers (virtual servers are fine) on which we will install

  1. ClearOS + Tiki + Zarafa
  2. sipXecs
  3. BigBlueButton
  4. Test a virtualization solution

Basic integration to work: use LDAP

Make "rooms" available for team collaboration / project management which offers the features of Tiki / BigBlueButton / etc.

Low-hanging fruit

Here, we implement desired things that are not part of the base packages, but have already been implemented by others, following and improving the documentation. We interact with the various projects and think ahead for the new possibilities offered by HTML5 (like WebRTC, etc.). By the end of this phase, we'll have a clear idea of our options for the road ahead.

In this phase, no development, only configuration and training.


"The default groupware and mail solution is now based on Zarafa technology."


Better integration between Tiki and ClearOS

Under the hood, a new engine for supporting web applications is also in development.


Once we have experimented enough with the various components, we can start improving interoperabiliy, adding missing features, and thinking of large scale deployment and maintenance

Page last modified on Saturday 31 May 2014 18:07:42 GMT-0000

Upcoming Events

No records to display