Download sourcegraph

Author: g | 2025-04-23

Sourcegraph, free and safe download. Sourcegraph latest version: Sourcegraph - A Free Browser Extension. Sourcegraph is an open-source browser extensi Download Open on Sourcegraph [NL] ダウンロードOpen on Sourcegraph [JA] Download do Open on Sourcegraph [PT] Open on Sourcegraph for Google Chrome. Free. In English; V

Sourcegraph Machine Images - Sourcegraph docs

To all Sourcegraph featuresAll Sourcegraph features are avilable on Sourcegraph Cloud instances out-of-the-box, including but not limited to:Server-side Batch ChangesPrecise code navigation powered by auto-indexingCode Monitoring (including email delivery of notifications)Access restrictionsGranting your team application-level admin access to the instance.Configuring any IP-restrictions (e.g. VPN) and/or SSO restrictions to the instance.Monthly upgrades and maintenanceAutomatic monthly upgrades and maintenance.Regular reassessment of resource utilization based on your organization's unique usage to determine if costs can be reduced without impact to service. Additionally, you will automatically benefit from any committed use cloud provider discounts we receive.Health monitoring, support, and SLAsInstance performance and health monitored by our team's on-call engineers.Support and SLAs.Backup and restoreSOC2/CI-79Backup and restore capability is provided via automated snapshots.Frequency: Snapshots are produced daily.Retention period: Snapshots are kept for 90 days.Training, feedback, and engagementAs with any Sourcegraph enterprise customer, you will also receive support from us with:Installing code host and code review integrationsMonitoring and aggregating user feedbackUnderstanding usage statistics of your deploymentInternal rollout programs including:Holding company-wide or team-by-team training sessions (contact us for details)Helping the maintainers of your internal engineer onboarding add a session on SourcegraphHolding ongoing brown bag lunches to introduce new feature releasesAdvice and templates on how to introduce Sourcegraph to your engineering organizationManaged SMTPAll Sourcegraph Cloud instances are provisioned with a Sourcegraph-managed SMTP server through a third-party provider for transactional email delivery. Email capabilities power features like:Code Monitoring notificationsInviting other users to a Sourcegraph instance, or to an organization/team on a Sourcegraph instanceImportant updates to user accounts (for example, creation of API keys)For builtin authentication, password resets and email verificationBy default, emails will be sent from an @cloud.sourcegraph.com email address. To test email delivery, refer to sending a test email.To opt out of managed SMTP, please let your Sourcegraph Account team know when requesting a trial. You can also opt Out by overriding the managed email.address and email.smtp configuration with your own in site configuration. If you have specific requests for managed SMTP, please reach out regarding special requirements.To learn more about how the Sourcegraph team operates managed SMTP internally, refer to our handbook.Sourcegraph management accessSourcegraph management access is the ability for Sourcergaph employees to grant time-bound and audit-trailed UI access to Cloud instances in the events of instance maintenance, issue troubleshooting, and customer assistance. Customer consent is guaranteed prior to human accesses.All Sourcegraph Cloud instances have Sourcegraph management access enabled by default, and customers may request to disable by contacting your Sourcegraph contact.RequirementsBusinessA dedicated project manager who serves as the point of contact for the rollout process.A mutual non-disclosure agreement and any additional approvals or special status required to allow Sourcegraph to manage infrastructure access tokens (listed below).Acceptance of our Terms of Service for private instances or an enterprise contract.TechnicalA dedicated technical point of contact for the installation process.Tokens with read access to your code hosts (we will direct you on how to enter them).Keys, access tokens, or any other setup required to integrate your SSO (single sign-on) provider with Sourcegraph, as well as support from a member of your team with administrator access to your SSO provider to help set up and test the integration.LimitationThe Sourcegraph instance can only be accessible via a public IP. Running it in a private network and pairing it with your private network via site-to-site VPN or VPC Peering is not yet supported.Code hosts or user authentication providers running in a private network are not yet supported. They have to be publically available or they must allow incoming traffic from Sourcegraph-owned static IP addresses. We do not have proper support for other connectivity methods, e.g. site-to-site VPN, VPC peering, tunneling.Instances currently run only

Deploying Sourcegraph executors - Sourcegraph docs

Sourcegraph Cloud is a single-tenant cloud solution. Cloud instances are private, dedicated instances provisioned and managed by Sourcegraph. Sourcegraph Cloud was formerly known as managed instances.Sourcegraph provisions each instance in an isolated and secure cloud environment. Access is restricted to only your organization through your SSO provider of choice. Enterprise VPN is available upon request.Start a Sourcegraph Cloud trialUse the button above to sign up for a free 15-day trial of Sourcegraph Cloud. Please contact us if you have specific VPN requirements or you require a large deployment with >500 users, >1,000 repos, or monorepos >5 GB.Trial limitationsWe currently have a limited capacity of single-tenant cloud instances and are prioritizing organizations with more than 100 developers. When you request a trial, you will receive an email indicating the status of your request.If your organization has fewer than 100 developers, we recommend trying Sourcegraph self-hosted.If you're eligible for a cloud instance, you will receive a link to the instance URL once it's provisioned. This normally takes less than one hour during business hours. From there, we recommend using the onboarding checklist to set up your instance quickly.Trials last 15 days. When the end of the trial approaches, Sourcegraph's Customer Support team will check in with you to either help you set up a Cloud subscription or end your trial.Cloud subscriptionAs part of this service you will receive a number of benefits from our team, including:Initial setup, configuration, and cost estimationAdvising if managed instances are right for your organization.Initial resource estimations based on your organization & code size.Putting forward a transparent deployment & cost estimate plan.Your own example.sourcegraph.com domain with fully managed DNS & HTTPS.Hardware provisioning, software installation, and kernel configuration done for you.Direct assistance in:Adding repositories from all of your code hosts to SourcegraphIntegrating your single sign-on provider with SourcegraphConfiguring SourcegraphAccess. Sourcegraph, free and safe download. Sourcegraph latest version: Sourcegraph - A Free Browser Extension. Sourcegraph is an open-source browser extensi

Install Sourcegraph on DigitalOcean - Sourcegraph docs

SyncingUser-level permissions syncing is supported for Azure DevOps code host connections. Here is the list of prerequisites:Configure Azure DevOps as an OAuth provider by consulting this pageNext verify that users can now sign up / login to your Sourcegraph instance with your Azure DevOps OAuth providerSet the following in your Azure DevOps code host connection:{ // ... "enforcePermissions": true}For each Azure DevOps organization that is part of the orgs or projects list in the code host configuration, enable Third-party application access via OAuth from Organization settings > Security > PoliciesNOTE: We do not support preemptive permissions syncing at this point. Once a user signs up / logins to Sourcegraph with their Azure DevOps account, Sourcegraph uses the authenticated access_token to calculate permissions by listing the organizations and projects that the user has access to. As a result, immediately after signing up user level permissions may not be 100% up to date. Users are advised to wait for an initial permissions sync to complete, whose status they may check from the Permissions tab under their account settings page. Alternatively they may also trigger a permissions sync for their account from the same page.Since permissions are already enforced by setting enforcePermission in the code host configuration, even though user permissions may not have synced completely, users will not have access to any repositories that they cannot access on Azure DevOps. As the user permissions sync progresses and eventually completes, they will be able to access the complete set of repositories on Sourcegraph that they can already access on Azure DevOps.Rate limitsWhen Sourcegraph hits a rate limit imposed by Azure DevOps, Sourcegraph waits the appropriate amount of time specified by the code host before retrying the request. You can read more about how Azure DevOps imposes rate limits here. And less likely to time out.Share Notebooks with your organizationNotebooks are now shareable within organizations. Previously, you could only share Notebooks with your entire instance (or share them publicly, in the case of Sourcegraph Cloud). This update allows you to create Notebooks with specific relevance to your organization, such as documentation of preferred engineering patterns or anti-patterns. Your organization's shared Notebooks will now show up in their own tabs on the Notebooks home page.Import and export Notebooks as MarkdownNotebooks can now be created by uploading a Markdown file, so if you're already working with Markdown documentation files, you can simply upload those files to add Sourcegraph snippets and turn them into full-fledged Notebooks. You can also export Notebooks to Markdown, allowing you to turn Sourcegraph Notebooks into repo-based Markdown files.Create search contexts with the new UIThe search contexts creation UI has received visual tweaks, making it easier to understand if you're using search queries or JSON to define your contexts. We've also added guidance on valid expressions for query-based contexts to make the creation process clearer.Upgrading Sourcegraph is now easier with the new migrator servicePreviously, failed database migrations were a common cause of pain when upgrading Sourcegraph. We've introduced a new migrator service and made several changes to make these database failures far less common. You can read more here.‍

Sourcegraph with Docker Compose - Sourcegraph docs

Site admins can sync Git repositories hosted on Azure DevOps with Sourcegraph so that users can search and navigate the repositories.To connect Azure DevOps to Sourcegraph, create a personal access token from your user settings page by following the below steps:Navigate to the Personal Access Tokens page from the user settings.Click on New Token.Under the Organization menu, select All accessible organizations to allow access to all organizations. This is required to be able to perform connection checks from the code host page and to sync repositories from multiple organizations. Alternatively, site admins may also create a unique user that has access to only the selective organizations that they would like to sync with Sourcegraph. However the token being created must have access to All accessible organizations as shown below.Select the following scopes:Code (Read)Project and TeamUser ProfileNext, configure the code host connection by following the next steps:Go to Site admin > Manage code hosts > Add repositories.Select Azure DevOps.Provide a configuration for the Azure DevOps code host connection. Here is an example configuration:{ "url": " "username": "", "token": "", "projects": ["org1/project1"], "orgs": ["org2"]}Select Add repositories.Repository syncingCurrently, all repositories belonging to the configured organizations/projects will be synced.In addition, you may exclude one or more repositories by setting the exclude field in the code host connection.HTTPS cloningSourcegraph clones repositories from Azure DevOps via HTTP(S), using the username and token required fields you provide in the configuration.ConfigurationAzure DevOps connections support the following configuration options, which are specified in the JSON editor in the site admin "Manage code hosts" area.admin/code_hosts/azuredevops.schema.json{ // A flag to enforce Azure DevOps repository access permissions "enforcePermissions": false, // A list of repositories to never mirror from Azure DevOps Services. "exclude": null, // Other example values: // - [ // { // "name": "myorg/myproject/myrepo" // } // ] // - [ // { // "name": "myorg/myproject/myrepo" // }, // { // "name": "myorg/myproject/myotherrepo" // }, // { // "pattern": "^topsecretproject/.*" // } // ] // The type of Git URLs to use for cloning and fetching Git repositories. // // If "http", Sourcegraph will access repositories using Git URLs of the form http(s)://dev.azure.com/myrepo.git. // // If "ssh", Sourcegraph will access repositories using Git URLs of the form [email protected]:v3/myrepo. See the documentation for how to provide SSH private keys and known_hosts: "gitURLType": "http", // An array of organization names identifying Azure DevOps organizations whose repositories should be mirrored on Sourcegraph. "orgs": null, // Other example values: // - ["name"] // - [ // "kubernetes", // "golang", // "facebook" // ] // An array of projects "org/project" strings specifying which Azure DevOps projects' repositories should be mirrored on Sourcegraph. "projects": null, // Other example values: // - ["org/project"] // The Personal Access Token associated with the Azure DevOps username used for authentication. "token": null, // URL for Azure DevOps Services, set to "url": null, // Other example values: // - " // A username for authentication with the Azure DevOps code host. "username": null}WebhooksPlease consult this page in order to configure webhooks.Permissions

GitHub - sourcegraph/sourcegraph-public-snapshot:

Mounted volumetmp_config=$(mktemp)trap "rm -f ${tmp_config}" EXITcat "${DOCKER_DAEMON_CONFIG_FILE}" | jq --arg DATA_ROOT "${DOCKER_DATA_ROOT}" '.["data-root"]=$DATA_ROOT' > "${tmp_config}"cat "${tmp_config}" > "${DOCKER_DAEMON_CONFIG_FILE}"# Restart Docker daemon to pick up new changessystemctl restart --now docker# Install Docker Composecurl -L " -s)-$(uname -m)" -o /usr/local/bin/docker-composechmod +x /usr/local/bin/docker-composecurl -L " -o /etc/bash_completion.d/docker-compose# Start Sourcegraph with Docker Composecd "${DEPLOY_SOURCEGRAPH_DOCKER_CHECKOUT}"/docker-composedocker-compose up -d --remove-orphansNOTE: If you're deploying a production instance, we recommend forking the deployment configuration repository to track any customizations you make to the deployment config. If you do so, you'll want to update the startup script you pasted from above to refer to the clone URL and revision of your fork:DEPLOY_SOURCEGRAPH_DOCKER_FORK_CLONE_URL: The Git clone URL of your deployment repository. If it is a private repository, please check with your code host on how to generate a URL for cloning private repositoryDEPLOY_SOURCEGRAPH_DOCKER_FORK_REVISION: The revision (branch) in your fork containing the customizations, typically "release"DeployClick Launch Instance in the Summary Section on the right to launch the EC2 node running Sourcegraph.In your web browser, navigate to the public IP address assigned to the EC2 node. (Look for the IPv4 Public IP value in your EC2 instance page under the Description panel.) It may take a few minutes for the instance to finish initializing before Sourcegraph becomes accessible.You can monitor the setup process by SSHing into the instance to run the following diagnostic commands:# Follow the status of the startup scripttail -f /var/log/cloud-init-output.log# Once installation is completed, check the health of the "sourcegraph-frontend" containerdocker ps --filter="name=sourcegraph-frontend-0"NOTE: If you have configured a DNS entry for the IP, please ensure to update externalURL in your Sourcegraph instance's Site Configuration to reflect thatUpgradeSee the Docker Compose upgrade docs.Storage and BackupsData is persisted within a Docker volume as defined in the deployment repository. The startup script configures Docker using a daemon configuration file to store all the data on the attached data volume, which is mounted at /mnt/docker-data, where volumes are stored within /mnt/docker-data/volumes.There are two, non-mutually-exclusive ways to back up data:Snapshot the entire /mnt/docker-data EBS volume on an automatic, scheduled basis.Use AWS RDS for PostgreSQL instead of the Dockerized PostgreSQL instance included by default. All data from Sourcegraph is derivable from the data stored in this database. Note, however, that it may take awhile to reclone repositories and rebuild indices afresh. If you require a faster restoration process, we recommend also snapshotting the EBS volume. (Recommended)Other resourcesHTTP and HTTPS/SSL configurationSite Administration Quickstart. Sourcegraph, free and safe download. Sourcegraph latest version: Sourcegraph - A Free Browser Extension. Sourcegraph is an open-source browser extensi

Sourcegraph Cody Gateway - Sourcegraph docs

On Google Cloud Platform in the us-central1 region. Other regions and cloud providers (such as AWS or Azure) are not yet supported.Some configuration options are managed by Sourcegrpah and cannot be override by customers, e.g. feature flags, experimental features.SecurityYour managed instance will be accessible over HTTPS/TLS, provide storage volumes that are encrypted at rest, and have access restricted to only your team through your enterprise VPN and/or internal SSO (single sign-on provider) of choice.For all managed instances, we will provide security capabilities from Cloudflare such as WAF and rate-limiting to protect your instance from malicious traffic.Your instance will be hosted in isolated Google Cloud infrastructure. See our employee handbook to learn more about the cloud architecture we use. Both your team and limited Sourcegraph personnel will have application-level administrator access to the instance.Only essential Sourcegraph personnel will have access to the instance, server, code, and any other sensitive materials, such as tokens or keys. The employees or contractors with access are bound by the same terms as Sourcegraph itself. Learn more in our security policies for Sourcegraph Cloud or contact us with any questions or concerns. You may also request a copy of our SOC 2 Report on our security portal.Accommodating special requirementsWe may be able to support special requests (network access policies, infrastructure requirements, custom version control systems, etc.) with additional time, support, and fees. Contact us to discuss any special requirements you may have.