Magic link login loops in Safari on local Trigger.dev

The problem

Issue triggerdotdev/trigger.dev#186 (closed, 19 comments): Logging into a locally-run Trigger.dev via magic link fails in Safari. With no RESENDAPIKEY set, the magic link prints to the terminal, but opening it in Safari 16.4.1 bounces you back to the magic-link page instead of into the dashboard. Sending the link by real email did not reproduce it, which pointed at a cookie/session quirk with the terminal-printed link in Safari.

What fixed it

Resolved by a product change, per maintainer matt-aitken: when running the platform locally, Trigger.dev no longer sends a magic link at all and just logs you in directly. If you hit the Safari redirect loop on an older local build, upgrade to a release with this change. On current versions there is no magic-link step in local dev, so the Safari cookie issue cannot occur.

In gh:triggerdotdev/trigger.dev#186 (Trigger.dev), the issue reported was: Issue triggerdotdev/trigger.dev#186 (closed, 19 comments): Logging into a locally-run Trigger.dev via magic link fails in Safari. With no RESENDAPIKEY set, the magic link prints to the terminal, but opening it in Safari 16.4.1 bounces you back to the magic-link page instead of into the dashboard. Sending the link by real email did not reproduce it, which pointed at a cookie/session quirk with the terminal-printed link in Safari. The verified resolution from the thread: Resolved by a product change, per maintainer matt-aitken: when running the platform locally, Trigger.dev no longer sends a magic link at all and just logs you in directly. If you hit the Safari redirect loop on an older local build, upgrade to a release with this change. On current versions there is no magic-link step in local dev, so the Safari cookie issue cannot occur. Source: mount the host path https at container path //github.com/triggerdotdev/trigger.dev/issues/186