# HG changeset patch
# User Anatoly Bubenkov <bubenkoff@gmail.com>
# Date 2015-04-22 14:57:12
# Node ID 778f7ae3b6eb1497ce1f3aac5653aab8e5fdba0a
# Parent  d741b99effdf396b8391814b26545451d138ab5b

docs: add a reference to https://github.com/shazow/sqlalchemygrate for migration from sqlite to other dbs

diff --git a/docs/usage/performance.rst b/docs/usage/performance.rst
--- a/docs/usage/performance.rst
+++ b/docs/usage/performance.rst
@@ -39,7 +39,8 @@ 2. Switch from sqlite to postgres or mys
     sqlite is a good option when having a small load on the system. But due to
     locking issues with sqlite, it is not recommended to use it for larger
     deployments. Switching to mysql or postgres will result in an immediate
-    performance increase.
+    performance increase. A tool like SQLAlchemyGrate_ can be used for
+    migrating to another database platform.
 
 3. Scale Kallithea horizontally
 
@@ -61,3 +62,5 @@ 3. Scale Kallithea horizontally
     - 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.
+
+.. _SQLAlchemyGrate: https://github.com/shazow/sqlalchemygrate