.nf { color: #990000; font-weight: bold } /* Name.Function */

.nn { color: #555555 } /* Name.Namespace */

.nt { color: #000080 } /* Name.Tag */

.nv { color: purple } /* Name.Variable */

.ow { font-weight: bold } /* Operator.Word */

.mf { color: #009999 } /* Literal.Number.Float */

.mh { color: #009999 } /* Literal.Number.Hex */

.mi { color: #009999 } /* Literal.Number.Integer */

.mo { color: #009999 } /* Literal.Number.Oct */

.sb { color: #bb8844 } /* Literal.String.Backtick */

.sc { color: #bb8844 } /* Literal.String.Char */

.sd { color: #bb8844 } /* Literal.String.Doc */

.s2 { color: #bb8844 } /* Literal.String.Double */

.se { color: #bb8844 } /* Literal.String.Escape */

.sh { color: #bb8844 } /* Literal.String.Heredoc */

.si { color: #bb8844 } /* Literal.String.Interpol */

.sx { color: #bb8844 } /* Literal.String.Other */

.sr { color: #808000 } /* Literal.String.Regex */

.s1 { color: #bb8844 } /* Literal.String.Single */

.ss { color: #bb8844 } /* Literal.String.Symbol */

.bp { color: #999999 } /* Name.Builtin.Pseudo */

.vc { color: #ff99ff } /* Name.Variable.Class */

.vg { color: #ff99ff } /* Name.Variable.Global */

.vi { color: #ff99ff } /* Name.Variable.Instance */

    locking issues with sqlite, it's not recommended to use it for larger

    setup. Switching to mysql or postgres will result in a immediate

    performance increase.

3. Scale RhodeCode horizontally

    Scaling horizontally can give huge performance increase when dealing with

    large traffic (large amount of users, CI servers etc). RhodeCode can be

    scaled horizontally on one (recommended) or multiple machines. In order

    to scale horizontally you need to do the following:

    - each instance needs it's own .ini file and unique `instance_id` set in them

    - each instance `data` storage needs to be configured to be stored on a 

      shared disk storage, preferably together with repositories. This `data`

      dir contains template caches, sessions, whoosh index and it's used for

      tasks locking (so it's safe across multiple instances). Set the

      `cache_dir`, `index_dir`, `beaker.cache.data_dir`, `beaker.cache.lock_dir`

      variables in each .ini file to shared location across RhodeCode instances 

    - if celery is used each instance should run separate celery instance, but

      the message broken should be common to all of them (ex one rabbitmq

      shared server)    

    - load balance using round robin or ip hash, recommended is writing LB rules

      that will separate regular user traffic from automated processes like CI

      servers or build bots.

waitress==0.8.1

webob==1.0.8

Pylons==1.0.0

Beaker==1.6.4

WebHelpers==1.3

formencode==1.2.4

SQLAlchemy==0.7.8

Mako==0.7.2

pygments>=1.5

whoosh>=2.4.0,<2.5

celery>=2.2.5,<2.3

babel

python-dateutil>=1.5.0,<2.0.0

dulwich>=0.8.5,<0.9.0

markdown==2.1.1

docutils==0.8.1

simplejson==2.5.2

mock

py-bcrypt