kallithea Files · docs/usage/subrepos.rst

Files @ cdf10b3df899

Branch filter:

Location: kallithea/docs/usage/subrepos.rst

cdf10b3df899 1013 B text/prs.fallenstein.rst Show Annotation Show as Raw Download as Raw

Jonathan Sternberg

Allow RhodeCode maintainers to specify a custom bug tracker.

This allows people who maintain large RhodeCode installations to setup their
own bug tracker and respond to requests against their specific installation.
The maintainer is then free to forward problems with RhodeCode to the
canonical issue tracker on bitbucket.

If the config option "bugtracker" is present, its value will be used with the
"Report a bug" button. If left blank, this disables the button. If no value is
present, then the default is used. This is so that the new config option
doesn't break installations of RhodeCode upgrading to a newer version and to
allow easier installation for the common use case.

.. _subrepos:

=============================================
working with RhodeCode and mercurial subrepos
=============================================

example usage of Subrepos with RhodeCode::

    ## init a simple repo
    hg init repo1
    cd repo1
    echo "file1" > file1
    hg add file1
    hg ci --message "initial file 1"

    #clone subrepo we want to add
    hg clone http://rc.local/subrepo

    ## use path like url to existing repo in RhodeCode
    echo "subrepo = http://rc.local/subrepo" > .hgsub

    hg add .hgsub
    hg ci --message "added remote subrepo"



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

cloning repo1 will also clone attached subrepository.

Next we can edit the subrepo data, and push back to RhodeCode. This will update
both of repositories.

see http://mercurial.aragost.com/kick-start/en/subrepositories/ for more
information about subrepositories