##// END OF EJS Templates
caches: use individual namespaces per user to prevent beaker caching problems....
caches: use individual namespaces per user to prevent beaker caching problems. - especially for mysql in case large number of data in caches there could be critical errors storing cache, and thus preventing users from authentication. This is caused by the fact that we used single namespace for ALL users. It means it grew as number of users grew reaching mysql single column limit. This changes the behaviour and now we use namespace per-user it means that each user-id will have it's own cache namespace fragmenting maximum column data to a single user cache. Which we should never reach.

File last commit:

r1856:25c48cf5 stable
r2572:5b07455a default
Show More
api-examples.rst
65 lines | 1.8 KiB | text/x-rst | RstLexer
project: added all source files and assets
r1 .. _api-ex:
API Example Usage
=================
Use the following example uses of the |RCE| API to carry out work on your
instances, or |repo| maintanence on the server. For the complete API
documentation, see the :ref:`api` section.
.. _api-strip:
Stripping Commits
-----------------
The strip command is useful for removing commits on the server, allowing
you to push changes without using force. To strip commits on the server, use
the following steps:
1. Install |RCT|, as explained in the :ref:`install-tools` section.
2. Configure the :file:`~/.rhoderc` file with the API connection details, as
explained in the :ref:`config-rhoderc` section.
3. Check the |RCE| changelog and see from which revision onwards you wish to
strip commits. This will also strip all descendants.
.. image:: ../images/pre-strip.png
4. Enter your |RCT| virtual environment, using the following example:
.. code-block:: bash
$ . venv/bin/activate
(venv)$
5. Use the API to strip a commit, or number of commits from a |repo|. In this
example I am stripping the top two commits from ``ad1e0523a4ab`` onwards.
.. note::
Repositories in |repo| groups require the |repo| group to be passed as
part of the ``repoid``.
.. code-block:: bash
# Run the Strip API call
$ rhodecode-api --instance-name=instance-id strip \
repoid:repo-group/repo-name revision:ad1e0523a4ab branch:stable
# Check the JSON-RPC verification
docs: small rst fixes.
r1856 .. code-block:: javascript
project: added all source files and assets
r1
{
"error": null,
"id": 5960,
"result": {
docs: small rst fixes.
r1856 "msg": "Stripped commit ad1e0523a4ab from repo `repo-group/repo-name`",
project: added all source files and assets
r1 "repository": "repo-group/repo-name"
}
}
6. Once the commits are stripped, you can verify that they are
stripped on the web interface.
.. image:: ../images/post-strip.png