bug: self-hosted internal network CI Deploy Broken

[eni9889]

Provide environment information

ghcr.io/triggerdotdev/trigger.dev:v4.3.0

Describe the bug

This example at https://trigger.dev/docs/cli-deploy#examples no longer works. What is the recommended way now to deploy inside an internal network

Reproduction repo

n/a

To reproduce

n/a

Additional information

n/a

[matt-aitken]

@eni9889 Could you provide more information than this on why it's not working for you? What error are you seeing? What is your self-hosted setup like?

This does work in general for cloud and self-hosted

[nicktrn]

hey @eni9889 - we'll have to update this docs page as many of those flags don't exist anymore. We simplified the deploy command so you should just we able to run npx trigger.dev@latest deploy even when self-hosting. This requires your webapp to be configured correctly with the appropriate env vars.

If you still run into any issues please let us know the exact error your seeing 🙏

[palbrecht1]

@nicktrn can you confirm that this works in air gaps environment? That it does not need access to trigger.dev's server to do this

[nicktrn]

@palbrecht1 that should work as long as you can reach the webapp and your docker registry. All registry info is now configured on the webapp itself via these env vars: