Here is my use case. Several instances of webpack-dev-servers, running simultaneously on shared server everyone is serving content on its one port.
这是我的用例。几个webpack-dev-servers实例,在共享服务器上同时运行,每个人都在其一个端口上服务内容。
At some point, every site falls into [WDS] Disconnected! loop. It's not clear to me where's the breaking point, but obviously, it correlates with the number of WDS instances.
在某一时刻,每个网站都会被断开连接!循环。我不清楚断点在哪里,但很明显,它与WDS实例的数量有关。
So my question is where's the bottleneck RAM, CPU, too many WebSocket connections? Maybe it is a configuration thing?
我的问题是,瓶颈内存,CPU,太多WebSocket连接?也许是构型的问题?
Have you ever encountered a similar problem?
你是否遇到过类似的问题?
Is there a way to fix it? I mean besides working on local machine:)
有办法解决吗?我的意思是,除了在本地机器上工作外:
- node: 8.9.1
- 节点:相应要求
- webpack: 3.5.5
- webpack:3.5.5
- webpack-dev-server: 2.7.1
- webpack-dev-server:2.7.1
1 个解决方案
#1
0
In webpacker.yml
file use the following settings for dev_server
on development
env.:
在webpacker。yml文件在开发环境中对dev_server使用以下设置:
dev_server:
host: '127.0.0.0'
port: 8080
https: false
disableHostCheck: true
#1
0
In webpacker.yml
file use the following settings for dev_server
on development
env.:
在webpacker。yml文件在开发环境中对dev_server使用以下设置:
dev_server:
host: '127.0.0.0'
port: 8080
https: false
disableHostCheck: true