101–110 of 154 posts
For everyone who is currently loosing productivity, perhaps your time might be well spent reviewing `git daemon`: http://git-scm.com/book/en/v2/Git-on-the-Server-Git-Daemon
Earlier quoted context omitted.
For repositories your projects depend on, you can set up a local proxy so you at least have local copies for continuous integration. E.g. PHP's Composer project has _Toran_ and _Satis_ for this: http://tech.m6web.fr/composer-installation-without-github.ht...
doesn't give me easy access to the source, browseable and searchable, I can't link to it when discussing with a colleague via chat, can't browse the docs and the wiki and I can't update them. It's a minor advantage at the cost of running yet another piece in my infrastructure that may die or exhibit problems. We use nexus as a proxy for various repositories and so far I've had nexus down more often than github.
IS there any opensource private github?
For everyone who is currently loosing productivity, perhaps your time might be well spent reviewing `git daemon`: http://git-scm.com/book/en/v2/Git-on-the-Server-Git-Daemon
For everyone who is currently losing productivity, perhaps you should close your HN tab
WALTER MERCADO
Earlier quoted context omitted.
GitHub isn't made for that though, if you need scripts to pull downm files for important work, then you should really be storing that stuff in S3. And probably some other place you can switch to if something goes wrong.
Someone pushed code to master or some other specified pre-master branch. Jenkins pulls down, builds, runs tests, uploads artifacts to S3. That doesn't sound unrealistic or risky on the surface, modulo relying on both GH and S3 being up. Arguably you should be able to mirror on both an internal git repository somewhere, but GitHub is down infrequently enough that it's hard to justify that work + continuing costs if yo…
Earlier quoted context omitted.
That is Murphy trolling you very, very hard.
GitLab CEO here, I might be missing the joke here, GitLab is a decentralized solution you run on your own servers. Maybe you are confused with GitLab.com?
Earlier quoted context omitted.
I guess no-one else has deployment scripts that pull from github, just because you don't have them.
GitHub isn't made for that though, if you need scripts to pull downm files for important work, then you should really be storing that stuff in S3. And probably some other place you can switch to if something goes wrong.
It doesn't matter what kind of deployment you do. Even s3 has outages if the network between you and s3 bites the dust. Even if you deploy straight from the developer's workstation to the production server, you can have an outage - network splits, hardware failure, developer-with-commit-rights gets sick. Working around an outage means you're not working on the product, and that's a loss of productivity.
Earlier quoted context omitted.
That is Murphy trolling you very, very hard.
GitLab CEO here, I might be missing the joke here, GitLab is a decentralized solution you run on your own servers. Maybe you are confused with GitLab.com?
Earlier quoted context omitted.
GitLab CEO here, I might be missing the joke here, GitLab is a decentralized solution you run on your own servers. Maybe you are confused with GitLab.com?
Is it? Having it hosted on my servers doesn't make it decentralized: it's just centralized in a place I own. If the server(s) go down, same problem as Github (except I may be able to take action). Right?