3 ms·

And yesterday we had "GitHub pausing feature development to prioritize moving infra to Azure", immediately followed by them breaking their infra.

cluckindan 1y ago
Well, of course the corporation wants to dogfood their platform. Expecting more and more downtime and random issues in the future.
progbits 1y ago
I thought they were already on Azure? At least I'm pretty sure the runners are, our account rep keeps trying to get us to use their GPU runners but they don't have a good GPU model selection and it seems to match what azure offers.
thelastgallon 1y ago
Its better for github to self-host.
sam_lowry_ 1y ago
Here's the step-by-step guide to self-hosting git repositories: Change directory to your local git repository that you want to share with friends and colleagues and do a bare clone `git clone --bare . /tmp/repo.git`. You just created a copy of the .git folder without all the checked out files. Upload /tmp/repo.git to your linux server over ssh. Don't have one? Just order a tiny cloud server from Hetzner. You can place your git repository anywhere, but the best way is to put it in a separate folder, e.g. /var/git. The command would look like `scp -r /tmp/repo.git me@server:/var/git/`. To share the repository with others, create a group, e.g. `groupadd --users me git` You will be able to add more users to the group with groupmod. Your git repository is now writable only by me. To make it writable by the git group, you have to change the group on all files in the repository to git with `chgrp -R git /var/repo.git` and enable the group write bit on them with `chmod -R g+w /var/repo.git`. This fixes the shared access for existing files. For new files, we have to make sure the group write bit is always on by changing UMASK from 022 to 002 in /etc/login.defs. There is one more trick. For now on, all new files and folders in /var/git will be created with the user's primary group. We could change users to have git as the primary group. But we can also force all new files and folders to be created with the parent folder's group and not user primary group. For that, set the group sticky bit on all folders in /var/git with `find /var/git -type d -exec chmod g+s \{\} +` You are done. Want to host your git repository online? Install caddy and point to /var/git with something like example.com { root * /var/git file_server } Your git repository will be instantly accessible via https://example.com/repo.git https://example.com/repo.git.

cluckindan 1y ago

Well, of course the corporation wants to dogfood their platform. Expecting more and more downtime and random issues in the future.

progbits 1y ago

I thought they were already on Azure? At least I'm pretty sure the runners are, our account rep keeps trying to get us to use their GPU runners but they don't have a good GPU model selection and it seems to match what azure offers.

thelastgallon 1y ago

Its better for github to self-host.

sam_lowry_ 1y ago

Here's the step-by-step guide to self-hosting git repositories: Change directory to your local git repository that you want to share with friends and colleagues and do a bare clone `git clone --bare . /tmp/repo.git`. You just created a copy of the .git folder without all the checked out files. Upload /tmp/repo.git to your linux server over ssh. Don't have one? Just order a tiny cloud server from Hetzner. You can place your git repository anywhere, but the best way is to put it in a separate folder, e.g. /var/git. The command would look like `scp -r /tmp/repo.git me@server:/var/git/`. To share the repository with others, create a group, e.g. `groupadd --users me git` You will be able to add more users to the group with groupmod. Your git repository is now writable only by me. To make it writable by the git group, you have to change the group on all files in the repository to git with `chgrp -R git /var/repo.git` and enable the group write bit on them with `chmod -R g+w /var/repo.git`. This fixes the shared access for existing files. For new files, we have to make sure the group write bit is always on by changing UMASK from 022 to 002 in /etc/login.defs. There is one more trick. For now on, all new files and folders in /var/git will be created with the user's primary group. We could change users to have git as the primary group. But we can also force all new files and folders to be created with the parent folder's group and not user primary group. For that, set the group sticky bit on all folders in /var/git with `find /var/git -type d -exec chmod g+s \{\} +` You are done. Want to host your git repository online? Install caddy and point to /var/git with something like example.com { root * /var/git file_server } Your git repository will be instantly accessible via https://example.com/repo.git https://example.com/repo.git.