The API, BackOffice, Storefront, and Nebulizer for IndexTank
Pull request Compare This branch is 23 commits behind linkedin:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
api Key generation now uses config file for better security Dec 22, 2011
backoffice Key generation now uses config file for better security Dec 22, 2011
demo_index
gen-py
nebu
storefront Key generation now uses config file for better security Dec 22, 2011
LICENSE
README.md Update README.md Dec 26, 2011

README.md

About IndexTank Service

IndexTank Service (http://indextank.com) 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 (https://github.com/linkedin/indextank-engine) binary.

Homepage:

Find out more about at: TBD

License:

Apache Public License (APL) 2.0

Components:

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

Dependencies:

Getting started:

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

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).

Backoffice

Django application that allows manual administration.

Storefront

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

Nebu

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