# GitHub Co-operative?

**URL:** <https://community.coops.tech/t/github-co-operative/885>\
**Category:** Technology\
**Created:** [1 July 2018 12:51 UTC](https://community.coops.tech/t/github-co-operative/885 "2018-07-01T12:51:33Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![BillySmith](https://community.coops.tech/user_avatar/community.coops.tech/billysmith/32/273_2.png) [@BillySmith](https://community.coops.tech/u/BillySmith)\
**Post date:** [1 July 2018 12:51 UTC](https://community.coops.tech/t/github-co-operative/885/1 "2018-07-01T12:51:33Z")

</div>

Since GitHub has become part of the Microsoft combine, what about creating a version of GitHub that is owned and run by it’s users?

Using a Co-op model would work for this.

---

<div class="post-metadata">

**Author:** ![Graham](https://community.coops.tech/user_avatar/community.coops.tech/graham/32/79_2.png) [@Graham](https://community.coops.tech/u/Graham)\
**Post date:** [1 July 2018 12:54 UTC](https://community.coops.tech/t/github-co-operative/885/2 "2018-07-01T12:54:52Z")

</div>

You mean something like [https://git.coop](https://git.coop) ?

---

<div class="post-metadata">

**Author:** ![BillySmith](https://community.coops.tech/user_avatar/community.coops.tech/billysmith/32/273_2.png) [@BillySmith](https://community.coops.tech/u/BillySmith)\
**Post date:** [1 July 2018 12:57 UTC](https://community.coops.tech/t/github-co-operative/885/3 "2018-07-01T12:57:01Z")

</div>

Thank you. 😃

I didn’t know that this existed. 😃

---

<div class="post-metadata">

**Author:** ![Graham](https://community.coops.tech/user_avatar/community.coops.tech/graham/32/79_2.png) [@Graham](https://community.coops.tech/u/Graham)\
**Post date:** [1 July 2018 13:47 UTC](https://community.coops.tech/t/github-co-operative/885/4 "2018-07-01T13:47:11Z")

</div>

Full disclosure: as of June 27th I’ve been a member of the management committee of Webarchitects (which reminds me, I must read the rules before the next meeting…).

---

<div class="post-metadata">

**Author:** ![chris](https://community.coops.tech/user_avatar/community.coops.tech/chris/32/2_2.png) [@chris](https://community.coops.tech/u/chris)\
**Post date:** [1 July 2018 18:11 UTC](https://community.coops.tech/t/github-co-operative/885/5 "2018-07-01T18:11:07Z")

</div>

> [@BillySmith](#):
>
> I didn’t know that this existed. 😃

See the [background thread on the CoTech Lomio forum](https://www.loomio.org/d/2BZ0CS9e/git-hosting-for-co-operators). the page on the Webarchitects site:

> **[Co-operative Git Hosting](https://www.webarchitects.coop/git)**
>
> Webarchitects provides free, unlimited git hosting for source code, issues and documentation for members of our co-operative on our GitLab CE server at git.coop. We can also provide maintained virtual private servers running GitLab CE for clients.

And the thread on this forum for more on [git.coop](https://git.coop/):

> [@Git hosting for co-operators : GitLab at git.coop](https://community.coops.tech/t/git-hosting-for-co-operators-gitlab-at-git-coop/544):
>
> Thank to testing by @decentral1se we are please to announce that GitLab CI is now available on the Co-operative GitLab server at [git.coop](https://git.coop/) using Docker and it is set to use debian:latest. I’m now looking at setting up [GitLab Container Registry](https://docs.gitlab.com/ce/user/project/container_registry.html). See [this Loomio thread](https://www.loomio.org/d/2BZ0CS9e/git-hosting-for-co-operators) for the background story of this service.

---

<div class="post-metadata">

**Author:** ![decentral1se](https://community.coops.tech/user_avatar/community.coops.tech/decentral1se/32/3122_2.png) [@decentral1se](https://community.coops.tech/u/decentral1se)\
**Post date:** [2 July 2018 07:39 UTC](https://community.coops.tech/t/github-co-operative/885/6 "2018-07-02T07:39:49Z")

</div>

@chris, been meaning to ask and suppose here is as good as anywhere!

I do know that Gitlab has a bunch to offer (via [Features | GitLab](https://about.gitlab.com/features/)) and have just been recently seen a private [gitlab.com](http://gitlab.com) account and noticed they have _a lot_ more on offer there. Is that the difference between the CE version and paid version?

One thing I’ve wondered about is increased resources for the CI runner. Do you consider running some sort of maintenance contract for that? Since Aptivate is moving (albeit slowly) towards more and more of our infrastructure on git.coop, we’d be interested to see!

EDIT: Oh yeah, and for anyone considering using git.coop, I absolutely recommend. Can’t fault webarchs on anything! Solid response times for all my nagging.

---

<div class="post-metadata">

**Author:** ![chris](https://community.coops.tech/user_avatar/community.coops.tech/chris/32/2_2.png) [@chris](https://community.coops.tech/u/chris)\
**Post date:** [2 July 2018 09:03 UTC](https://community.coops.tech/t/github-co-operative/885/7 "2018-07-02T09:03:08Z")

</div>

> [@decentral1se](#):
>
> I do know that Gitlab has a bunch to offer (via [Features | GitLab](https://about.gitlab.com/features/)) and have just been recently seen a private [gitlab.com](http://gitlab.com) account and noticed they have _a lot_ more on offer there. Is that the difference between the CE version and paid version?

Do you have any particular features in mind? The things I hope we will do with [git.coop](https://git.coop/) over the next year or so are:

- Rebuild it on a Debian Stretch virtual server (it is currently running on a Jessie server) with the Ansible code to deploy it being made public (currently this is in a private repo).
- Add a [GitLab Container Registry](https://docs.gitlab.com/ee/administration/container_registry.html)
- Setup a [Mattermost server](https://docs.mattermost.com/install/install-debian-88.html) and enable [GitLab Single Sign-On](https://docs.mattermost.com/deployment/sso-gitlab.html)

> [@decentral1se](#):
>
> One thing I’ve wondered about is increased resources for the CI runner. Do you consider running some sort of maintenance contract for that?

Does it need an increase in resources? The server doesn’t seem very loaded to me, there are big spikes and at some point we will get a faster file server which should help flatten these:

![cpu-week](https://community.coops.tech/uploads/default/original/1X/e95f54a28b2f0b2497647725787f48fcf83d6ec5.png) ![if_docker0-week](https://community.coops.tech/uploads/default/original/1X/14d3989d71845b5ff0182d124c78b6aca4715f68.png) ![load-week](https://community.coops.tech/uploads/default/original/1X/9bbdc9a7d4a3b8cbee77d1cc1371e9ab35180d97.png) ![memory-week](https://community.coops.tech/uploads/default/original/1X/0de2be3ea5ea99ee9412fcf09d07fd6a8fa8327d.png)

By the way at our AGM last week we started to discuss setting up a `members.webarchitects.coop` Discourse forum and, assuming this is agreed at our Committee meeting next week, I expect it’ll be up and running in a couple of weeks time at the latest — when it is that would be the ideal place to raise matter like this, in the meantime this is good place.

---

<div class="post-metadata">

**Author:** ![SzczepanOfAnimorph](https://community.coops.tech/user_avatar/community.coops.tech/szczepanofanimorph/32/1692_2.png) [@SzczepanOfAnimorph](https://community.coops.tech/u/SzczepanOfAnimorph)\
**Post date:** [2 July 2018 18:07 UTC](https://community.coops.tech/t/github-co-operative/885/8 "2018-07-02T18:07:44Z")

</div>

Works like a charm, thank you WebArchs!

---

<div class="post-metadata">

**Author:** ![chris](https://community.coops.tech/user_avatar/community.coops.tech/chris/32/2_2.png) [@chris](https://community.coops.tech/u/chris)\
**Post date:** [3 July 2018 06:58 UTC](https://community.coops.tech/t/github-co-operative/885/9 "2018-07-03T06:58:10Z")

</div>

The [P2P Foundation](https://p2pfoundation.net/) have a wiki paging listing [community hosted GitLab instances](https://wiki.p2pfoundation.net/List_of_Community-Hosted_GitLab_Instances) and there is one other `.coop` listed there, the domain is owned by the New Zealand based ii Limited, the IP address is on a Packet Host (New York, USA) subnet and they are running GitLab Enterprise Edition (not Free software), rather than the Community Edition (Free software), that we have at [git.coop](https://git.coop/), it is open to allow anyone to register and I guess Enspiral might be involved since it hosts [a copy of the Loomio code](https://gitlab.ii.coop/loomio/loomio)?

> **[Sign in](https://gitlab.ii.coop/users/sign_in)**
>
> GitLab Enterprise Edition

Does anyone know more about it?

---

<div class="post-metadata">

**Author:** ![decentral1se](https://community.coops.tech/user_avatar/community.coops.tech/decentral1se/32/3122_2.png) [@decentral1se](https://community.coops.tech/u/decentral1se)\
**Post date:** [4 July 2018 07:59 UTC](https://community.coops.tech/t/github-co-operative/885/10 "2018-07-04T07:59:12Z")

</div>

> - the Ansible code to deploy it being made public

Great!

> - Add a GitLab Container Registry

Oh yes please!

> Does it need an increase in resources?

I think it is limited to single CI runs on projects. If I don’t cancel a previous build when running another, the other is pending. Also, when we two people are running builds on projects within an account, I think they queue builds and only one runs at a time. Could be wrong but that’s just what I’ve noticed in passing.

> By the way at our AGM last week we started to discuss setting up a members.webarchitects.coop

🔥🔥🔥

---

<div class="post-metadata">

**Author:** ![chris](https://community.coops.tech/user_avatar/community.coops.tech/chris/32/2_2.png) [@chris](https://community.coops.tech/u/chris)\
**Post date:** [4 July 2018 08:45 UTC](https://community.coops.tech/t/github-co-operative/885/11 "2018-07-04T08:45:47Z")

</div>

> [@decentral1se](#):
>
> I think it is limited to single CI runs on projects. If I don’t cancel a previous build when running another, the other is pending. Also, when we two people are running builds on projects within an account, I think they queue builds and only one runs at a time. Could be wrong but that’s just what I’ve noticed in passing.

We had `concurrent = 1` in `/etc/gitlab-runner/config.toml`, I have increased this to `4`, I’m not sure if this will do the job or if additional `[[runners]]` sections need adding to the file, the [documentation](https://docs.gitlab.com/runner/configuration/advanced-configuration.html) doesn’t appear to make this clear? Let me know if this has made a difference next time you use it.

---

<div class="post-metadata">

**Author:** ![jdaviescoates](https://community.coops.tech/user_avatar/community.coops.tech/jdaviescoates/32/223_2.png) [@jdaviescoates](https://community.coops.tech/u/jdaviescoates)\
**Post date:** [4 July 2018 10:27 UTC](https://community.coops.tech/t/github-co-operative/885/12 "2018-07-04T10:27:19Z")

</div>

> [@chris](#):
>
> Does anyone know more about it?

I didn’t, but it would appear it is run by this chap Chris McClimans [@hippiehacker on twitter](https://twitter.com/hippiehacker) (blogs at [http://blog.ii.coop/](http://blog.ii.coop/)) so [I’ve just invited him here to tell us more](https://twitter.com/jdaviescoates/status/1014455273468170240) 🙂
