Fix: Trigger.dev

[rennokki]

Changes

Fixed the Trigger.dev images pointing to the latest instead of main.

latest tag is 8 months old and points to v2 while main is the newest, v3.

This will also fix problems with ARM machines not being able to run because latest is v2 and has no support for linux/arm64

Trigger also comes with new services: Redis and Electric, which are configured in their own Docker examples.

Issues

N/A

[rennokki]

@andrasbacsai

The trigger stack needed new services: electric and redis.

The trigger with external database service is expected to be handled by the user, but I'm not sure if we should remove it, as the stack is complete in trigger.yaml.

[Mortalife]

This will likely not run in Staging or Production because you're missing both the coordinator service and the docker-provider. The versions for these images should be v3 not main as has been set.

There are more complete versions (though still not following the deployment best practices provided by Trigger.dev) available in the discussion on this topic.

You can find details of official deployment which myself and other have based our working examples off at: https://github.com/triggerdotdev/docker

You can find the discussion at: #2439

[rennokki]

@Mortalife Let me take a look at it closer and I'll join that discussion afterwards.

[andrasbacsai]

I think this is still WIP, right? As we need the coorditor (and probably other stuffs) as well.

[rennokki]

@andrasbacsai Looking at it in the next hours.

[rennokki]

Not sure if I am the only one that has issues with shared configurations. They seem to not be working properly? I end up in the SERVICE_* variables not working well and get populated in my env variables.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
14127286	Triggered	Generic Password	cda2e26	lang/ro.json	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[hamedyosefian]

Hi... when release this version ??

[peaklabs-dev]

@rennokki I have tested it and have one improvement request. Could you please check the healthcheck for Trigger as I am unsure if it has one and the current one is not working.

[rennokki]

@peaklabs-dev @andrasbacsai