My personal @github repos are now migrated to @gitlab.
As for why I chose to do this?
http://www.tuxmachines.org/node/112706 and http://techrights.org/2018/06/17/microsoft-patent-cybermobbing/ for starters…
My personal @github repos are now migrated to @gitlab.
As for why I chose to do this?
http://www.tuxmachines.org/node/112706 and http://techrights.org/2018/06/17/microsoft-patent-cybermobbing/ for starters…
Looks like I am not the only person #movingtogitlab :-)
Sad news that M$ are to acquire GitHub. I suspect I’ll start getting Windows adverts in my email inbox soon as my office uses GitHub
On the plus side, this LinuxJournal article has proposed some alternatives. GitLab is a good one and even mentioned on some job listings so I guess I’ll move my repos there.
I’ll be removing my GitHub repos…
https://www.linuxjournal.com/content/microsoft-reportedly-acquire-github
A while ago, I posted of my frustration with Google Music when it refused to download my tracks. Well, I did some digging around and found that someone had written an API to expose the Google Music backend. The link is at
https://github.com/simon-weber/Unofficial-Google-Music-API
and has spawned several other tools including
https://github.com/thebigmunch/gmusicapi-scripts/
Which is a set of scripts designed to sync, upload and/or download from the Google Music collection.
I wrote my own Python script using the Gmusic API to bulk delete albums from my Gmusic account (it’s easy to bulk upload using Google’s MusicManager, but not to bulk delete), and the gmusicapi-scripts enables me to download most of my tracks.
I do a fair amount of work using git as version control, with SVN and CVS close behind, but I haven’t used any of them so much as a distributed version control. However, since I’ve started using Bitbucket and GitHub, I have encountered many issues to do with DVC. One of the main ones is communication via proxy.
My workplace doesn’t allow communication through the net without it going through a proxy server and it is an major pain in the arse to get through. Fortunately, git allows you to configure git to use a proxy server:
To use a proxy server for HTTP communication:
git config --global http.proxy http://user:password@proxyserver:9999
To use a proxy server for HTTPS communication:
git config --global https.proxy http://user:password@proxyserver:9999
My company firewall also injects its own SSL certificate, which breaks SSL verification, so to get around that:
git config --global http.sslVerify false