mirror of
https://github.com/sourcegraph/sourcegraph.git
synced 2026-02-06 18:31:54 +00:00
fc76a9c675
Apparently VS Code's Python support uses port 9000, so as long as we use it most VS Code Python devs can't run the app due to the port conflict with our services. This PR switches the app's blobstore to listen on `:49000` instead of `:9000`. My thinking for now is that we can centralize all "default endpoint" and "what host/port should I listen on?" into the `deploy` package, and for now just change ports to have a `4` in front of them to reduce the change of conflicts. Later, once we have them centralized in the `deploy` package we can easily modify that code to pick an unavailable port. This also binds blobstore to `127.0.0.1` (more secure), previously it was bound to `localhost`. ## Test plan To test this I did the following: 1. [x] Methodically searched our codebase for `9000` and vetted each instance, to ensure I didn't miss anything. 2. [x] Tested with `sg start app` and confirmed `sudo lsof -i -P | grep LISTEN | grep :9000` reported nothing while `sudo lsof -i -P | grep LISTEN | grep :49000` did. 3. [x] Created an app build with `./enterprise/dev/app/build.sh` and tested it: * [x] Confirmed embeddings generation (which get stored in blobstore) still works through the setup wizard 4. [x] Confirmed `sg start enterprise-codeintel` starts and runs Signed-off-by: Stephen Gutekanst <stephen@sourcegraph.com> |
||
|---|---|---|
| .. | ||
| internal | ||
| rootfs | ||
| shared | ||
| BUILD.bazel | ||
| image_test.yaml | ||
| macro.bzl | ||
| main.go | ||
| postgres_exporter.yaml | ||