Rename some strings examples and commands in documentation

README.rst

@@ -25,15 +25,15 b' Installation'
 ------------
 Stable releases of RhodeCode are best installed via::
 
-    easy_install rhodecode
+    easy_install kallithea
 
 Or::
 
-    pip install rhodecode
+    pip install kallithea
 
 Detailed instructions and links may be found on the Installation page.
 
-Please visit http://packages.python.org/RhodeCode/installation.html for
+Please visit http://packages.python.org/Kallithea/installation.html for
 more details
 
 
@@ -138,8 +138,8 b' Online documentation'
 --------------------
 
 Online documentation for the current version of RhodeCode is available at
- - http://packages.python.org/RhodeCode/
- - http://rhodecode.readthedocs.org/en/latest/index.html
+ - http://packages.python.org/Kallithea/
+ - http://kallithea.readthedocs.org/
 
 You may also build the documentation for yourself - go into ``docs/`` and run::
 

docs/Makefile

@@ -72,17 +72,17 b' qthelp:'
 	@echo
 	@echo "Build finished; now you can run "qcollectiongenerator" with the" \
 	      ".qhcp project file in $(BUILDDIR)/qthelp, like this:"
-	@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/RhodeCode.qhcp"
+	@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/Kallithea.qhcp"
 	@echo "To view the help file:"
