Specifying Jobs in Blueprint Infrastructure as Code Spec


I am looking at using Render to host a discourse instance. I notice that in the Discourse example you have the database migrations and static asset compilations whenever the service starts.

Instead, I was hoping to run those as one-off jobs, both to reduce startup time, and to have more control over when they are run and the ability to debug them.

It seems like the Jobs feature is a good match for this, but I was curious if there would be a way to specify the jobs in the Blueprint spec, so that I could re-run them easily, as some named job.

Hi there,

The ad-hoc/one-off nature of Jobs doesn’t feel like it fits the infrastructure definition of a Blueprint. But there does seem to be a feature request for it: https://feedback.render.com/features/p/blueprints-support-for-one-off-jobs

Maybe a “Release Phase Script” would be better suited to deploy-based tasks, which is a planned feature request: https://feedback.render.com/features/p/release-phase-script


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.