Namespace creation, Validation, and Admin Setup in internal OpenVSX Deployment

[ErikaMolnar]

Hello,

I've deployed OpenVSX internally where I containerized the backend. Specifically, I modified the URL used for malicious checks, because as it is now it pulled this json file from the public GitHub which we do not want. I made changes directly in the PostgreSQL database (I saw some similar approach here) setting my user as an admin and updating the active field in the extension table from false to true. This allowed me to access the admin dashboard in the web UI but I get some errors (maybe my fault).

I want to make sure that I'm following best practices for:

• Creating and validating namespaces in an internal deployment. Am I on the right track? Is this done from the admin dashboard?
• Setting myself as an administrator correctly (without direct DB modifications).
• I saw that for validating a namespace on the official openvsx page you have to open a GitHub issue and the team will handle this internally. Can you please share the process if you can?

I’d appreciate any info on the recommended approach for handling these tasks in an internal setup.
Thank you!