-	@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/RhodeCode.qhc"
+	@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/Kallithea.qhc"
 
 devhelp:
 	$(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
 	@echo
 	@echo "Build finished."
 	@echo "To view the help file:"
-	@echo "# mkdir -p $$HOME/.local/share/devhelp/RhodeCode"
-	@echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/RhodeCode"
+	@echo "# mkdir -p $$HOME/.local/share/devhelp/Kallithea"
+	@echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/Kallithea"
 	@echo "# devhelp"
 
 epub:

docs/api/api.rst

@@ -5,15 +5,15 b' API'
 ===
 
 
-Starting from RhodeCode version 1.2 a simple API was implemented.
+Starting from Kallithea version 1.2 a simple API was implemented.
 There's a single schema for calling all api methods. API is implemented
-with JSON protocol both ways. An url to send API request to RhodeCode is
+with JSON protocol both ways. An url to send API request to Kallithea is
 <your_server>/_admin/api
 
 API ACCESS FOR WEB VIEWS
 ++++++++++++++++++++++++
 
-API access can also be turned on for each web view in RhodeCode that is
+API access can also be turned on for each web view in Kallithea that is
 decorated with `@LoginRequired` decorator. To enable API access simple change
 the standard login decorator to `@LoginRequired(api_access=True)`.
 
@@ -21,7 +21,7 b' To make this operation easier, starting '
 of views that will have API access enabled. Simply edit `api_access_controllers_whitelist`
 option in your .ini file, and define views that should have API access enabled.
 Following example shows how to enable API access to patch/diff raw file and archive
-in RhodeCode::
+in Kallithea::
 
     api_access_controllers_whitelist =
         ChangesetController:changeset_patch,
@@ -30,7 +30,7 b' in RhodeCode::'
         FilesController:archivefile
 
 
-After this change, a rhodecode view can be accessed without login by adding a
+After this change, a Kallithea view can be accessed without login by adding a
 GET parameter `?api_key=<api_key>` to url. By default this is only
 enabled on RSS/ATOM feed views. Exposing raw diffs is a good way to integrate with
 3rd party services like code review, or build farms that could download archives.
@@ -62,7 +62,7 b' Simply provide'
     api_key can be found in your user account page
 
 
-RhodeCode API will return always a JSON-RPC response::
+Kallithea API will return always a JSON-RPC response::
 
     {
         "id":<id>, # matching id sent by request
@@ -78,8 +78,8 b' and result will be null.'
 API CLIENT
 ++++++++++
 
-From version 1.4 RhodeCode adds a script that allows to easily
-communicate with API. After installing RhodeCode a `kallithea-api` script
+From version 1.4 Kallithea adds a script that allows to easily
+communicate with API. After installing Kallithea a `kallithea-api` script
 will be available.
 
 To get started quickly simply run::
@@ -96,7 +96,7 b' after that simply run any api command fo'
  kallithea-api get_repo
 
  calling {"api_key": "<apikey>", "id": 75, "args": {}, "method": "get_repo"} to http://127.0.0.1:5000
- rhodecode said:
+ Kallithea said:
  {'error': 'Missing non optional `repoid` arg in JSON DATA',
   'id': 75,
   'result': None}
@@ -105,10 +105,10 b' Ups looks like we forgot to add an argum'
 
 Let's try again now giving the repoid as parameters::
 
-    kallithea-api get_repo repoid:rhodecode
+    kallithea-api get_repo repoid:myrepo
 
-    calling {"api_key": "<apikey>", "id": 39, "args": {"repoid": "rhodecode"}, "method": "get_repo"} to http://127.0.0.1:5000
-    rhodecode said:
+    calling {"api_key": "<apikey>", "id": 39, "args": {"repoid": "myrepo"}, "method": "get_repo"} to http://127.0.0.1:5000
+    Kallithea said:
     {'error': None,
      'id': 39,
      'result': <json data...>}
@@ -146,7 +146,7 b' rescan_repos'
 ------------
 
 Dispatch rescan repositories action. If remove_obsolete is set
-RhodeCode will delete repos that are in database but not in the filesystem.
+Kallithea will delete repos that are in database but not in the filesystem.
 This command can be executed only using api_key belonging to user with admin
 rights.
 
@@ -225,7 +225,7 b' OUTPUT::'
 show_ip
 -------
 
-Shows IP address as seen from RhodeCode server, together with all
+Shows IP address as seen from Kallithea server, together with all
 defined IP addresses for given user.
 This command can be executed only using api_key belonging to user with admin
 rights.

docs/conf.py

@@ -1,6 +1,6 b''
 # -*- coding: utf-8 -*-
 #
-# RhodeCode documentation build configuration file, created by
+# Kallithea documentation build configuration file, created by
 # sphinx-quickstart on Sun Oct 10 16:46:37 2010.
 #
 # This file is execfile()d with the current directory set to its containing dir.
@@ -44,7 +44,7 b" source_suffix = '.rst'"
 master_doc = 'index'
 
 # General information about the project.
-project = u'RhodeCode'
+project = u'Kallithea'
 copyright = u'%s, Marcin Kuzminski' % (datetime.datetime.now().year)
 
 # The version info for the project you're documenting, acts as replacement for
@@ -171,7 +171,7 b" html_theme_path = ['theme']"
 #html_file_suffix = None
 
 # Output file base name for HTML help builder.
-htmlhelp_basename = 'RhodeCodedoc'
+htmlhelp_basename = 'Kallithea-docs'
 
 
 # -- Options for LaTeX output --------------------------------------------------
@@ -185,7 +185,7 b" htmlhelp_basename = 'RhodeCodedoc'"
 # Grouping the document tree into LaTeX files. List of tuples
 # (source start file, target name, title, author, documentclass [howto/manual]).
 latex_documents = [
-  ('index', 'RhodeCode.tex', u'RhodeCode Documentation',
+  ('index', 'Kallithea.tex', u'Kallithea Documentation',
    u'Marcin Kuzminski', 'manual'),
 ]
 
@@ -218,7 +218,7 b' latex_documents = ['
 # One entry per manual page. List of tuples
 # (source start file, name, description, authors, manual section).
 man_pages = [
-    ('index', 'kallithea', u'RhodeCode Documentation',
+    ('index', 'kallithea', u'Kallithea Documentation',
      [u'Marcin Kuzminski'], 1)
 ]
 

docs/contributing.rst

@@ -1,26 +1,26 b''
 .. _contributing:
 
 =========================
-Contributing to RhodeCode
+Contributing to Kallithea
 =========================
 
-If you would like to contribute to RhodeCode, please contact me, any help is
+If you would like to contribute to Kallithea, please contact us, any help is
 greatly appreciated!
 
 Could I request that you make your source contributions by first forking the
-RhodeCode repository on bitbucket_
+Kallithea repository on bitbucket_
 https://bitbucket.org/conservancy/kallithea and then make your changes to
 your forked repository. Please post all fixes into **dev** bookmark since your
 change might be already fixed there and i try to merge all fixes from dev into
 stable, and not the other way. Finally, when you are finished with your changes,
-please send me a pull request.
+please send us a pull request.
 
-To run RhodeCode in a development version you always need to install the latest
-required libs. Simply clone rhodecode and switch to beta branch::
+To run Kallithea in a development version you always need to install the latest
+required libs. Simply clone Kallithea and switch to beta branch::
 
     hg clone https://kallithea-scm.org/repos/kallithea
 
-after downloading/pulling RhodeCode make sure you run::
+after downloading/pulling Kallithea make sure you run::
 
     python setup.py develop
 
@@ -46,8 +46,6 b" There's a special set of tests for push/"
 
 
 | Thank you for any contributions!
-|  Marcin
-
 
 
 .. _bitbucket: http://bitbucket.org/

docs/installation.rst

@@ -4,28 +4,28 b''
 Installation
 ============
 
-``RhodeCode`` is written entirely in Python. Before posting any issues make
+``Kallithea`` is written entirely in Python. Before posting any issues make
 sure, your not missing any system libraries and using right version of
-libraries required by RhodeCode. There's also restriction in terms of mercurial
-clients. Minimal version of hg client known working fine with RhodeCode is
+libraries required by Kallithea. There's also restriction in terms of mercurial
+clients. Minimal version of hg client known working fine with Kallithea is
 **1.6**. If you're using older client, please upgrade.
 
 
-Installing RhodeCode from PyPI (aka "Cheeseshop")
+Installing Kallithea from PyPI (aka "Cheeseshop")
 -------------------------------------------------
 
-Rhodecode requires python version 2.5 or higher.
+Kallithea requires python version 2.5 or higher.
 
-The easiest way to install ``rhodecode`` is to run::
+The easiest way to install ``kallithea`` is to run::
 
-    easy_install rhodecode
+    easy_install kallithea
 
 Or::
 
-    pip install rhodecode
+    pip install kallithea
 
-If you prefer to install RhodeCode manually simply grab latest release from
-http://pypi.python.org/pypi/RhodeCode, decompress the archive and run::
+If you prefer to install Kallithea manually simply grab latest release from
+http://pypi.python.org/pypi/Kallithea, decompress the archive and run::
 
     python setup.py install
 
@@ -39,8 +39,8 b' Step by step installation example for Li'
 -------------------------------------------
 
 
-For installing RhodeCode i highly recommend using separate virtualenv_. This
-way many required by RhodeCode libraries will remain sandboxed from your main
+For installing Kallithea i highly recommend using separate virtualenv_. This
+way many required by Kallithea libraries will remain sandboxed from your main
 python and making things less problematic when doing system python updates.
 
 Alternative very detailed installation instructions for Ubuntu Server with
@@ -50,64 +50,64 b' celery, indexer and daemon scripts: http'
 - Assuming you have installed virtualenv_ create a new virtual environment
   using virtualenv command::
 
-    virtualenv --no-site-packages /opt/rhodecode-venv
+    virtualenv --no-site-packages /opt/kallithea-venv
 
 
 .. 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
+   Kallithea.  If you do not specify ``--no-site-packages``,
+   it's possible that Kallithea 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.
 
 
-- this will install new virtualenv_ into `/opt/rhodecode-venv`.
+- this will install new virtualenv_ into `/opt/kallithea-venv`.
 - Activate the virtualenv_ by running::
 
-    source /opt/rhodecode-venv/bin/activate
+    source /opt/kallithea-venv/bin/activate
 
 .. 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.
 
-- Make a folder for rhodecode data files, and configuration somewhere on the
+- Make a folder for Kallithea data files, and configuration somewhere on the
   filesystem. For example::
 
-    mkdir /opt/rhodecode
+    mkdir /opt/kallithea
 
 
-- Go into the created directory run this command to install rhodecode::
+- Go into the created directory run this command to install kallithea::
 
-    easy_install rhodecode
+    easy_install kallithea
 
   or::
 
-    pip install rhodecode
+    pip install kallithea
 
-- This will install rhodecode together with pylons and all other required
+- This will install Kallithea together with pylons and all other required
   python libraries into activated virtualenv
 
 Requirements for Celery (optional)
 ----------------------------------
 
 In order to gain maximum performance
-there are some third-party you must install. When RhodeCode is used
+there are some third-party you must install. When Kallithea is used
 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
+Of course Kallithea works in sync mode also and then you do not have to install
 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
+Kallithea for say 7 to 10 repositories, Kallithea will perform perfectly well
 without celery running.
 
-If you make the decision to run RhodeCode with celery make sure you run
+If you make the decision to run Kallithea with celery make sure you run
 celeryd using paster and message broker together with the application.
 
 .. note::
-   Installing message broker and using celery is optional, RhodeCode will
+   Installing message broker and using celery is optional, Kallithea will
    work perfectly fine without them.
 
 

docs/installation_win.rst

@@ -5,7 +5,7 b' Step by step Installation for Windows'
 =====================================
 
 
-RhodeCode step-by-step install Guide for Windows
+Kallithea step-by-step install Guide for Windows
 
 Target OS: Windows XP SP3 32bit English (Clean installation)
 + All Windows Updates until 24-may-2012
@@ -121,22 +121,22 b' that came preinstalled in Vista/7 and ca'
   Typically: C:\\Python27
 
 
-Step5 - RhodeCode folder structure
+Step5 - Kallithea folder structure
 ----------------------------------
 
-Create a RhodeCode folder structure
+Create a Kallithea folder structure
 
-This is only a example to install RhodeCode, you can of course change
+This is only a example to install Kallithea, you can of course change
 it. However, this guide will follow the proposed structure, so please
 later adapt the paths if you change them. My recommendation is to use
 folders with NO SPACES. But you can try if you are brave...
 
 Create the following folder structure::
 
-  C:\RhodeCode
-  C:\RhodeCode\Bin
-  C:\RhodeCode\Env
-  C:\RhodeCode\Repos
+  C:\Kallithea
+  C:\Kallithea\Bin
+  C:\Kallithea\Env
+  C:\Kallithea\Repos
 
 
 Step6 - Install virtualenv
@@ -146,24 +146,24 b' Install Virtual Env for Python'
 
 Navigate to: http://www.virtualenv.org/en/latest/index.html#installation
 Right click on "virtualenv.py" file and choose "Save link as...".
-Download to C:\\RhodeCode (or whatever you want)
+Download to C:\\Kallithea (or whatever you want)
 (the file is located at
 https://raw.github.com/pypa/virtualenv/master/virtualenv.py)
 
-Create a virtual Python environment in C:\\RhodeCode\\Env (or similar). To
+Create a virtual Python environment in C:\\Kallithea\\Env (or similar). To
 do so, open a CMD (Python Path should be included in Step3), navigate
 where you downloaded "virtualenv.py", and write::
 
- python virtualenv.py C:\RhodeCode\Env
+ python virtualenv.py C:\Kallithea\Env
 
 (--no-site-packages is now the default behaviour of virtualenv, no need
 to include it)
 
 
-Step7 - Install RhodeCode
+Step7 - Install Kallithea
 -------------------------
 
-Finally, install RhodeCode
+Finally, install Kallithea
 
 Close previously opened command prompt/s, and open a Visual Studio 2008
 Command Prompt (**IMPORTANT!!**). To do so, go to Start Menu, and then open
@@ -186,31 +186,31 b' to::'
 
 In that CMD (loaded with VS2008 PATHs) type::
 
-  cd C:\RhodeCode\Env\Scripts (or similar)
+  cd C:\Kallithea\Env\Scripts (or similar)
   activate
 
-The prompt will change into "(Env) C:\\RhodeCode\\Env\\Scripts" or similar
+The prompt will change into "(Env) C:\\Kallithea\\Env\\Scripts" or similar
 (depending of your folder structure). Then type::
 
- pip install rhodecode
+ pip install kallithea
 
 (long step, please wait until fully complete)
 
 Some warnings will appear, don't worry as they are normal.
 
 
-Step8 - Configuring RhodeCode
+Step8 - Configuring Kallithea
 -----------------------------
 
 
-steps taken from http://packages.python.org/RhodeCode/setup.html
+steps taken from http://packages.python.org/Kallithea/setup.html
 
 You have to use the same Visual Studio 2008 command prompt as Step7, so
 if you closed it reopen it following the same commands (including the
 "activate" one). When ready, just type::
 
-  cd C:\RhodeCode\Bin
-  paster make-config RhodeCode production.ini
+  cd C:\Kallithea\Bin
+  paster make-config Kallithea production.ini
 
 Then, you must edit production.ini to fit your needs (ip address, ip
 port, mail settings, database, whatever). I recommend using NotePad++
@@ -224,11 +224,11 b' your edits (if any), in the previous Com'
  paster setup-db production.ini
 
 (this time a NEW database will be installed, you must follow a different
-step to later UPGRADE to a newer RhodeCode version)
+step to later UPGRADE to a newer Kallithea version)
 
 The script will ask you for confirmation about creating a NEW database,
 answer yes (y)
-The script will ask you for repository path, answer C:\\RhodeCode\\Repos
+The script will ask you for repository path, answer C:\\Kallithea\\Repos
 (or similar)
 The script will ask you for admin username and password, answer "admin"
 + "123456" (or whatever you want)
@@ -239,11 +239,11 b' If you make some mistake and the script '
 it again.
 
 
-Step9 - Running RhodeCode
+Step9 - Running Kallithea
 -------------------------
 
 
-In the previous command prompt, being in the C:\\RhodeCode\\Bin folder,
+In the previous command prompt, being in the C:\\Kallithea\\Bin folder,
 just type::
 
  paster serve production.ini
@@ -261,7 +261,7 b' again. Don\'t forget the "http://" in Int'
 What this Guide does not cover:
 
 - Installing Celery
-- Running RhodeCode as Windows Service. You can investigate here:
+- Running Kallithea as Windows Service. You can investigate here:
 
   - http://pypi.python.org/pypi/wsgisvc
   - http://ryrobes.com/python/running-python-scripts-as-a-windows-service/
@@ -275,18 +275,18 b' What this Guide does not cover:'
 Upgrading
 =========
 
-Stop running RhodeCode
+Stop running Kallithea
 Open a CommandPrompt like in Step7 (VS2008 path + activate) and type::
 
- easy_install -U rhodecode
- cd \RhodeCode\Bin
+ easy_install -U kallithea
+ cd \Kallithea\Bin
 
 { backup your production.ini file now} ::
 
- paster make-config RhodeCode production.ini
+ paster make-config Kallithea production.ini
 
 (check changes and update your production.ini accordingly) ::
 
  paster upgrade-db production.ini (update database)
 
-Full steps in http://packages.python.org/RhodeCode/upgrade.html
+Full steps in http://packages.python.org/Kallithea/upgrade.html

docs/make.bat

@@ -88,9 +88,9 b' if "%1" == "qthelp" ('
 	echo.
 	echo.Build finished; now you can run "qcollectiongenerator" with the ^
 .qhcp project file in %BUILDDIR%/qthelp, like this:
-	echo.^> qcollectiongenerator %BUILDDIR%\qthelp\RhodeCode.qhcp
+	echo.^> qcollectiongenerator %BUILDDIR%\qthelp\Kallithea.qhcp
 	echo.To view the help file:
-	echo.^> assistant -collectionFile %BUILDDIR%\qthelp\RhodeCode.ghc
+	echo.^> assistant -collectionFile %BUILDDIR%\qthelp\Kallithea.ghc
 	goto end
 )
 

docs/setup.rst

@@ -5,31 +5,31 b' Setup'
 =====
 
 
-Setting up RhodeCode
+Setting up Kallithea
 --------------------
 
-First, you will need to create a RhodeCode configuration file. Run the
+First, you will need to create a Kallithea configuration file. Run the
 following command to do this::
 
-    paster make-config RhodeCode production.ini
+    paster make-config Kallithea production.ini
 
 - This will create the file `production.ini` in the current directory. This
-  configuration file contains the various settings for RhodeCode, e.g proxy
+  configuration file contains the various settings for Kallithea, e.g proxy
   port, email settings, usage of static files, cache, celery settings and
   logging.
 
 
-Next, you need to create the databases used by RhodeCode. I recommend that you
+Next, you need to create the databases used by Kallithea. I recommend that you
 use postgresql or sqlite (default). If you choose a database other than the
 default ensure you properly adjust the db url in your production.ini
-configuration file to use this other database. RhodeCode currently supports
+configuration file to use this other database. Kallithea currently supports
 postgresql, sqlite and mysql databases. Create the database by running
 the following command::
 
     paster setup-db production.ini
 
 This will prompt you for a "root" path. This "root" path is the location where
-RhodeCode will store all of its repositories on the current machine. After
+Kallithea will store all of its repositories on the current machine. After
 entering this "root" path ``setup-db`` will also prompt you for a username
 and password for the initial admin account which ``setup-db`` sets
 up for you.
@@ -42,19 +42,19 b' setup process can be fully automated, ex'
 - The ``setup-db`` command will create all of the needed tables and an
   admin account. When choosing a root path you can either use a new empty
   location, or a location which already contains existing repositories. If you
-  choose a location which contains existing repositories RhodeCode will simply
+  choose a location which contains existing repositories Kallithea will simply
   add all of the repositories at the chosen location to it's database.
   (Note: make sure you specify the correct path to the root).
 - Note: the given path for mercurial_ repositories **must** be write accessible
-  for the application. It's very important since the RhodeCode web interface
+  for the application. It's very important since the Kallithea web interface
   will work without write access, but when trying to do a push it will
   eventually fail with permission denied errors unless it has write access.
 
-You are now ready to use RhodeCode, to run it simply execute::
+You are now ready to use Kallithea, to run it simply execute::
 
     paster serve production.ini
 
-- This command runs the RhodeCode server. The web app should be available at the
+- This command runs the Kallithea server. The web app should be available at the
   127.0.0.1:5000. This ip and port is configurable via the production.ini
   file created in previous step
 - Use the admin account you created above when running ``setup-db``
@@ -64,7 +64,7 b' You are now ready to use RhodeCode, to r'
 - In the admin panel you can toggle ldap, anonymous, permissions settings. As
   well as edit more advanced options on users and repositories
 
-Optionally users can create `rcextensions` package that extends RhodeCode
+Optionally users can create `rcextensions` package that extends Kallithea
 functionality. To do this simply execute::
 
     paster make-rcext production.ini
@@ -77,36 +77,36 b' Please see the `__init__.py` file inside'
 for more details.
 
 
-Using RhodeCode with SSH
+Using Kallithea with SSH
 ------------------------
 
-RhodeCode currently only hosts repositories using http and https. (The addition
+Kallithea currently only hosts repositories using http and https. (The addition
 of ssh hosting is a planned future feature.) However you can easily use ssh in
-parallel with RhodeCode. (Repository access via ssh is a standard "out of
+parallel with Kallithea. (Repository access via ssh is a standard "out of
 the box" feature of mercurial_ and you can use this to access any of the
-repositories that RhodeCode is hosting. See PublishingRepositories_)
+repositories that Kallithea is hosting. See PublishingRepositories_)
 
-RhodeCode repository structures are kept in directories with the same name
+Kallithea repository structures are kept in directories with the same name
 as the project. When using repository groups, each group is a subdirectory.
 This allows you to easily use ssh for accessing repositories.
 
 In order to use ssh you need to make sure that your web-server and the users
 login accounts have the correct permissions set on the appropriate directories.
 (Note that these permissions are independent of any permissions you have set up
-using the RhodeCode web interface.)
+using the Kallithea web interface.)
 
-If your main directory (the same as set in RhodeCode settings) is for example
-set to **/home/hg** and the repository you are using is named `rhodecode`, then
+If your main directory (the same as set in Kallithea settings) is for example
+set to **/home/hg** and the repository you are using is named `kallithea`, then
 to clone via ssh you should run::
 
-    hg clone ssh://[e-mail]/home/hg/rhodecode
+    hg clone ssh://[e-mail]/home/hg/kallithea
 
 Using other external tools such as mercurial-server_ or using ssh key based
 authentication is fully supported.
 
 Note: In an advanced setup, in order for your ssh access to use the same
-permissions as set up via the RhodeCode web interface, you can create an
-authentication hook to connect to the rhodecode db and runs check functions for
+permissions as set up via the Kallithea web interface, you can create an
+authentication hook to connect to the Kallithea db and runs check functions for
 permissions against that.
 
 Setting up Whoosh full text search
@@ -116,7 +116,7 b' Starting from version 1.1 the whoosh ind'
 command ``make-index``. To use ``make-index`` you must specify the configuration
 file that stores the location of the index. You may specify the location of the
 repositories (`--repo-location`).  If not specified, this value is retrieved
-from the RhodeCode database.  This was required prior to 1.2.  Starting from
+from the Kallithea database.  This was required prior to 1.2.  Starting from
 version 1.2 it is also possible to specify a comma separated list of
 repositories (`--index-only`) to build index only on chooses repositories
 skipping any other found in repos location
@@ -135,14 +135,14 b' For a full index rebuild use::'
 
 building index just for chosen repositories is possible with such command::
 
- paster make-index production.ini --index-only=vcs,rhodecode
+ paster make-index production.ini --index-only=vcs,kallithea
 
 
 In order to do periodical index builds and keep your index always up to date.
 It's recommended to do a crontab entry for incremental indexing.
 An example entry might look like this::
 
-    /path/to/python/bin/paster make-index /path/to/rhodecode/production.ini
+    /path/to/python/bin/paster make-index /path/to/kallithea/production.ini
 
 When using incremental mode (the default) whoosh will check the last
 modification date of each file and add it to be reindexed if a newer file is
@@ -156,7 +156,7 b' or in the admin panel you can check `bui'
 Setting up LDAP support
 -----------------------
 
-RhodeCode starting from version 1.1 supports ldap authentication. In order
+Kallithea starting from version 1.1 supports ldap authentication. In order
 to use LDAP, you have to install the python-ldap_ package. This package is
 available via pypi, so you can install it by running
 
@@ -314,7 +314,7 b' LDAP Search Scope : required'
 
 Login Attribute : required
     The LDAP record attribute that will be matched as the USERNAME or
-    ACCOUNT used to connect to RhodeCode.  This will be added to `LDAP
+    ACCOUNT used to connect to Kallithea.  This will be added to `LDAP
     Filter`_ for locating the User object.  If `LDAP Filter`_ is specified as
     "LDAPFILTER", `Login Attribute`_ is specified as "uid" and the user has
     connected as "jsmith" then the `LDAP Filter`_ will be augmented as below
@@ -338,19 +338,19 b' Email Attribute : required'
     The LDAP record attribute which represents the user's email address.
 
 If all data are entered correctly, and python-ldap_ is properly installed
-users should be granted access to RhodeCode with ldap accounts.  At this
-time user information is copied from LDAP into the RhodeCode user database.
+users should be granted access to Kallithea with ldap accounts.  At this
+time user information is copied from LDAP into the Kallithea user database.
 This means that updates of an LDAP user object may not be reflected as a
-user update in RhodeCode.
+user update in Kallithea.
 
 If You have problems with LDAP access and believe You entered correct
-information check out the RhodeCode logs, any error messages sent from LDAP
+information check out the Kallithea logs, any error messages sent from LDAP
 will be saved there.
 
 Active Directory
 ''''''''''''''''
 
-RhodeCode can use Microsoft Active Directory for user authentication.  This
+Kallithea can use Microsoft Active Directory for user authentication.  This
 is done through an LDAP or LDAPS connection to Active Directory.  The
 following LDAP configuration settings are typical for using Active
 Directory ::
@@ -368,32 +368,32 b' appropriately configured.'
 Authentication by container or reverse-proxy
 --------------------------------------------
 
-Starting with version 1.3, RhodeCode supports delegating the authentication
+Starting with version 1.3, Kallithea supports delegating the authentication
 of users to its WSGI container, or to a reverse-proxy server through which all
 clients access the application.
 
-When these authentication methods are enabled in RhodeCode, it uses the
+When these authentication methods are enabled in Kallithea, it uses the
 username that the container/proxy (Apache/Nginx/etc) authenticated and doesn't
 perform the authentication itself. The authorization, however, is still done by
-RhodeCode according to its settings.
+Kallithea according to its settings.
 
 When a user logs in for the first time using these authentication methods,
-a matching user account is created in RhodeCode with default permissions. An
-administrator can then modify it using RhodeCode's admin interface.
+a matching user account is created in Kallithea with default permissions. An
+administrator can then modify it using Kallithea's admin interface.
 It's also possible for an administrator to create accounts and configure their
 permissions before the user logs in for the first time.
 
 Container-based authentication
 ''''''''''''''''''''''''''''''
 
-In a container-based authentication setup, RhodeCode reads the user name from
+In a container-based authentication setup, Kallithea reads the user name from
 the ``REMOTE_USER`` server variable provided by the WSGI container.
 
 After setting up your container (see `Apache's WSGI config`_), you'd need
 to configure it to require authentication on the location configured for
-RhodeCode.
+Kallithea.
 
-In order for RhodeCode to start using the provided username, you should set the
+In order for Kallithea to start using the provided username, you should set the
 following in the [app:main] section of your .ini file::
 
     container_auth_enabled = true
@@ -402,7 +402,7 b' following in the [app:main] section of y'
 Proxy pass-through authentication
 '''''''''''''''''''''''''''''''''
 
-In a proxy pass-through authentication setup, RhodeCode reads the user name
+In a proxy pass-through authentication setup, Kallithea reads the user name
 from the ``X-Forwarded-User`` request header, which should be configured to be
 sent by the reverse-proxy server.
 
@@ -420,8 +420,8 b' reverse-proxy setup with basic auth::'
       SetEnvIf X-Url-Scheme https HTTPS=1
 
       AuthType Basic
-      AuthName "RhodeCode authentication"
-      AuthUserFile /home/web/rhodecode/.htpasswd
+      AuthName "Kallithea authentication"
+      AuthUserFile /home/web/kallithea/.htpasswd
       require valid-user
 
       RequestHeader unset X-Forwarded-User
@@ -432,7 +432,7 b' reverse-proxy setup with basic auth::'
       RequestHeader set X-Forwarded-User %{RU}e
     </Location>
 
-In order for RhodeCode to start using the forwarded username, you should set
+In order for Kallithea to start using the forwarded username, you should set
 the following in the [app:main] section of your .ini file::
 
     proxypass_auth_enabled = true
@@ -446,7 +446,7 b' the following in the [app:main] section '
 Integration with Issue trackers
 -------------------------------
 
-RhodeCode provides a simple integration with issue trackers. It's possible
+Kallithea provides a simple integration with issue trackers. It's possible
 to define a regular expression that will fetch issue id stored in commit
 messages and replace that with an url to this issue. To enable this simply
 uncomment following variables in the ini file::
@@ -483,18 +483,18 b' can be found at *kallithea.lib.hooks*.'
 Changing default encoding
 -------------------------
 
-By default RhodeCode uses utf8 encoding, starting from 1.3 series this
+By default Kallithea uses utf8 encoding, starting from 1.3 series this
 can be changed, simply edit default_encoding in .ini file to desired one.
-This affects many parts in rhodecode including committers names, filenames,
-encoding of commit messages. In addition RhodeCode can detect if `chardet`
-library is installed. If `chardet` is detected RhodeCode will fallback to it
+This affects many parts in Kallithea including committers names, filenames,
+encoding of commit messages. In addition Kallithea can detect if `chardet`
+library is installed. If `chardet` is detected Kallithea will fallback to it
 when there are encode/decode errors.
 
 
 Setting Up Celery
 -----------------
 
-Since version 1.1 celery is configured by the rhodecode ini configuration files.
+Since version 1.1 celery is configured by the Kallithea ini configuration files.
 Simply set use_celery=true in the ini file then add / change the configuration
 variables inside the ini file.
 
@@ -509,14 +509,14 b' In order to start using celery run::'
 
 .. note::
    Make sure you run this command from the same virtualenv, and with the same
-   user that rhodecode runs.
+   user that Kallithea runs.
 
 HTTPS support
 -------------
 
 There are two ways to enable https:
 
-- Set HTTP_X_URL_SCHEME in your http server headers, than rhodecode will
+- Set HTTP_X_URL_SCHEME in your http server headers, than Kallithea will
   recognize this headers and make proper https redirections
 - Alternatively, change the `force_https = true` flag in the ini configuration
   to force using https, no headers are needed than to enable https
@@ -558,8 +558,8 b' Sample config for nginx using proxy::'
     server {
        listen          443;
        server_name     your.kallithea.server;
-       access_log      /var/log/nginx/rhodecode.access.log;
-       error_log       /var/log/nginx/rhodecode.error.log;
+       access_log      /var/log/nginx/kallithea.access.log;
+       error_log       /var/log/nginx/kallithea.error.log;
 
        ssl on;
        ssl_certificate     your.kallithea.server.crt;
@@ -626,7 +626,7 b' Here is a sample configuration file for '
             #Directive to properly generate url (clone url) for pylons
             ProxyPreserveHost On
 
-            #rhodecode instance
+            #kallithea instance
             ProxyPass / http://127.0.0.1:5000/
             ProxyPassReverse / http://127.0.0.1:5000/
 
@@ -668,7 +668,7 b' then change <someprefix> into your chose'
 Apache's WSGI config
 --------------------
 
-Alternatively, RhodeCode can be set up with Apache under mod_wsgi. For
+Alternatively, Kallithea can be set up with Apache under mod_wsgi. For
 that, you'll need to:
 
 - Install mod_wsgi. If using a Debian-based distro, you can install
@@ -681,7 +681,7 b" that, you'll need to:"
     a2enmod wsgi
 
 - Create a wsgi dispatch script, like the one below. Make sure you
-  check the paths correctly point to where you installed RhodeCode
+  check the paths correctly point to where you installed Kallithea
   and its Python Virtual Environment.
 - Enable the WSGIScriptAlias directive for the wsgi dispatch script,
   as in the following example. Once again, check the paths are
@@ -691,8 +691,8 b' Here is a sample excerpt from an Apache '
 
     WSGIDaemonProcess pylons \
         threads=4 \
-        python-path=/home/web/rhodecode/pyenv/lib/python2.6/site-packages
-    WSGIScriptAlias / /home/web/rhodecode/dispatch.wsgi
+        python-path=/home/web/kallithea/pyenv/lib/python2.6/site-packages
+    WSGIScriptAlias / /home/web/kallithea/dispatch.wsgi
     WSGIPassAuthorization On
 
 .. note::
@@ -700,7 +700,7 b' Here is a sample excerpt from an Apache '
    into above configuration
 
 .. note::
-   Running RhodeCode in multiprocess mode in apache is not supported,
+   Running Kallithea in multiprocess mode in apache is not supported,
    make sure you don't specify `processes=num` directive in the config
 
 
@@ -708,22 +708,22 b' Example wsgi dispatch script::'
 
     import os
     os.environ["HGENCODING"] = "UTF-8"
-    os.environ['PYTHON_EGG_CACHE'] = '/home/web/rhodecode/.egg-cache'
+    os.environ['PYTHON_EGG_CACHE'] = '/home/web/kallithea/.egg-cache'
 
     # sometimes it's needed to set the curent dir
-    os.chdir('/home/web/rhodecode/')
+    os.chdir('/home/web/kallithea/')
 
     import site
-    site.addsitedir("/home/web/rhodecode/pyenv/lib/python2.6/site-packages")
+    site.addsitedir("/home/web/kallithea/pyenv/lib/python2.6/site-packages")
 
     from paste.deploy import loadapp
     from paste.script.util.logging_config import fileConfig
 
-    fileConfig('/home/web/rhodecode/production.ini')
-    application = loadapp('config:/home/web/rhodecode/production.ini')
+    fileConfig('/home/web/kallithea/production.ini')
+    application = loadapp('config:/home/web/kallithea/production.ini')
 
 Note: when using mod_wsgi you'll need to install the same version of
-Mercurial that's inside RhodeCode's virtualenv also on the system's Python
+Mercurial that's inside Kallithea's virtualenv also on the system's Python
 environment.
 
 

docs/upgrade.rst

@@ -12,16 +12,16 b' Upgrading from PyPI (aka "Cheeseshop")'
    configuration backup before doing an upgrade.
 
    (These directions will use '{version}' to note that this is the version of
-   Rhodecode that these files were used with.  If backing up your RhodeCode
+   Kallithea that these files were used with.  If backing up your Kallithea
    instance from version 1.3.6 to 1.4.0, the ``production.ini`` file would be
    backed up to ``production.ini.1-3-6``.)
 
 
-If using a sqlite database, stop the Rhodecode process/daemon/service, and
+If using a sqlite database, stop the Kallithea process/daemon/service, and
 then make a copy of the database file::
 
  service kallithea stop
- cp rhodecode.db rhodecode.db.{version}
+ cp kallithea.db kallithea.db.{version}
 
 
 Back up your configuration file::
@@ -30,30 +30,30 b' Back up your configuration file::'
 
 
 Ensure that you are using the Python Virtual Environment that you'd originally
-installed Rhodecode in::
+installed Kallithea in::
 
  pip freeze
 
-will list all packages installed in the current environment.  If Rhodecode
+will list all packages installed in the current environment.  If Kallithea
 isn't listed, change virtual environments to your venv location::
 
- source /opt/rhodecode-venv/bin/activate
+ source /opt/kallithea-venv/bin/activate
 
 
-Once you have verified the environment you can upgrade ``Rhodecode`` with::
+Once you have verified the environment you can upgrade ``Kallithea`` with::
 
- easy_install -U rhodecode
+ easy_install -U kallithea
 
 Or::
 
- pip install --upgrade rhodecode
+ pip install --upgrade kallithea
 
 
 Then run the following command from the installation directory::
 
- paster make-config RhodeCode production.ini
+ paster make-config Kallithea production.ini
 
-This will display any changes made by the new version of RhodeCode to your
+This will display any changes made by the new version of Kallithea to your
 current configuration. It will try to perform an automerge. It's recommended
 that you re-check the content after the automerge.
 
@@ -80,21 +80,21 b' options that need to be set.'
    DB schema upgrade library has some limitations and can sometimes fail if you try to
    upgrade from older major releases. In such case simply run upgrades sequentially, eg.
    upgrading from 1.2.X to 1.5.X should be done like that: 1.2.X. > 1.3.X > 1.4.X > 1.5.X
-   You can always specify what version of RhodeCode you want to install for example in pip
-   `pip install RhodeCode==1.3.6`
+   You can always specify what version of Kallithea you want to install for example in pip
+   `pip install Kallithea==1.3.6`
 
 You may find it helpful to clear out your log file so that new errors are
 readily apparent::
 
- echo > rhodecode.log
+ echo > kallithea.log
 
-Once that is complete, you may now start your upgraded Rhodecode Instance::
+Once that is complete, you may now start your upgraded Kallithea Instance::
 
  service kallithea start
 
 Or::
 
- paster serve /var/www/rhodecode/production.ini
+ paster serve /var/www/kallithea/production.ini
 
 .. note::
    If you're using Celery, make sure you restart all instances of it after

docs/usage/backup.rst

@@ -1,26 +1,26 b''
 .. _backup:
 
 ====================
-Backing up RhodeCode
+Backing up Kallithea
 ====================
 
 
 Settings
 --------
 
-Just copy your .ini file, it contains all RhodeCode settings.
+Just copy your .ini file, it contains all Kallithea settings.
 
 Whoosh index
 ------------
 
 Whoosh index is located in **/data/index** directory where you installed
-RhodeCode ie. the same place where the ini file is located
+Kallithea ie. the same place where the ini file is located
 
 
 Database
 --------
 
-When using sqlite just copy rhodecode.db.
+When using sqlite just copy kallithea.db.
 Any other database engine requires a manual backup operation.
 
 Database backup will contain all gathered statistics

docs/usage/debugging.rst

@@ -1,10 +1,10 b''
 .. _debugging:
 
 ===================
-Debugging RhodeCode
+Debugging Kallithea
 ===================
 
-If you encountered problems with RhodeCode here are some instructions how to
+If you encountered problems with Kallithea here are some instructions how to
 possibly debug them.
 
 ** First make sure you're using the latest version available.**
@@ -12,7 +12,7 b' possibly debug them.'
 enable detailed debug
 ---------------------
 
-RhodeCode uses standard python logging modules to log it's output.
+Kallithea uses standard python logging modules to log it's output.
 By default only loggers with INFO level are displayed. To enable full output
 change `level = DEBUG` for all logging handlers in currently used .ini file.
 This change will allow to see much more detailed output in the logfile or

docs/usage/general.rst

@@ -1,17 +1,17 b''
 .. _general:
 
 =======================
-General RhodeCode usage
+General Kallithea usage
 =======================
 
 
 Repository deleting
 -------------------
 
-Currently when admin/owner deletes a repository, RhodeCode does not physically
+Currently when admin/owner deletes a repository, Kallithea does not physically
 delete a repository from filesystem, it renames it in a special way so it's
 not possible to push,clone or access repository. It's worth a notice that,
-even if someone will be given administrative access to RhodeCode and will
+even if someone will be given administrative access to Kallithea and will
 delete a repository You can easy restore such action by restoring `rm__<date>`
 from the repository name, and internal repository storage (.hg/.git). There
 is also a special command for cleaning such archived repos::
@@ -60,7 +60,7 b' example::'
 
 This can be an issue for build systems and any other hardcoded scripts, moving
 repository to a group leads to a need for changing external systems. To
-overcome this RhodeCode introduces a non changable replacement url. It's
+overcome this Kallithea introduces a non changable replacement url. It's
 simply an repository ID prefixed with `_` above urls are also accessible as::
 
   http://server.com/_<ID>
@@ -74,13 +74,13 b' Mailing'
 -------
 
 When administrator will fill up the mailing settings in .ini files
-RhodeCode will send mails on user registration, or when RhodeCode errors occur
+Kallithea will send mails on user registration, or when Kallithea errors occur
 on errors the mails will have a detailed traceback of error.
 
 
 Mails are also sent for code comments. If someone comments on a changeset
 mail is sent to all participants, the person who commited the changeset
-(if present in RhodeCode), and to all people mentioned with @mention system.
+(if present in Kallithea), and to all people mentioned with @mention system.
 
 
 Trending source files
@@ -95,7 +95,7 b' located in `/kallithea/lib/celerylib/tas'
 Cloning remote repositories
 ---------------------------
 
-RhodeCode has an ability to clone remote repos from given remote locations.
+Kallithea has an ability to clone remote repos from given remote locations.
 Currently it support following options:
 
 - hg  -> hg clone
@@ -109,9 +109,9 b' Currently it support following options:'
 
 If you need to clone repositories that are protected via basic auth, you
 might pass the url with stored credentials inside eg.
-`http://user:[e-mail]/repo`, RhodeCode will try to login and clone
+`http://user:[e-mail]/repo`, Kallithea will try to login and clone
 using given credentials. Please take a note that they will be stored as
-plaintext inside the database. RhodeCode will remove auth info when showing the
+plaintext inside the database. Kallithea will remove auth info when showing the
 clone url in summary page.
 
 
@@ -120,7 +120,7 b' Visual settings in admin pannel'
 -------------------------------
 
 
-Visualisation settings in RhodeCode settings view are extra customizations
+Visualisation settings in Kallithea settings view are extra customizations
 of server behavior. There are 3 main section in the settings.
 
 General
@@ -133,7 +133,7 b' define company specific information into'
 key that would add give info about a manager of each repository. There's no
 limit for adding custom fields. Newly created fields are accessible via API.
 
-`Show RhodeCode version` option toggles displaying exact RhodeCode version in
+`Show Kallithea version` option toggles displaying exact Kallithea version in
 the footer
 
 
@@ -153,7 +153,7 b' public/private icons should be shown in '
 Meta-Tagging
 ~~~~~~~~~~~~
 
-With this option enabled, special metatags that are recognisible by RhodeCode
+With this option enabled, special metatags that are recognisible by Kallithea
 will be turned into colored tags. Currently available tags are::
 
     [featured]

docs/usage/git_support.rst

@@ -5,18 +5,18 b' GIT support'
 ===========
 
 
-Git support in RhodeCode 1.3 was enabled by default. You need to have a git
+Git support in Kallithea 1.3 was enabled by default. You need to have a git
 client installed on the machine to make git fully work.
 
 Although There is one limitation on git usage.
 
 - large pushes requires a http server with chunked encoding support.
 
-if you plan to use git you need to run RhodeCode with some
+if you plan to use git you need to run Kallithea with some
 http server that supports chunked encoding which git http protocol uses,
 i recommend using waitress_ or gunicorn_ (linux only) for `paste` wsgi app
 replacement. Starting from version 1.4 waitress_ is the default wsgi server
-used in RhodeCode.
+used in Kallithea.
 
 To use, simply change change the following in the .ini file::
 

docs/usage/locking.rst

@@ -1,7 +1,7 b''
 .. _locking:
 
 ===================================
-RhodeCode repository locking system
+Kallithea repository locking system
 ===================================
 
 
@@ -20,7 +20,7 b' influence this state:'
   user has write/admin permissions on this repo
 
 
-RhodeCode will remember the user id who locked the repo
+Kallithea will remember the user id who locked the repo
 only this specific user can unlock the repo (locked=false) by calling
 
 - `hg/git push <repo>`

docs/usage/performance.rst

@@ -1,15 +1,15 b''
 .. _performance:
 
 ================================
-Optimizing RhodeCode Performance
+Optimizing Kallithea Performance
 ================================
 
-When serving large amount of big repositories RhodeCode can start
+When serving large amount of big repositories Kallithea can start
 performing slower than expected. Because of demanding nature of handling large
 amount of data from version control systems here are some tips how to get
 the best performance.
 
-* RhodeCode will perform better on machines with faster disks (SSD/SAN). It's
+* Kallithea will perform better on machines with faster disks (SSD/SAN). It's
   more important to have faster disk than faster CPU.
 
 * Slowness on initial page can be easily fixed by grouping repositories, and/or
@@ -17,7 +17,7 b' the best performance.'
   option and vcs_full_cache setting in .ini file
 
 
-Follow these few steps to improve performance of RhodeCode system.
+Follow these few steps to improve performance of Kallithea system.
 
 
 1. Increase cache
@@ -30,7 +30,7 b' 1. Increase cache'
     few hundreds of repositories on main page can sometimes make the system
     to behave slow when cache expires for all of them. Increasing `expire`
     option to day (86400) or a week (604800) will improve general response
-    times for the main page. RhodeCode has an intelligent cache expiration
+    times for the main page. Kallithea has an intelligent cache expiration
     system and it will expire cache for repositories that had been changed.
 
 2. Switch from sqlite to postgres or mysql
@@ -40,10 +40,10 b' 2. Switch from sqlite to postgres or mys'
     setup. Switching to mysql or postgres will result in a immediate
     performance increase.
 
-3. Scale RhodeCode horizontally
+3. Scale Kallithea horizontally
 
     Scaling horizontally can give huge performance increase when dealing with
-    large traffic (large amount of users, CI servers etc). RhodeCode can be
+    large traffic (large amount of users, CI servers etc). Kallithea can be
     scaled horizontally on one (recommended) or multiple machines. In order
     to scale horizontally you need to do the following:
 
@@ -53,7 +53,7 b' 3. Scale RhodeCode horizontally'
       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
+      variables in each .ini file to shared location across Kallithea 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)

docs/usage/statistics.rst

@@ -4,9 +4,9 b''
 Statistics
 ==========
 
-The RhodeCode statistics system makes heavy demands of the server resources, so
+The Kallithea statistics system makes heavy demands of the server resources, so
 in order to keep a balance between usability and performance, the statistics are
-cached inside db and are gathered incrementally, this is how RhodeCode does
+cached inside db and are gathered incrementally, this is how Kallithea does
 this:
 
 With Celery disabled
@@ -16,14 +16,14 b' With Celery disabled'
   updates statistics cache.
 - This happens on each single visit to the statistics page until all commits are
   fetched. Statistics are kept cached until additional commits are added to the
-  repository. In such a case RhodeCode will only fetch the new commits when
+  repository. In such a case Kallithea will only fetch the new commits when
   updating it's cache.
 
 
 With Celery enabled
 -------------------
 
-- On the first visit to the summary page RhodeCode will create tasks that will
+- On the first visit to the summary page Kallithea will create tasks that will
   execute on celery workers. This task will gather all of the stats until all
   commits are parsed, each task will parse 250 commits, and run the next task to
   parse next 250 commits, until all of the commits are parsed.

docs/usage/subrepos.rst

@@ -1,10 +1,10 b''
 .. _subrepos:
 
 =============================================
-working with RhodeCode and mercurial subrepos
+working with Kallithea and mercurial subrepos
 =============================================
 
-example usage of Subrepos with RhodeCode::
+example usage of Subrepos with Kallithea::
 
     ## init a simple repo
     hg init repo1
@@ -16,7 +16,7 b' example usage of Subrepos with RhodeCode'
     #clone subrepo we want to add
     hg clone http://rc.local/subrepo
 
-    ## use path like url to existing repo in RhodeCode
+    ## use path like url to existing repo in Kallithea
     echo "subrepo = http://rc.local/subrepo" > .hgsub
 
     hg add .hgsub
@@ -26,11 +26,11 b' example usage of Subrepos with RhodeCode'
 
 In file list of repo1 you will see a connected subrepo at revision it was
 during cloning.
-Clicking in subrepos link should send you to proper repository in RhodeCode
+Clicking in subrepos link should send you to proper repository in Kallithea
 
 cloning repo1 will also clone attached subrepository.
 
-Next we can edit the subrepo data, and push back to RhodeCode. This will update
+Next we can edit the subrepo data, and push back to Kallithea. This will update
 both of repositories.
 
 see http://mercurial.aragost.com/kick-start/en/subrepositories/ for more

docs/usage/troubleshooting.rst

@@ -14,14 +14,14 b' Troubleshooting'
 |
 
 :Q: **Can't install celery/rabbitmq?**
-:A: Don't worry RhodeCode works without them too. No extra setup is required.
+:A: Don't worry Kallithea works without them too. No extra setup is required.
     Try out great celery docs for further help.
 
 |
 
 :Q: **Long lasting push timeouts?**
 :A: Make sure you set a longer timeouts in your proxy/fcgi settings, timeouts
-    are caused by https server and not RhodeCode.
+    are caused by https server and not Kallithea.
 
 |
 
@@ -43,16 +43,16 b' Troubleshooting'
 
 |
 
-:Q: **How i use hooks in RhodeCode?**
+:Q: **How i use hooks in Kallithea?**
 :A: It's easy if they are python hooks just use advanced link in hooks section
     in Admin panel, that works only for Mercurial. If you want to use githooks,
     just install proper one in repository eg. create file in
-    `/gitrepo/hooks/pre-receive`. You can also use RhodeCode-extensions to
+    `/gitrepo/hooks/pre-receive`. You can also use Kallithea-extensions to
     connect to callback hooks, for both Git and Mercurial.
 
 |
 
-:Q: **RhodeCode is slow for me, how can i make it faster?**
+:Q: **Kallithea is slow for me, how can i make it faster?**
 :A: See the :ref:`performance` section
 
 |