You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This document describes the process to update a Docker Compose Sourcegraph instance. If you are unfamiliar with sourcegraph versioning or releases see our [general concepts documentation](/admin/updates/).
# Install single-container Sourcegraph with Docker on AWS
2
4
3
5
This tutorial shows you how to deploy [single-container Sourcegraph with Docker](/admin/deploy/docker-single-container/) to a single EC2 instance on AWS.
@@ -33,7 +35,7 @@ This tutorial shows you how to deploy [single-container Sourcegraph with Docker]
33
35
- usermod -a -G docker ec2-user
34
36
35
37
# Install and run Sourcegraph. Restart the container upon subsequent reboots
# Install single-container Sourcegraph with Docker on DigitalOcean
2
4
3
5
This tutorial shows you how to deploy [single-container Sourcegraph with Docker](/admin/deploy/docker-single-container/) to a single node running on DigitalOcean.
@@ -17,7 +19,7 @@ This tutorial shows you how to deploy [single-container Sourcegraph with Docker]
# Install single-container Sourcegraph with Docker on Google Cloud
2
4
3
5
This tutorial shows you how to deploy [single-container Sourcegraph with Docker](/admin/deploy/docker-single-container/) to a single node running on Google Cloud.
@@ -23,7 +25,7 @@ This tutorial shows you how to deploy [single-container Sourcegraph with Docker]
The Docker Single Container deployment type is a way to very quickly get an instance of Sourcegraph set up locally to experiment with many of its features. However, it is **not recommended** for a production instance, and **has limitations** depending on the OS you are deploying to, as well as the associated resources. See the [troubleshooting section](#troubleshooting) for additional information.
Once the server is ready (logo is displayed in the terminal), navigate to the hostname or IP address on port `7080`. Create the admin account, then you'll be guided through setting up Sourcegraph for code searching and navigation.
@@ -46,7 +48,7 @@ For example, to mount a `.gitconfig`, create a file `/mnt/sourcegraph/config/git
46
48
Alternatively you can create a new Docker image which inherits from Sourcegraph and then mutates the environment:
47
49
48
50
```dockerfile
49
-
FROM sourcegraph/server:5.6.2535
51
+
FROM sourcegraph/server:{CURRENT_VERSION_NO_V}
50
52
51
53
COPY gitconfig /etc/gitconfig
52
54
COPY ssh /root/.ssh
@@ -87,7 +89,7 @@ This is required to [collect debug data](/admin/pprof).
87
89
The docker run command for single-container Sourcegraph needs an additional publish flag to expose the debug port:
If Sourcegraph is deployed to a remote server, then access via an SSH tunnel using a tool
@@ -105,7 +107,7 @@ Add the following to your docker run command:
105
107
```sh
106
108
$ docker run [...]
107
109
-e (YOUR CODE)
108
-
sourcegraph/server:5.6.2535
110
+
sourcegraph/server:{CURRENT_VERSION_NO_V}
109
111
```
110
112
111
113
## Operation
@@ -254,7 +256,7 @@ Sourcegraph can be **tested** on Windows 10 using roughly the same steps provide
254
256
1.[Install Docker for Windows](https://docs.docker.com/docker-for-windows/install/)
255
257
2. Using a command prompt, follow the same [installation steps provided above](#install-sourcegraph-with-docker) but remove the `--volume` arguments. For example by pasting this:
Sourcegraph should now be available via the address set. Browsing to the url should now provide access to the Sourcegraph UI to create the initial administrator account.
@@ -79,7 +81,7 @@ Example overrides can be found in the [examples](https://github.com/sourcegraph/
79
81
80
82
Providing the override file to Helm is done with the inclusion of the values flag and the name of the file:
It will take around 10 minutes for the load balancer to be fully ready, you may check on the status and obtain the load balancer IP using the following command:
It will take some time for the load balancer to be fully ready, use the following to check on the status and obtain the load balancer address (once available):
It may take some time before your ingress is up and ready to proceed. Depending on how your Ingress Controller works, you may be able to check on its status and obtain the public address of your Ingress using:
Sourcegraph [Google Compute Engine (GCE) Images](https://cloud.google.com/compute/docs/images) allow you to quickly deploy a production-ready Sourcegraph instance tuned to your organization's scale in just a few clicks.
@@ -143,7 +145,7 @@ SSH into the VM as user `sourcegraph` and run the following command:
143
145
144
146
```bash
145
147
# Please update the version number according to the upgrade notes
You can use your own PostgreSQL v12+ server with Sourcegraph if you wish. For example, you may prefer this if you already have existing backup infrastructure around your own PostgreSQL server, wish to use Amazon RDS, etc.
@@ -53,7 +55,7 @@ docker run [...]
53
55
-e CODEINTEL_PGPASSWORD=secret
54
56
-e CODEINTEL_PGDATABASE=sourcegraph-codeintel
55
57
-e CODEINTEL_PGSSLMODE=require
56
-
sourcegraph/server:5.6.2535
58
+
sourcegraph/server:{CURRENT_VERSION_NO_V}
57
59
```
58
60
59
61
### Docker Compose
@@ -148,7 +150,7 @@ When [PgBouncer] is used, we need to include `statement_cache_mode=describe` in
# Adding SSL (HTTPS) to Sourcegraph with a self-signed certificate
2
4
3
5
This is for external Sourcegraph instances that need a self-signed certificate because they don't yet have a certificate from a [globally trusted Certificate Authority (CA)](https://en.wikipedia.org/wiki/Certificate_authority#Providers). It includes how to get the self-signed certificate trusted by your browser.
0 commit comments