fix: broken trigger.dev templates

[Winne4r]

Changes

• Fixed the incorrect length for MAGIC_LINK_SECRET, ENCRYPTION_KEY, and SESSION_SECRET in both Trigger.dev templates.

The latest template was unusable due to the following issues:

• service was working, but it was imposible to login via the cli and deploy anything
• key creating from UI was also broken

I discovered that the issue was related to wrong length of keys:
https://github.com/triggerdotdev/docker/blob/b2c2949ac923b91f86fe2014059e531fae1d9c33/.env.example#L64

As you can see these secrets should be generated with:

openssl rand -hex 16

which is equal to 32 chars string

[Winne4r]

I also added some missing config, with this changes I finally managed to successfully run the background task.

[peaklabs-dev]

Why did you change this?

[Winne4r]

Without this change it will not work properly.
You can check config - 3040 is unused port. Probably earlier smbody changed DEV_OTEL_EXPORTER_OTLP_ENDPOINT to the right one, but forgot about OTEL_EXPORTER_OTLP_ENDPOINT

[peaklabs-dev]

Do not add port mappings as this is insecure.

[Winne4r]

It's specific to tigger.dev.
The coordinator pulls and runs images in the root Docker network, and this behavior cannot be changed. To enable newly deployed containers to communicate with the coordinator within the trigger network, you can only map the port.

I can change it to bind only 127.0.0.1 to smthing like:

ports:
      - 127.0.0.1:9020:9020

will it help?

[Winne4r]

I changed it to restrict the port to only the host machine.