Replicant

h1. Source code repositories

h2. Mirrors 

h3. Pushing mirrors with SSH access

If you have SSH access, you can then clone the git repository directly on the server. This is way faster than having to push the code from a slow ADSL connection for instance.

# Check the LineageOS manifest for newly added repos

# If there are any, add them in the LineageOS-mirror manifest and push the changes to git.replicant.us

# If there are any, create the newly added repos in the LineageOS-mirror group (using the exact same names the repos have in LineageOS)

<pre>

# sudo -iu git

$ cd repositories/LineageOS-mirror/

$ git clone --mirror git://github.com/LineageOS/<repo-name>.git

$ cd <repo-name>.git

$ touch git-daemon-export-ok

</pre>

h3. Pushing the code without SSH

Replicant uses gitolite to handle git access.

gitolite is configured by configuration files stored in git. The repository that handles that is at:

<pre>

ssh://git@git.replicant.us/gitolite-admin

</pre>

h3. cgit

See [[Cgit]] for where to adjust its configuration. 

Once the code is pushed you will need to adjust the cgit configuration to make it appear on the web interface.

h3. Bundles

It's worth to check if all mirror repos have bundles in place.

h3. CAF variants

If we ever add support for a device that uses CAF branches of Qualcomm repos, we need to figure out how the mirror can still be updated and how releases can be tagged.

CAF branches are in the same repos as the default branches. So two or more local repos are created for one remote repo when the default branch and the CAF branches are checked out. The current setup for tagging a new release and updating the mirror assumes that there is one local repo for one remote repo.