##// 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:

r1:854a839a default
r2591:36829a17 stable
Show More
migrate-repos.rst
23 lines | 740 B | text/x-rst | RstLexer

Migrating |repos|

If you have installed |RCM| and have |repos| that you wish to migrate into the system, use the following instructions.

  1. On the |RCM| interface, check your |repo| storage location under :menuselection:`Admin --> Settings --> System Info`. For example, Storage location: /home/{username}/repos.
  2. Copy the |repos| that you want |RCM| to manage to this location.
  3. Remap and rescan the |repos|, see :ref:`remap-rescan`

Important

Directories create |repo| groups inside |RCM|.

Importing adds |RCM| git hooks to your |repos|.

You should verify if custom .hg or .hgrc files inside repositories should be adjusted since |RCM| reads the content of them.