Sourcegraph is a self-hosted code search and intelligence tool that helps developers find, review, understand, and debug code. Organizations that switch from OpenGrok to Sourcegraph typically cite the following reasons:
Both Sourcegraph and OpenGrok are self-hosted, and your code never touches Sourcegraph’s (or Oracle’s) servers.
One key feature of OpenGrok that Sourcegraph lacks is support for Subversion, Mercurial, CVS, and Perforce repositories. Sourcegraph only supports Git repositories.
Oracle releases OpenGrok under the open-source CDDL license and does not (currently) have any monetization plans for it. Sourcegraph is a commercial product, with a free tier and paid premium features available.
Every organization’s needs are different. Install and use Sourcegraph for free to see if it’s right for your organization.
For more information about Sourcegraph, see:
Migrating from Oracle OpenGrok to Sourcegraph consists of 4 steps:
The following sections guide you through the migration process.
You can deploy Sourcegraph in 2 ways:
The fastest way to try it is to run Sourcegraph Server locally with the quickstart instructions.
Choose a deployment option and follow the instructions. When you’ve signed into your Sourcegraph instance as a site admin, continue to the next section.
Sourcegraph and Oracle OpenGrok differ in how they access repositories:
SRC_ROOTpath on disk. You place repositories there and configure the sync.py tool to fetch updates.
Sourcegraph’s “active” model lets it:
git pushed data);
Sourcegraph also partially supports the “passive” model like OpenGrok, but it’s not recommended because you lose these benefits. To use it anyway, see “Add repositories already cloned to disk”.
To configure which repositories Sourcegraph will make available for searching and browsing:
When you’ve added repositories and confirmed that you can search and browse them, continue to the next section.
Like Oracle OpenGrok, Sourcegraph is self-hosted. You control who can access it. Sourcegraph supports many user authentication and security options:
After you’ve set Sourcegraph up, it’s time to share it with your organization. Successful roll-outs of Sourcegraph typically involve the following steps.
I set up Sourcegraph as a possible alternative to OpenGrok for code search. [Describe the perceived benefits vs. OpenGrok that are most relevant to your organization.]
- Search: [URL to an example search results page on your Sourcegraph instance]
- Code browsing: [URL to a code file page on your Sourcegraph instance]
[Include screenshots of your Sourcegraph instance here]
Post feedback at https://github.com/sourcegraph/sourcegraph [change if needed]
If there are any blockers preventing your organization from switching to Sourcegraph, we’d love to hear from you so we can address them.