I am running on Cloud 9 and it took forever for me to figure out how to get things going. I went to Vagrant and kind of got it going there though it took some doing too as the whole Windows/symlink thing was difficult using Oracle Virtualbox.
On Cloud 9 you are effectively running “in production” even in development.
As such you need to add the following line to your development.rb file:
config.webpack.dev_server.enabled = false
Then, each time you want to see something work in production you actually have to run to compile everything in public/webpack:
Once that’s done, run foreman start -f Procfile.dev and that file should look like this:
# Run Rails & Webpack concurrently
# Example file from webpack-rails gem
rails: bundle exec rails server -b $IP -p $PORT
webpack: ./node_modules/.bin/webpack-dev-server --config config/webpack.config.js --host $IP --port $PORT
With these changes I can, I think, use Cloud 9. Vagrant I wound up getting to work by simply doing a global npm install of webpack-dev-server then changing the Procfile to point to the directory it was in instead of the one it wasn’t in within my project for whatever reason.