Payload on Heroku

[endymion1818]

Hi,

I am having an issue with Payload on Heroku. I've encountered the following error:

2022-01-31T13:13:48.768765+00:00 app[web.1]: $ yarn build:payload && yarn build:server
2022-01-31T13:13:49.251849+00:00 app[web.1]: $ PAYLOAD_CONFIG_PATH=src/payload.config.ts payload build
2022-01-31T13:14:07.980762+00:00 heroku[router]: at=error code=H20 desc="App boot timeout" method=GET path="/" host=antecedents-backend.herokuapp.com request_id=15dc9045-53cb-4f93-b2f9-a5b53d9eea00 fwd="78.151.190.134" dyno= connect= service= status=503 bytes= protocol=https
2022-01-31T13:14:37.570493+00:00 heroku[web.1]: Process running mem=556M(108.7%)
2022-01-31T13:14:37.586988+00:00 heroku[web.1]: Error R14 (Memory quota exceeded)
2022-01-31T13:14:47.727732+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2022-01-31T13:14:47.909097+00:00 heroku[web.1]: Stopping process with SIGKILL
2022-01-31T13:14:48.821432+00:00 heroku[web.1]: Process exited with status 137

This happens on both the Hobby and Free tier.

What is the expected memory usage of Payload?

[DanRibbens]

You should be able to run an instance of Payload and stay under 512 MB for a basic app on free/hobby tier. Though, you may run in to overheads in the build step you are calling that require more memory. I know others have successfully used Heroku to host Payload apps, though I'm not sure their specific configurations.

Here are a couple of things to help limit memory usage:

1. Avoid devDependencies by installing dependencies for production: yarn install --production to include only packages necessary for production.
2. Move any non-production packages to devDependencies in your package.json see demo example or next example
3. Consider building your application in a CI process, then transfer build artifacts to your host. Here is an example of a Payload + Next.js github action to an Azure Web App See example, this may be helpful for configuring for Heroku: https://github.com/marketplace/actions/deploy-to-heroku
4. Verify that you can run the same build commands locally to rule out any code errors like infinite loops or circular dependencies.

Feel free to share your package.json along with any followup questions you've got for more help.