Reputation: 2063
I'm trying to deploy the static website to Heroku and I struggle how to correctly setup the Procfile
.
I have next command to run on the server:
npm install
gulp build
(will make a build with /public
folder)http-server
(will serve /public
by default)What I've tried:
web: npm install; gulp build; http-server
web: npm install & gulp build & http-server
Upvotes: 18
Views: 21661
Reputation: 409
You can run multiple command inside Procfile using sh -c
command :
worker: sh -c 'firstCommand && secondCommand && etc...'
Notes : Procfile should be at the project root level.
For example :
worker: sh -c 'cd backend && yarn install && yarn build && yarn start-worker'
Or in your case (if u have Procfile at the same level as package.json) :
web: sh -c 'npm install && gulp build && npm run http-server'
Upvotes: 3
Reputation: 456
You may also have been looking for &&
or a library like concurrently.
Regardless, and per the docs, use Procfile
as nothing more than an entry point to your npm start script.
Use the npm scripts lifecycle as stated (npm-scripts).
"scripts": {
"start": "node index.js",
"test": "mocha",
"postinstall": "bower install && grunt build"
}
Heroku has adopted the 'there's an app for everything' mantra, but for buildpacks. Whatever you're building, there's a buildpack for it.
Upvotes: 5
Reputation: 2063
Okay, so I've spent a bit of time on that and came up with the answer. By default, heroku is installing all packages from the package.json
file, so npm install
is no longer required. Then what was left - gulp build
and http-server
.
For that case, I've added "postinstall" : "gulp build"
to my package.json
and it left me with web: http-server
.
Simplifying things have actually solved the problem. Not sure how useful that information might be to you, but it's worth to share.
Upvotes: 23