##// END OF EJS Templates
filter out repo groups choices to only ones that you have write+ access to. Before it was read+ access and you got proper...
filter out repo groups choices to only ones that you have write+ access to. Before it was read+ access and you got proper error saying that you don't have write permissions to group to create repo in. Filtering out the read groups is less confusing for users. ref #730

File last commit:

r3224:8b8edfc2 beta
r3239:a9565b8b beta
Show More
installation.rst
133 lines | 4.2 KiB | text/x-rst | RstLexer
/ docs / installation.rst
updated docs, added sphinx build
r568 .. _installation:
docs
r2095 ============
updated docs, added sphinx build
r568 Installation
============
whitespace cleanup
r3224 ``RhodeCode`` is written entirely in Python. Before posting any issues make
sure, your not missing any system libraries and using right version of
added info about minimum client version for rhodecode. Fixes #224
r1439 libraries required by RhodeCode. There's also restriction in terms of mercurial
clients. Minimal version of hg client known working fine with RhodeCode is
**1.6**. If you're using older client, please upgrade.
updated docs, added sphinx build
r568
H Waldo G
fleshing out the Upgrade doc, and modified the references to Cheeseshop in the Install doc
r2806 Installing RhodeCode from PyPI (aka "Cheeseshop")
-------------------------------------------------
updated docs, added sphinx build
r568
merge docs in beta with those corrected by Jason Harris
r1092 Rhodecode requires python version 2.5 or higher.
The easiest way to install ``rhodecode`` is to run::
updated docs, added sphinx build
r568
docs and readme update
r1062 easy_install rhodecode
updated docs, added sphinx build
r568
Or::
docs and readme update
r1062 pip install rhodecode
updated docs, added sphinx build
r568
merge docs in beta with those corrected by Jason Harris
r1092 If you prefer to install RhodeCode manually simply grab latest release from
fix doc typo
r2351 http://pypi.python.org/pypi/RhodeCode, decompress the archive and run::
updated docs, added sphinx build
r568
docs and readme update
r1062 python setup.py install
updated docs, added sphinx build
r568
added detailed step-by-step installation instruction for windows
r2358 Step by step installation example for Windows
---------------------------------------------
updated docs, added sphinx build
r568
added detailed step-by-step installation instruction for windows
r2358 :ref:`installation_win`
Step by step installation example for Linux
-------------------------------------------
updated docs, added sphinx build
r568
small docs updates
r1309 For installing RhodeCode i highly recommend using separate virtualenv_. This
way many required by RhodeCode libraries will remain sandboxed from your main
whitespace cleanup
r3224 python and making things less problematic when doing system python updates.
small docs updates
r1309
added my gist script for another detailed installation instructions
r3169 Alternative very detailed installation instructions for Ubuntu Server with
celery, indexer and daemon scripts: https://gist.github.com/4546398
whitespace cleanup
r3224 - Assuming you have installed virtualenv_ create a new virtual environment
using virtualenv command::
more docs update
r572
changed /var/www to /opt as example in installation, it's just a better example.
r2650 virtualenv --no-site-packages /opt/rhodecode-venv
more docs update
r572
merge docs in beta with those corrected by Jason Harris
r1092
.. note:: Using ``--no-site-packages`` when generating your
virtualenv is **very important**. This flag provides the necessary
isolation for running the set of packages required by
RhodeCode. If you do not specify ``--no-site-packages``,
it's possible that RhodeCode will not install properly into
the virtualenv, or, even if it does, may not run properly,
depending on the packages you've already got installed into your
Python's "main" site-packages dir.
whitespace cleanup
r3224 - this will install new virtualenv_ into `/opt/rhodecode-venv`.
merge docs in beta with those corrected by Jason Harris
r1092 - Activate the virtualenv_ by running::
more docs update
r572
changed /var/www to /opt as example in installation, it's just a better example.
r2650 source /opt/rhodecode-venv/bin/activate
merge docs in beta with those corrected by Jason Harris
r1092
.. note:: If you're using UNIX, *do not* use ``sudo`` to run the
``virtualenv`` script. It's perfectly acceptable (and desirable)
to create a virtualenv as a normal user.
whitespace cleanup
r3224
- Make a folder for rhodecode data files, and configuration somewhere on the
small docs updates
r1309 filesystem. For example::
more docs update
r572
changed /var/www to /opt as example in installation, it's just a better example.
r2650 mkdir /opt/rhodecode
whitespace cleanup
r3224
small docs updates
r1309 - Go into the created directory run this command to install rhodecode::
more docs update
r572
small docs updates
r1309 easy_install rhodecode
whitespace cleanup
r3224
small docs updates
r1309 or::
more docs update
r572
whitespace cleanup
r3224 pip install rhodecode
- This will install rhodecode together with pylons and all other required
small docs updates
r1309 python libraries into activated virtualenv
more docs update
r572
cleaned installation docs a little
r855 Requirements for Celery (optional)
----------------------------------
small docs updates
r1309 In order to gain maximum performance
whitespace cleanup
r3224 there are some third-party you must install. When RhodeCode is used
small docs updates
r1309 together with celery you have to install some kind of message broker,
recommended one is rabbitmq_ to make the async tasks work.
Of course RhodeCode works in sync mode also and then you do not have to install
whitespace cleanup
r3224 any third party applications. However, using Celery_ will give you a large
speed improvement when using many big repositories. If you plan to use
RhodeCode for say 7 to 10 repositories, RhodeCode will perform perfectly well
small docs updates
r1309 without celery running.
whitespace cleanup
r3224
If you make the decision to run RhodeCode with celery make sure you run
celeryd using paster and message broker together with the application.
small docs updates
r1309
cleaned installation docs a little
r855 .. note::
Installing message broker and using celery is optional, RhodeCode will
merge docs in beta with those corrected by Jason Harris
r1092 work perfectly fine without them.
cleaned installation docs a little
r855
whitespace cleanup
r3224 **Message Broker**
cleaned installation docs a little
r855
- preferred is `RabbitMq <http://www.rabbitmq.com/>`_
merge docs in beta with those corrected by Jason Harris
r1092 - A possible alternative is `Redis <http://code.google.com/p/redis/>`_
cleaned installation docs a little
r855
whitespace cleanup
r3224 For installation instructions you can visit:
merge docs in beta with those corrected by Jason Harris
r1092 http://ask.github.com/celery/getting-started/index.html.
This is a very nice tutorial on how to start using celery_ with rabbitmq_
cleaned installation docs a little
r855
more docs update
r572
You can now proceed to :ref:`setup`
cleaned installation docs a little
r855 -----------------------------------
updated docs, added sphinx build
r568
whitespace cleanup
r3224 .. _virtualenv: http://pypi.python.org/pypi/virtualenv
more docs update
r572 .. _python: http://www.python.org/
.. _mercurial: http://mercurial.selenic.com/
.. _celery: http://celeryproject.org/
H Waldo G
fleshing out the Upgrade doc, and modified the references to Cheeseshop in the Install doc
r2806 .. _rabbitmq: http://www.rabbitmq.com/