-
Notifications
You must be signed in to change notification settings - Fork 820
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
Open RavenDb Studio as a standalone webapplication #16761
Comments
What exactly are you trying to do? |
Hi @ayende I would like to open RavenDB Studio as a standalone application. Currently, RavenDB Studio is accessed through a web browser, which requires navigating to the appropriate URL. However, it would be extremely convenient if RavenDB Studio could be opened as a standalone application on desktop platforms. This would provide a more seamless user experience and allow for easy access. One possible implementation approach is to add a line in the manifest.json file, specifically display: 'standalone', which would enable RavenDB Studio to be installed and opened as if it were a standalone application. |
@ml054 is that something that is even possible for us? |
@ayende Do you guys prefer a pull request so you can test it out? |
Before that, we need to understand what is the point, just being able to store that as a app launcher shortcut? |
@smarinade Would you like to have a separately hosted or locally running RavenDB studio application to be able to connect to multiple RavenDB instances (and have those instances running without studio)? |
Note that what you are asking is not supported. The studio is bundled with RavenDB, and it is meant to be used with the same server. That alleviate things like versioning, CORS, etc. |
Would it be possible to open the application as a standalone web application?
Possible solution
By adding the display property "standalone" to your manifest.json the application will look and behave like a standalone application.
Manifest.json example
{ ... "display": "standalone" }
The text was updated successfully, but these errors were encountered: