|
|
|
|
|
|
by sdesol
3780 days ago
|
|
|
You have a valid point, but what isn't obvious is my technology isn't really dependent on GitHub. The only thing that can cripple me is Git becoming less vogue. There are two parts to my technology: - There is the front end which is 100% JavaScript and this is important since it allows me to build on top of existing web solutions like GitHub - There is the indexing engine which was insanely hard to develop and is what makes my solution unique. I've attached some screenshots that shows how I'm using my JavaScript technology to integrate with Bitbucket here: http://imgur.com/a/7AME6 I've also uploaded some screenshots that shows how I monitor/manage indexing. Right now, my indexing engine can easily process 10s of thousands of repositories with millions of branches on a single machine. The indexers are designed to scale horizontally and developing them was insanely hard and that's what I'm really selling. There is a reason why GitHub stopped indexing commits a few years ago. And why Bitbucket has a 5 year old ticket about code searching: https://bitbucket.org/site/master/issues/2874/ability-to-sea... Should the worst happen and I get shut out by GitHub and Atlassian, there is always GitLab, Gogs, etc. For now, I'm more than happy to build on top of GitHub and ensuring my solution works with their Enterprise offering. |
|
|
https://developer.atlassian.com/bitbucket/guides/getting-sta...
The browser extension is nifty, but Connect provides a proper API for embedding custom views in the Bitbucket UI if you want something a bit more robust (i.e. it will still work even if we decide to change the DOM at some point in the future).