##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
shadow-repos: use safer way to destroy shadow repositories....
shadow-repos: use safer way to destroy shadow repositories. we had reported errors on removal of shadow repos. Not reproduced, however suspecting are filesystem sync/symlink race-conditions on shared storage. End result were existing shadow-repo directories that tricked rhodecode into thinking shadow repos is existing, but infact it was a dummy structure semi-removed. Using shutil.move we ENSURE rhodecode doesn't read those back even if removal fails.
marcink - - Load All Authors

File last commit:

r1:854a839a default
r2791:27d869d5 stable
Show More
migrate-repos.rst
23 lines | 740 B | text/x-rst | RstLexer
/ docs / install / migrate-repos.rst
History | Annotation | Raw |Copy content |Copy permalink

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.