masto-fe-standalone/Procfile.dev

web: PORT=3000 bundle exec puma -C config/puma.rb
sidekiq: PORT=3000 bundle exec sidekiq
stream: PORT=4000 yarn run start
webpack: ./bin/webpack-dev-server --host 0.0.0.0
changed to run foreman with vagrant (#2742) * changed to run foreman with vagrant * change port specification method and database setting * delete changes of environment variable related code * hard coated the port 2017-05-04 02:39:50 +00:00			`web: PORT=3000 bundle exec puma -C config/puma.rb`
Fix sidekiq "port" being wrong (#3014) Sidekiq doesn't need a port, however that env var is used for generating URLs in development, so when foreman sets it wrong, you get bad URLs from the streaming API during development 2017-05-12 15:46:14 +00:00			`sidekiq: PORT=3000 bundle exec sidekiq`
changed to run foreman with vagrant (#2742) * changed to run foreman with vagrant * change port specification method and database setting * delete changes of environment variable related code * hard coated the port 2017-05-04 02:39:50 +00:00			`stream: PORT=4000 yarn run start`
			`webpack: ./bin/webpack-dev-server --host 0.0.0.0`