Deploying docuseal to heroku, getting 404 errors on rendering the document

[svsaraf]

I've used the "deploy to heroku" button on docuseal, and wired up a custom subdomain and SSL using heroku SSL, but otherwise am using the vanilla configuration.

While the docuseal experience worked perfectly the first day I deployed it, a couple days later most static loads are now 404ing. From experience with Heroku, my guess is this is because the static files on the Heroku dyno are not reliable (you should put static files in S3 or somewhere stable).

Is that correct? If so, can you show instructions for how to modify the docuseal code so that static files get rendered correctly? Interestingly this doesn't apply to all static files. It's also possible there's some issue with the JS renderer unrelated to static file storage. But my testing on docuseal.co (i.e. not my on-prem version) shows that this is the likely culprit.

[svsaraf]

Screenshots here

[omohokcoj]

@svsaraf Heroku doesn't have a persistent storage and all files are removed on app restart - you need to use AWS s3 with heroku for storage

[svsaraf]

Thanks - for future searchers, AWS s3 creds should be put in heroku here.

With the variable names set per documentation here: https://www.docuseal.co/docs/configuring-docuseal-via-environment-variables