-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting up a private Open VSX registry #703
Comments
Hi @aallrd, thank you for choosing Open VSX. I think the
Hope this helps. Please report back your findings. |
Hello,
I start the server loading this file using the below command line:
It throws the below database related error:
I have tried modifying the I am guessing otherwise I need to setup an external PostgreSQL database and fill the configuration under Do you have any idea? |
To move forward in the meantime I have managed to setup an external PostgreSQL database:
I added the below properties in
I started the server:
And it now fails because of the
What's the simplest thing I could add there? |
Hi @aallrd, you need to setup a GitHub OAuth app and add the
You also need to run a ElasticSearch 7.11.0 instance and configure it:
|
Can’t I just disable the authentication entirely ? |
Not at this moment, see #337. I think you can set random values for the github You can then publish extensions using |
I am having a hard time connecting the openvsx-server to my elasticsearch instance. Here is my
And my
The openvsx-server waits for the elasticsearch service to be up as instructed:
But I keep getting these errors:
Do you have an idea of what could be wrong in the Thank you. |
In Looking at the exception, it seems like JobRunr is trying to use ElasticSearch to store its jobs, despite |
Maybe it is that the server can't connect to postgres? |
I actually forgot to mount the
|
Okay I am able to have something up and running with the below
As you mentioned, the Publish (http://localhost:3000/user-settings/extensions) and Login URLs do not work. I am now trying to create a namespace/publish my package, using the
Can you share more details about how to publish packages in this configuration ? |
I think you need a user and personal access token. This is from the dev configuration:
I think you don't need to set |
Thank you for these DB commands, they will be useful to manually create other users/tokens.
|
Yes, you can use
Yes, that's expected. You need to publish the dependency first and then try again.
extension file resources are processed async. It can take a little while before it becomes available on the web portal |
Using a '-' will just create "ACME-co", it's not the same as "ACME co".
What does inactive mean ? |
That's true, but spaces are not allowed in the namespace name. The displayName can have spaces.
No, something went wrong. I'd clear the database and try again.
The extension can't be retrieved and doesn't show up in search results. |
I cleared the DB, published again and found this in the log:
Seems like indeed it failed to insert in the DB despite the success message:
Do you have an idea what could be the issue? Also, is there a way to delete things (namespaces, packages, ...) from the command line since the UI is not available? |
That happens sometimes. This method is retryable, so it doesn't directly mean the publish operation failed.
No, there isn't. You can clear the database. |
Do you have a demo/reference VSIX package I could try to test with? |
I am still not able to make it work using your example extension:
I have the same exception that I mentioned before in the logs, and nothing is displayed in the UI.
Can you please share what version of PostgreSQL and Elasticsearch you are using in production so that I align with these versions? I have attached my I don't know how to move forward on this issue. |
I get the same error messages when opening openvsx in a Gitpod workspace. I'll try to find the cause of the issue there. In the meantime you can try PostgreSQL 10.17 and ElasticSearch 7.11.0. |
Using these versions of PostgreSQL and and ElasticSearch, I am able to see the extension on the portal 👍 . I am still getting the aforementioned errors in the logs, so it does not seem to be related to this specific issue. The portal weirdly displays "0 results" on the homepage (do you know why?), but searching for the extension yields results and I can browse the extension details. |
Ok, thanks for the feedback.
Search results are cached for 10 minutes. When you do |
I fixed the publish errors that I got on Gitpod. It might also fix the publishing error that you're seeing. |
I confirm that I am not seeing the aforementioned errors in the log using |
As mentioned in #706, I am now trying to host this setup internally at https://openvsx.foo.com.
I updated my docker_compose.yml with this new custom image (removed the UI service) and configured my reverse proxy to listen on http://localhost:8080/ but I am unable to access the UI (blank page). In the web browser console when opening https://openvsx.foo.com/ I have the below error:
I cannot find the file bundle.js in my custom built openvsx-server image, what did I miss? |
You need to do |
It does clone in
With your
|
The file bundle.js seems to be available after the yarn build:
But only the static folder is copied at the end of the Dockerfile, is that expected?
|
Yes, but for the webui to generate
|
Okay that did the trick even though I don't understand why it has to be different from the project's Dockerfile.
Now that I moved to an isolated network without internet access I am facing a new issue: extensions information is not loading when I browse them. I am observing two behaviors:
Do you have an idea what could be the issue? |
Can you open the network tab in the browser developer tools and search for README.md? |
From the web console I get:
|
|
I am not sure how to check that, where can I see it? |
Nevermind, that was my first guess. |
You can set |
I added the
Shouldn't the port be 443 there ? |
You also need to set |
That did the trick. 👍 |
That would be much appreciated. Looking forward to it! |
Here is the complete Dockerfile
|
Thanks @oloedpaper. I've added a slightly modified version of the DockerFile to the wiki: https://github.com/eclipse/openvsx/wiki/Deploying-Open-VSX#getting-started |
Hello guys! |
Hello,
Thank you for this project.
I am trying to setup an internal Open VSX registry for my development team in order to be able to publish our private extensions for VSCode.
I read the deployment documentation but I am struggling to configure the
openvsx-server
.I understand it requires an
application.yml
file mounted at/home/openvsx/server/config/application.yml
in the container, but I cannot find any basic template to get started from.I have found this application.yml from open-vsx.org but it seems very complex for what I am trying to setup.
My goal is to have a publicly available internal instance with local storage, basically the simplest deployment possible for our small team.
Could you share some documentation/material to be able to setup this deployment?
Thank you.
The text was updated successfully, but these errors were encountered: