91–100 of 175 posts
And so is all Github-dependent deployment...
The main reason that we switch to that was exactly to avoid deployment issues. Security is also a bonus (in case somebody modifies existing packages).
Probably there are tools like this for all type of packages.
The common complaint is that when github goes down so do issue trackers/project management/docs etc. What are the equivalent alternatives for these systems that are distributed, so tolerant to downtime. If you are in a situation that you're using a DVCS but relying on centralised everything else, and saying that you're unable to work because your Issue tracker/CI server is down, have you really gained anything over t…
You can setup gitlab with clones, if one server goes down, second has a copy. You know, git is a distributed system, unlike github.
Earlier quoted context omitted.
Now if only we had a convenient way of using a distributed VCS without a central hub.
That sounds like a joke, but that's exactly the problem: the VCS has been distributed, but not all the services enmeshed around it: all the discussions (issues, pull requests, design debates, …). Github makes it easy to host git repositories, but so do a bunch of other services and it's not that hard to host your own either way or to set up trees of repository or multiple mirrors or what have you. The reason people u…
Depends for who. When I'm a user of a project, I don't care at all about anything other than the repository. The source code is the only thing that matters.
Anyway, you can't really avoid centralization in most of the projects. Barring some extreme social experiments, a project always has identity, a "canonical version". That's your SPOF right there. Of course we have tons of experience with mitigating potential issues - from caching and mirroring to not doing stupid shit like telling your CI server to download dependencies from GitHub every time it builds your project. Temporary GitHub outages seem to be a problem mostly for people doing the latter kind of stupid shit.
What would be interesting to see though is some kind of torrent network for Git repos. The kind of where I ask for a particular commit of a particular project, and I get a way to download it from some random computer that has it (with all the magic crypto code signing for confirming the code was not maliciously changed, etc.). Node.js developers have local mirrors of third of GitHub anyway, so that would pretty much solve "GitHub is down" issues.
Though it would not solve the problem of people too lazy to have a local cache of their dependencies...
SourceForge is doing fine ;)
If only we had a version control system that didn't rely on a central hub...
We do, it's called Fossil! http://fossil-scm.org/ Fossil tracks issues (tickets), documentation, and wiki pages at the same level as it tracks code, so when you clone a Fossil repo, everything gets downloaded to your local computer. You can then respond to tickets and perform repo maintenance offline, syncing everything to the server when you're back up. Edit: A few weeks ago I got a job a one-hour train ride away. I…
If only we had a version control system that didn't rely on a central hub...
Earlier quoted context omitted.
Now if only we had a convenient way of using a distributed VCS without a central hub.
Did someone say GitTorrent...? https://github.com/cjb/GitTorrent
Also:
sudo npm install --global gittorrent
Cool! It automatically installs a local copy of half of GitHub! ;).