You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I manage environment vars with dotenvx. The way is works is that you store encrypted env vars in your repo, and you have just one secret key that gets used to unencrypt everything else at runtime. Makes env management across multiple platforms much easier.
The problem is that you unencrypt vars by using a custom run command, ex.:
dotenvx run -- my_script.ts
This doesn't work well with trigger.dev. Could you allow me to set custom run commands for my tasks?
Describe the solution you'd like to see
Allow a custom run command to be specified in the task config, or support doing this with extensions.
Describe alternate solutions
My temp solutions:
don't use dotenvx for the vars that I want to use with my trigger.dev tasks
Wrap my task script so that instead of calling directly, my task does something like run_bash('dotenvx run -- node my_script.js'). Haven't tested this yet; it would probably work but I assume it would cause me to lose my telemetry.
Additional information
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I manage environment vars with dotenvx. The way is works is that you store encrypted env vars in your repo, and you have just one secret key that gets used to unencrypt everything else at runtime. Makes env management across multiple platforms much easier.
The problem is that you unencrypt vars by using a custom run command, ex.:
dotenvx run -- my_script.ts
This doesn't work well with trigger.dev. Could you allow me to set custom run commands for my tasks?
Describe the solution you'd like to see
Allow a custom run command to be specified in the task config, or support doing this with extensions.
Describe alternate solutions
My temp solutions:
run_bash('dotenvx run -- node my_script.js')
. Haven't tested this yet; it would probably work but I assume it would cause me to lose my telemetry.Additional information
No response
The text was updated successfully, but these errors were encountered: