How to use one port for Webpack AND api server for HEROKU?

Hi,

trying to deploy my build to heroku. this repository uses two ports, one webpack and one for api. but as i know, heroku just has one PORT option which gets self assigned with env port variable.

i cannot figure out how to combine the two services. how should i handle this big problem ?

https://myapp.herokuapp.com/ws/?EIO=3&transport=polling&t=LMr9Nni -> 
app[web.1]: [0] proxy error { [Error: connect ECONNREFUSED 127.0.0.1:3030]

[OKNoah]

@sascha1337

Procfile:

web: $WEB

In Terminal in the root of your app directory:

heroku apps:create myniceapp
heroku config:set --app myniceapp WEB="npm run start-prod"
git push heroku master

heroku apps:create myniceapp-api
heroku config:set --app myniceapp-api WEB="npm run start-prod-api"
git remote add heroku-api https://git.heroku.com/myniceapp-api.git
git push heroku-api master

So there you have two identical heroku apps, but one is running the command npm run start-prod and the other npm run start-prod-api. Both of these exist in the package.json already, each runs either the front-end alone or the back-end.

[OKNoah]

@cedricium Probably. You can push the same repo to two different Heroku apps and just use different commands to run them. E.g. node server/index.js and node client/index.js respectively.

But there are downsides:

• You’ll have way more dependencies to download. Your back-end server will need to download Vue, for example, and your frontend will need to download Sequelize. Can be a waste of bandwidth and time.

• You won’t be able to use different versions of the same package between front and back. You back-end might have a dependency on a certain version of moment, but your front-end might need a newer version.

If you want easier development, some people use Vagrant or Docker to create a virtual system that runs both their seperate server repo and their front-end repo, plus any necessary databases and so on. Then they can and run their app locally with 1 command, and begin developing more quickly, while still having 2 repos. Only downside is this can be slow on older computers or lightweight models like MacBook (2015) or MacBook Air.