[Replicant] Git bundles as solution for issues with git.replicant.us

Wolfgang Wiedmeyer wreg at wiedmeyer.de
Thu Dec 29 15:44:35 UTC 2016


Denis 'GNUtoo' Carikli writes:

> On Mon, 19 Dec 2016 00:13:27 +0100
> Wolfgang Wiedmeyer <wreg at wiedmeyer.de> wrote:
>
>> The cause is probably mostly related to server load
>> in both instances.
> Indeed.
>> I investigated a bit and found a solution: git
>> bundles. The repo tool searches for them by default and uses them if
>> they are available. I did a blog post about them [1]. 
> Thanks a lot for documenting it, I mentioned it before but I didn't have
> time to look at how to use it.
>
>> I'm not sure how easy they can be made accessible when using Gitlab,
>> but if you use Apache or Nginx on the server, then it's likely
>> possible using similar AliasMatch rules as I used.
> Worst case scenario we could use git hooks. We might also revisit the
> use of gitlab when replicant source code is moved to another server.

Any update regarding new infrastructure? Is there anything I could help
with?

Wolfgang

> Denis.


-- 
Website: https://fossencdi.org
OpenPGP: 0F30 D1A0 2F73 F70A 6FEE  048E 5816 A24C 1075 7FC4
Key download: https://wiedmeyer.de/keys/ww.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.osuosl.org/pipermail/replicant/attachments/20161229/8f3a7ac9/attachment.asc>


More information about the Replicant mailing list