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
Copy file name to clipboardexpand all lines: README.md
+5
Original file line number
Diff line number
Diff line change
@@ -62,6 +62,11 @@ After you created the GitHub OAuth app, the next step is to copy the _Client ID_
62
62
63
63
With these settings in place, you should be able to log in by authorizing your OAuth app.
64
64
65
+
### Docker Compose Setup
66
+
67
+
If you prefer to quickly get started with a local, docker-based development environment, you can use the approach described in our [docker compose setup](doc/development.md#using-docker-compose).
68
+
You can use our docker compose profiles, allowing you the option to either run a service directly in a docker container or to manually build and run it on your local machine.
69
+
65
70
### Google Cloud Setup
66
71
67
72
If you would like to test file storage via Google Cloud, follow these steps:
Copy file name to clipboardexpand all lines: doc/development.md
+40-1
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,29 @@ To get started quickly, it is recommended to use Gitpod as default with the deve
6
6
7
7
[](https://gitpod.io/#https://github.com/eclipse/openvsx)
8
8
9
+
### Using Docker Compose
10
+
11
+
To run the Open VSX registry in a development environment, you can use `docker compose` by following these steps:
12
+
13
+
* Verify Docker Compose is installed by running `docker compose version`. If an error occurs, you may need to [install docker compose](https://docs.docker.com/compose/install/) on your machine.
14
+
* Decide which profile(s) to run based on your needs. By default, only the PostgreSQL and Elasticsearch containers start, which suits running the OpenVSX server and web UI locally for easier debugging. The [docker-compose.yml] file defines additional profiles for specific components:
15
+
*`backend`: Starts the OpenVSX server container (java).
16
+
*`frontend`: Starts the web UI container.
17
+
*`commandline`: Starts a container with the OpenVSX CLI tools.
18
+
*`openvsx`: Combines `backend`, `frontend`, and `commandline` profiles to start all related services.
19
+
*`kibana`: Starts a kibana instance for easier access to the Elasticsearch service.
20
+
* In the project root, initiate Docker Compose:
21
+
* Without profiles: `docker compose up`.
22
+
* With profiles: `docker compose --profile <profile_name> up`. Use multiple `--profile` flags for multiple profiles, e.g., `docker compose --profile openvsx --profile kibana up`.
23
+
24
+
* Depending on which profile(s) you selected, after some seconds, the respective services become available:
25
+
* registry backend is available at [http://localhost:8080/](http://localhost:8080/) if the `backend` or `openvsx` profile was selected.
26
+
* web ui is available at [http://localhost:3000/](http://localhost:3000/) if the `frontend` or `openvsx` profile was selected.
27
+
* kibana is exposed at [http://localhost:5601/](http://localhost:5601/) if the `kibana` profile was selected.
28
+
* Open VSX CLI commands can be run via `docker compose exec cli lib/ovsx` if the `commandline` or `openvsx` profile was selected.
29
+
* To load some extensions from the main registry (openvsx.org), run `docker compose exec cli yarn load-extensions <N>`, where N is the number of extensions you would like to publish in your local registry.
30
+
* For troubleshooting or manual intervention, access a service's interactive shell with `docker compose run --rm <service> /bin/bash`. Service names are listed in the [docker-compose.yml](docker-compose.yml) file.
31
+
9
32
### Setup locally on WSL
10
33
11
34
- Install WSL
@@ -96,7 +119,7 @@ To get started quickly, it is recommended to use Gitpod as default with the deve
96
119
97
120
- Download the Elasticsearch image from Docker Hub and enable it in the Docker Desktop
98
121
99
-
### Run the application
122
+
### Run the application locally
100
123
101
124
- cd cli
102
125
@@ -115,3 +138,19 @@ To get started quickly, it is recommended to use Gitpod as default with the deve
115
138
- yarn build:default
116
139
- yarn start:default
117
140
- Go to localhost:3000 on browser and it should be up and running
141
+
142
+
### Optional: Deploy example extensions to your local registry
143
+
144
+
Run:
145
+
146
+
- in `server/`:
147
+
`gradlew downloadTestExtensions` to download vsix files from the official store and from Github.
148
+
- in project root (the server application must be running):
0 commit comments