yeah. seems to be the case 🙁 what is
yeah. seems to be the case 🙁 what is the "best practice" here?
13 Replies
Ignoring it is what you want, right?
no i need it to be available to convex
The dockerfile itself?
yes
using it to kick of an external container in the actions
If you need values from the dockerfile you'd generally use env vars for that
Typically dockerfile is in repo root unless you're multi-repo
You're trying to read in the entire yaml aren't you
yeah, but it's not the dockerfile for this project
hmm
it's for running daytona containers with an agent
but if convex doesn't make it easy to pass a file like this, then i'll find a different approach
esbuild won't support yaml imports natively - can you pass a yaml string to Image.fromDockerfile or some alternative version of that method?
If it didn't have to be a file you could author in a js/ts file, which is kind of terrible, but could be livable maybe
i just wanted something quick and hacky for now since that dockerfile was working locally, but not after production deploy. but it also has a declarative typescript builder sdk that i can use instead i think. just already had the dockerfile doing what i needed.
If there's any way to pass a yaml string instead of a file path, pasting the yaml to a js template literal might be the quickest path forward. If it works well you could make a script that generates a js file from the dockerfile in your convex directory before you deploy.
cool thanks