-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
Support for docker containers #64
Comments
I think this is a more general I have created a workaround by running a local server and modifying Overlay.vue component to forward requests to my local server. The local server then accepts the request and calls It is definitely possible to implement The local server is a simple Node.js server like this: const express = require('express')
const launchMiddleware = require('launch-editor-middleware')
const app = express()
app.all('*', (request, response, next) => {
response.header('Access-Control-Allow-Origin', '*')
response.header('Access-Control-Allow-Headers', '*')
response.header('Access-Control-Allow-Methods', '*')
next()
})
app.use('/__open-in-editor', launchMiddleware())
app.listen(5173) Then simply fork the NOTE: Be aware that the file path needs to be the full absolute path for IDE and |
The inspector does not work when using a vite server running inside a docker container because the inspector attempts to open the editor within the context of the docker shell.
I've read that it's possible to configure command execution on the host from the container, but it seems cumbersome and potentially opens a major security vulnerability in the host machine.
Do you have any ideas about how this can be supported?
The text was updated successfully, but these errors were encountered: