I’d like to add support for
user.git.coop for static sites at some point, when I can find the time. Only potential issue with this, last time I looked, was that we would need to sort out our own scripts for provisioning Let’s Encrypt certs, but this isn’t a big deal and now that wild card certs are possible that might be the way to go. Perhaps a domain other than
git.coop could be used, how about
user.member.webarch.coop or something else?
I’m not sure what the other GitLab CE features we could add are, let me know if you find some?
We don’t have currently have any plans for raising additional income to cover the costs of
git.coop, do you have any suggestions?
runner.git.coop server has acces to 6 CPU cores and 16G of RAM, the processors are:
model name : AMD Opteron(tm) Processor 6128
cpu MHz : 1884.607
cache size : 512 KB
bogomips : 3769.63
We could rebuild or move it to the newer front facing server which has low energy CPUs (but probably faster RAM):
model name : Intel(R) Xeon(R) CPU E5-2630L v4 @ 1.80GHz
cpu MHz : 1795.876
cache size : 25600 KB
bogomips : 3591.70
And although the CPU might not be much different in speed we could potentially, if there is spare space, run it off the RAID1 SSDs that are the system disks rather than over the network off the file server as this might be faster and we don’t need backups of this server as we can spin it up from scratch using Ansible, the only concern about doing this would be that it would add additional wear and tear to the SSDs and we have 45 virtual servers running on this machine and can’t afford for it to have any downtime.
The machine it is on does have 10k SAS disk set up with (I believe) software RAID5 and perhaps moving it to them might help some, I’ll discuss it with @kate and see what we can come up with, but it might be the case that we can’t really do much without faster hardware or by using external servers.
Following are some Munin graphs from today to give you an idea of what is going on: