"Different port range PR #110" breaks webpacker
bbugh opened this issue · comments
This pull request #110 seems to break webpacker if you use PORT anywhere in the JavaScript envs. In addition, even if you specify PORT=3000 with PORT=3000 ./bin/webpacker or PORT=3000 ./bin/webpacker-dev-server, the port that node sees will be 5100.
For example, we specify in development.rb what some of our websocket and asset hosts are. In development mode, this is always localhost:#{ENV['PORT']}. However, whether we set PORT or not, in the webpacker process the PORT is set to 5100 100% of the time.
Foreman's assumption seems to be that you specify the port for every process, but then ignores the setting for secondary processes.
Related:
@bbugh is this still an issue?