The API, BackOffice, Storefront, and Nebulizer for IndexTank
Python JavaScript C Other
Latest commit 880c629 May 18, 2013 @dbuthay dbuthay Merge pull request #9 from Digga/patch-1
removed misplaced quote in ul tag
Failed to load latest commit information.
backoffice fixed a few loose ends and added sample configuration files Jan 17, 2012
demo_index initial copy Dec 21, 2011
nebu - Changed mode to all service runs to be executable Feb 10, 2012
sample-config/etc Added api to hosts Feb 10, 2012
server_configurations/storage/etc/service - Changed mode to all service runs to be executable Feb 10, 2012
storage Fixing path to raw storage logs in backup script Feb 12, 2012
storefront removed misplaced quote in ul tag May 19, 2013
LICENSE initial copy Dec 21, 2011 updating readme. storefront is incompatible with django 1.3.x Jan 16, 2012

About IndexTank Service

IndexTank Service ( contains the source code for implementing the Search-as-a-Service platform. It contains the components that allow managing user accounts, server instances (worker) and index instances (deploy); it depends on IndexTank Engine ( binary.


Find out more about at: TBD


Apache Public License (APL) 2.0


  1. API
  2. Backoffice
  3. Storefront
  4. Nebu


Getting started:

  1. Create the database schema (python syncdb).
  2. Create an account.
  3. Start an index instance (IndexTank Engine).
  4. Start API.


Django application implementing the REST JSON API, enables index management per account, indexing functions and search. Interacts via Thrift with specific index instances (deploy).


Django application that allows manual administration.


Django application with the service web, contains the user registration form (allows creating accounts).


Index, deploy & worker manager. A worker (server instance) may contain a deploy (index instance) or many.