-
-
Notifications
You must be signed in to change notification settings - Fork 629
Config option to listen unix-socket instead of port for dev-server #2752
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
Comments
👍 hmm, I looked at the code that we have before, I think we will return it in the next few days, it's not difficult |
subscribe |
Sorry for delay webpack/webpack-dev-server#3479, after merge I will update our logic here and all will be work |
This issue had no activity for at least half a year. It's subject to automatic issue closing if there is no activity in the next 15 days. |
Issue was closed because of inactivity. If you think this is still a valid issue, please file a new issue with additional information. |
Is your feature request related to a problem? Please describe.
At first i was create this issue at webpack/webpack-dev-server#3308
As described at https://webpack-v3.jsx.app/configuration/dev-server/#devserver-socket unix socket can be listen unix-sockets with
devServer: {socket}
, but with webpack-dev-server@4 it's does't work.As i can find socket option belongs to dev-server and dropped at 4th version.
Describe the solution you'd like
I was think it's problem related to dev-server, but redirected here.
Describe alternatives you've considered
Now i resolve this issue by replacing webpack-cli + simple-configuration with own express app what uses dev and hot middleware directly without dev-server.
Additional context
About my use case
Thick dev-server with many users
Any user can create socket's at own specified folder
Nginx automatically serves static from folder and not found from sockets over https with wildcard certifaicate
PROJECT-USER.dev-server.example.com => /home/USER/sockets/PROJECT.sock
Also it's uses different socket name for proxy
/api
to backend app, but it unrelated to this issueIt's gives way to don't do any actions to serve new or test project from user folder.
Every project have https on standard port and easy semantic name.
Dev's have no requirements to local machine and can easly and instantly show own version to other.
No local accessed app ports gives way to use POSIX permission to restrict access between different devs. (nginx uses project named auth basic file from user folder)
Just nginx and permission without external programs gives zero-cost reasonable isolation and high control to any dev without special requirements with just a copy&paste folder. (without socket option it's requires additional code or manual actions from every dev)
The text was updated successfully, but these errors were encountered: