
<EmbeddedYoutubeVideo id="_dGkagmwZqU" />

## Transcript

Reading and searching open source code really helps me understand my project dependencies, it helps me optimize my code, and it helps me figure out how to best implement a new feature. I also find that real-life examples in open source code help new developers learn effectively, and can encourage them to become contributors to open source, too!

I’m Lisa, Director of Developer Education at Sourcegraph, and the team here is working on indexing every open source repository on GitHub and GitLab with at least one star. You, too, can add open source repositories to Sourcegraph cloud to help others be able to search across many repos. I’ll walk you through the process.

### Manage repositories from your Sourcegraph cloud account

First, you’ll need to have an account on Sourcegraph cloud. Once you sign up or login, you’ll click on your user icon on the top right corner of the page. From the drop-down menu, click on **Repositories**. If you have repositories on your account already, click through to **Manage Repositories**.

From here you will be able to connect your own repositories to Sourcegraph, but for now, we’re going to scroll down to **Other public repositories**. We’ll click on the checkbox **Sync specific public repositories by URL**. 

### Add links to public repositories

In the box, you can add links to these public repos, whether you contribute to the project or not. These are probably open source projects that you care about. Add one URL per line with no separating characters other than the `ENTER` key.

I have identified two projects that I would like to have Sourcegraph index. One of them is this [Cloud Haiku repository](https://github.com/do-community/cloud_haiku), I’ll go through, copy, and paste. Then I’ll hit `ENTER` to start a new line — don’t put any characters in between. Then I’ll go through and copy paste for the second repository, which is an [archive of computational history](https://github.com/dhmit/computation_hist). When you are satisfied with the repositories that you have added, you can click the **Save** button below. You can always add more repos later!

### Verify that repositories have been added

Once I've clicked on **Save** I should see that these repositories are loaded in, preloaded to my account. And now I can actually check to make sure that Sourcegraph has in fact indexed these repositories by looking for a specific string that I know exists in one of them. So, first I’ll identify that string and share that with you really quickly.

In this Cloud Haiku repository, there is this line, “Like the octopuses’ minds” and a break. I suspect this is not a common line in open source repositories. So what I’m going to do next is open a private or incognito window and then I’m going to search Sourcegraph for this specific line to make sure that it is globally available. 

Now I have my private window, I’m going to go to sourcegraph.com and I’m going to search that line that I mentioned before. So this is “Like the octopuses’ minds” with a break. I am in the context:global search, I am not logged in, and I am going to hit the **Search**. So here we see that there are actually a few instances of this line, but it is limited to this repo. This repo is the one that I just added, so we know that that repository has been indexed by Sourcegraph. Now, even an anonymous user, not logged in, will be able to access the open source repos that I just added. 

Looking forward to seeing the open source repositories that you’ll add to Sourcegraph. Happy coding and happy searching through open source!

## Related links

To learn more about Sourcegraph cloud, check out our full written tutorial on [How to add open source software projects to Sourcegraph cloud](https://learn.sourcegraph.com/how-to-add-open-source-software-projects-to-sourcegraph-cloud) and our tutorial on [How to add private code repositories to Sourcegraph cloud](https://learn.sourcegraph.com/how-to-add-private-code-repositories-to-sourcegraph).


Sourcegraph is indexing open source

Find out how to add open source repos to Sourcegraph cloud so you can search across all the code you care about.

How to add open source software to Sourcegraph cloud (video)


<EmbeddedYoutubeVideo id="f4jEXHn3T74" />

## Transcript

Sourcegraph lets you search over the many repositories of public code that we're indexing on GitHub and GitLab.

If you want to search your own private repositories, you can now do that too by adding your private repositories to your Sourcegraph account.

---

**NOTE**:

_Searching private code is currently in Public Beta._

---

When you add private code to Sourcegraph, it remains private. So it won't show up in anybody else's search results, and you’ll only see it when you're logged in with your account, and no Sourcegraph employee can ever see any private code

My name is Marek, I'm an engineer at Sourcegraph, and I'm going to show you how you can add your own private repositories to Sourcegraph and start searching over your own code.

To start, open the menu in the top right, and go to “Repositories”. You can also find repositories on the “Settings” page. The “Repositories” page is where you can manage any synced repositories that you have. But first, we'll have to connect a code host. So I'll click on “Connect code hosts” to do that.

I happen to have all my repositories on GitHub, so that's the code host that I'd like to connect. I'll do that by clicking the connect button. In order to connect my GitHub account with Sourcegraph, I have to authorize by clicking on the green button here.

Now that I've connected GitHub, I can go to the next step and actually select the repositories that I want to add. And I'll do that by clicking add to your repositories. Now I want to select specific repositories to add. So I'll click on “Sync selected repositories”. And this will give me a list of my repositories that are available. I'm interested in two private repositories that I want to have in Sourcegraph, so I'll select these two. And then I'll click “Save” at the bottom.

Once my repositories are synced, I see them here on this page. I can now go back to the “Search” page to start doing some searches. On the search page, I can now search for code in my private repositories. I can specify that I'm interested in my own private repositories by switching the search context. The search context drop down on the left allows me to do that.

The `global` context is the default context. And that searches over all of the public repositories that have already been indexed by Sourcegraph. The context below is my own username. So, that refers to all the repositories that I've personally added to Sourcegraph. By selecting my username here, I'm going to switch to the context that searches specifically over the code that I added.

Now I can try this out with a search that includes a keyword that I know exists in my private repositories. On the results page, I'm getting results that are coming directly from these repositories that I've added. So now I know that I'm searching over my own private code. No one else will see these results because they are private, so I'm the only user who will be getting access to this repository.

I can click on search results and start browsing my codebase on Sourcegraph. This lets me use Sourcegraph features, like code intelligence when I hover over a token, and find references that show me where a particular symbol is being used.

If you want to learn more about the kinds of things that you can search for, and how to use different search features like filters and types of search, I invite you to take a look at the [documentation](https://docs.sourcegraph.com/) and learn more there.

_For a full tutorial, read "[How to add private code repositories to Sourcegraph cloud](/how-to-add-private-code-repositories-to-sourcegraph)."_

Connecting private software repos to your Sourcegraph cloud account

Learn about connecting your private code repositories to Sourcegraph cloud and searching your own code.

How to add private code repositories to Sourcegraph cloud (video)


<EmbeddedYoutubeVideo id="r2CpLe1h89I" />

## Related links

- [Sourcegraph cloud code search](https://sourcegraph.com/search)
- [Sourcegraph docs](https://docs.sourcegraph.com)
- [Read about literal search patterns](/how-to-search-code-with-sourcegraph-using-literal-patterns)
- [Watch: Three Ways to Search with Sourcegraph (Video)](/three-ways-to-search-code-with-sourcegraph)

## Transcript

Have you ever been faced with an error message and spent a really long time trying to figure out where it was coming from?

My name is Marek. I'm an engineer at Sourcegraph. And I'm going to share with you my own error message story.

A few months ago, I was working on a browser extension in Chrome. And I started seeing this unfamiliar message that I hadn't seen before. It looked something like this. "Extension context invalidated." What does that even mean? I didn't know where this error was being thrown. And I didn't know where to start looking. We were loading code from a few different repositories into this browser extension bundle. So I wasn't sure where this was coming from.

At first, I tried doing some searches right in my editor to try to find an exact match for the text of this error message. But I got nowhere. I didn't find any matches in the repository that I had open at all.

So I'll show you how I actually used Sourcegraph to do a code search that helped me find the answer. By default, Sourcegraph searches for code in literal search mode. That means it looks for an exact match. For an error message, this is pretty convenient. And I can show you by pasting that error message directly into the search box. Now, I don't need to surround this search with quotes, because literal search will by default already search for the entire thing.

As soon as I get results, there's a hint about where this is coming from. And that's in the name of this repository that I'm getting. So I'm seeing chromium as the repository. This gives me a hint that this is part of the Chrome browser itself and actually not at all a part of the code base that I was working on. The chromium source code is in a public GitHub repository, and Sourcegraph searches over public code. This helped me save a lot of time and a lot of struggle to get to the bottom of this error message. And it turns out it was an issue with the way that the browser extension was being reloaded for development.

Sourcegraph's default search mode is great for error messages like this, but if you're looking for patterns, you can also use regular expressions. And you can also use structural search. So you can take a look at our documentation to learn more about that.


Finding software error messages with Sourcegraph universal code search

Learn about finding error messages in your code with Sourcegraph.

How to find error messages with Sourcegraph (video)


<EmbeddedYoutubeVideo id="u_SmtOejFkg" />

## Transcript

Hi, I’m Lisa, Director of Developer Education at Sourcegraph, and I’m going to walk you through installing an instance of Sourcegraph on a Linux Ubuntu 20.04 cloud server. We’ll be using a [DigitalOcean Droplet](https://www.digitalocean.com/) with the recommended 4GB of RAM and 2 CPUs for this demo.

Sourcegraph is a tool that can allow you to search the code that is important to you. You can try out [Sourcegraph cloud](https://sourcegraph.com) on the web to search through open source repositories right now. In this video, we’ll discuss an installation instead. If you would like to use Sourcegraph to access local code, server-side code, or code from several different code hosts, an instance like this may be the right fit for you. 

Installing Sourcegraph with Docker is appropriate for testing and fairly quick to set up. If you would like to use Sourcegraph in a production environment, you should follow our documentation on installing [Sourcegraph with Docker Compose](https://docs.sourcegraph.com/admin/install/docker-compose) on a single node, or on a [Kubernetes cluster](https://docs.sourcegraph.com/admin/install/kubernetes). Let’s get started.

### Server setup

I set up this DigitalOcean Droplet with a [non-root sudo user](https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-20-04), Sammy. First, I want to make sure that everything is up to date by running the following command. 

```sh
sudo apt update
```

I’ll enter the password when prompted to use my sudo user. 

Now we know everything is up to date, and I can move ahead to installing Docker. I am going to use the snap package manager, so let’s make sure that’s installed. 

```sh
sudo apt install snapd
```

With that installed and set up, I want to make sure I have the core libraries I need, so I’ll run sudo snap install core.

```sh
sudo snap install core
```

Now that snap is installed, we’ll install Docker using snap.
```sh
sudo snap install docker
```

Now that we have Docker installed, we can move on to installing Sourcegraph with Docker.

### Installing Sourcegraph

We have a multi-line Docker command that we need to run, and we’ll demonstrate how to do that here. We’ll be using the sudo command and it’s going to take a little bit. 

We’ll run the following Docker run command:

```sh
sudo docker run -d --publish 80:7080 --publish 443:7443 \
--restart unless-stopped \
--volume /root/.sourcegraph/config:/etc/sourcegraph \
--volume /root/.sourcegraph/data:/var/opt/sourcegraph \
sourcegraph/server:3.30.4
```

This command is telling your server to install and run Sourcegraph, binding port 7080 to TCP port 80 of your server; it’s calling up the relevant files from the Docker image of Sourcegraph. Since this is a cloud server, we can keep our instance of Sourcegraph up and running even after closing our Terminal connection to the server, and that was one of the details we pass to this command. It is also setting up a store for your Sourcegraph data.

### Verify installation

With our installation complete, we can navigate to our web browser of choice and enter the IP address of the server with port 80. We’ll press enter and get the feedback that the installation is complete. We have validated that we have installed Sourcegraph with Docker on this Ubuntu server. At this point, you can create your account. 

Now we have verified that everything is working. For next steps, head on over to [Sourcegraph Learn](https://learn.sourcegraph.com). Or go ahead to read through our [documentation](https://docs.sourcegraph.com) to read more about Sourcegraph, the different installation methods, and how you can effectively search all of your code. Happy coding and happy searching!

_For a longer-form written tutorial of this guide, read “[How to install Sourcegraph on Linux with Docker](https://learn.sourcegraph.com/how-to-install-sourcegraph-on-linux-with-docker).”_


Test a Sourcegraph installation with Docker on DigitalOcean to search your code

Install Sourcegraph onto a DigitalOcean Ubuntu cloud server with Docker.

How to install Sourcegraph with Docker on a Linux cloud server (video)


<EmbeddedYoutubeVideo id="1qa3dyzJ3Go" />

## Learn more

- Install the [Sourcegraph browser extension](https://docs.sourcegraph.com/integration/browser_extension)
- Learn about the [“Git Extras” Sourcegraph extension](https://sourcegraph.com/extensions/sourcegraph/git-extras)
- Learn about [Sourcegraph extensions for your code editor](https://sourcegraph.com/extensions?category=Code+editors)
- Watch the video: [Open-in-editor Sourcegraph extension](https://youtu.be/Maa6jCaoZFw)

## Transcript

As a developer, I spend most of my time either in my code editor — for me, usually that's VS Code — or on GitHub, reviewing pull requests or browsing repositories. Whenever I switch between different tools, I don't like it when I lose my train of thought, and I don't like it when I lose the context of the files that I'm working on.

My name is Marek. I'm an engineer at Sourcegraph. Let me show you how I use Sourcegraph on a day-to-day basis in my own work in a way that helps me read and understand code better without losing context as I switch between tools.

My starting point is usually on GitHub. Often, I'm reviewing a pull request or just trying to understand how some piece of code works. By installing the Sourcegraph browser extension, I can have Sourcegraph features right in Github. Here, by hovering over a symbol in Github, I'm able to get Sourcegraph code intelligence right where I am.

Now, I can use the **Find references** button here to jump into Sourcegraph and start exploring the code. The bottom panel is the **References** panel, and it's listing all the places where this particular token is being used in this codebase. If I want to learn more about the context of this particular piece of code, I can use the **Git blame** action to show the history of the changes made to it and why they were made.

Often my workflow involves collaborating with other engineers. I can copy this link to this particular place in the code and share it with my colleagues on Slack. Because this is a public repository, Sourcegraph generates a preview image that helps me show what I'm linking to.

Typically after I've explored and learned about some code, my next step is to jump into my editor and make some changes. I can do that with the **Open in VS Code** action here. Now I've already configured Sourcegraph to point to my local repository. By clicking the button, I'm taken to my editor, and I'm able to start working right away.

Sometimes while I'm coding, I'm curious to learn more about a particular symbol that's in the code, like this `configurationResolver`. With the Sourcegraph VS Code extension, I can jump right into a Sourcegraph search and find out more.

I probably switch between my editor, GitHub and Sourcegraph multiple times a day. So I love having integrations that make that as smooth as possible. Now, let me show you how you can set up these integrations for your own workflow.

First, install the Sourcegraph browser extension. It's available for Chrome, Firefox, and Safari. Next, install the Sourcegraph extension for Visual Studio Code. And finally, to be able to jump from Sourcegraph right into your editor, go to the Sourcegraph extensions page and go to the **Code editors** section, you'll find our integrations for VS Code as well as several other editors. And you just have to add the local directory where you have your repositories cloned in the Sourcegraph settings for this to work.


Integrating Sourcegraph into code host and editor workflows

Learn how to switch between your code host (like GitHub), code editor or IDE (like VS Code), and Sourcegraph.

How to integrate Sourcegraph into your workflows


<EmbeddedYoutubeVideo id="XLfE2YuRwvw" />

## In this video

- Literal search ([tutorial](/how-to-search-code-with-sourcegraph-using-literal-patterns), [docs](https://docs.sourcegraph.com/code_search/reference/queries#literal-search-default))
- Regular expression search ([tutorial](/how-to-search-with-sourcegraph-using-regular-expression-patterns), ([docs](https://docs.sourcegraph.com/code_search/reference/queries#regular-expression-search))
- Structural search ([tutorial](how-to-search-with-sourcegraph-using-structural-patterns), [docs](https://docs.sourcegraph.com/code_search/reference/structural))

## Transcript

Hi, my name is Marek. And I'm going to tell you about the different ways that you can search with Sourcegraph. So, Sourcegraph supports three different search modes: literal search, regular expressions, and structural search. I'll tell you a little bit about each one and how you can use them.

By default Sourcegraph searches in literal search mode. This is useful when you're looking to find an exact match. For example, if you're looking for a function name, or a variable name, or an exact string in your code. Let's say that I'm looking for a function called "ReadFile". I can search for directly, and it'll find exact matches. But I can also narrow this down by saying I'm only looking for results in the Go language. So I'm getting results from a variety of different repositories that match the exact query "ReadFile".

Sometimes you're not looking for an exact match, but you're looking for a pattern. Regular Expression search can help you find patterns in you in your code. Suppose I'm looking for CSS colors that are defined as six character hex codes. I know that the CSS color code format can be defined as a regular expression. And it starts with a hash symbol, followed by characters in the range between zero and nine and between A and F. And that's repeated six times. So I've just written that pattern as a regular expression. And I can also add the keyword that narrows this down to only CSS files. And I'll enable regular expression mode for this one. So now I'm getting results that are matching anything that looks like a hex color code. I could expand on this query by adding that I'm only looking for cases where background color is the property that's been set. So now with this search query, I will see only results that match background color, followed by a hex code.

Regular expressions are useful when you're looking for a pattern in your code. But sometimes you want to take into account the actual structure of your code. This is where structural search can help. Let me show you an example. I'll enable structural search. And let's say for example, I'm looking for a function call to a function called "WriteFile". And I know that the instance that I'm looking for is where the first argument is called "path". But I wanted that to match any other arguments after that. So I'm going to use the three dots that match any other arguments in a structural search. I'm also going to restrict this only to Go files. So now I'm getting matches that correspond to function calls where the first argument is path. But the other arguments could be anything. Notice that this is using matching brackets. So even if there are expressions in this function call that contain other brackets, the search will still take that into account and correctly match the entire function call.

Now, in some cases, I see that the constant that's used as the last argument here is relevant. So I may want to narrow the search down and actually search for only the calls where a particular constant is being used as the final argument here. So if I redo this search, the now I'm seeing that I'm getting results for this function call where the first argument is the one I've specified, as well as the last one, but I'm matching any arguments in between, and they can be any expressions in the code.

So I've given you an overview of the three different ways that you can search with Sourcegraph. With each of these modes, you can also filter down by a variety of criteria like programming language, repositories, and file names and a lot of other things too. So you can look at our search query docs to learn more.


Searching code with Sourcegraph using literal patterns, regular expressions, and structural search

Demo of how to search code three different ways with Sourcegraph

How to add open source software to Sourcegraph cloud (video)

How to add private code repositories to Sourcegraph cloud (video)

How to find error messages with Sourcegraph (video)

How to install Sourcegraph with Docker on a Linux cloud server (video)

How to integrate Sourcegraph into your workflows

Three ways to search code with Sourcegraph