#Temporal.io and Dagger.io

1 messages · Page 1 of 1 (latest)

harsh orbit
#

They seem like oil and water for all the joy I'm having integrating. Has anybody tread this path before? I've had it almost working on three separate occasions, but it is elusive. I'm happy to post more, but there is a lot of history and I don't want to just dump a bunch of code; I don't want to do that if nobody here is familiar with the model.

rotund heron
#

IIRC @rich wasp has been through that path before and he seemed quite happy with it

harsh orbit
#

Oh really! that's awesome. I'm able to consistently get my stack to stand, but when I navigate to localhost:8233 I get 404'd from temporal.

Screenshot_2026-04-15_at_3.20.37_PM.png
#

I've got:

  • temporal db
  • temporal server (with db bound)
  • temporal UI (with server bound)
    I believe all the hostnames and ports and all that are well aligned. At one point I actually saw the temporal UI, but when I went to add the next layer of complexity it regressed to this 404 state and I haven't been able to climb back up.
rotund heron
harsh orbit
#

correct

harsh orbit
#

OMG I was going to the wrong path. actual real deal 404 due to user error cost me 2 days of work RIP

rotund heron
rich wasp
#

Um, I'm using Temporal with Dagger to run CI pipelines "durably". I'm not running Temporal inside Dagger. To me, that would be a very hard challenge to get done just thinking about it. 🙂

harsh orbit
#

It wasn't too bad getting it going, really. The issue was that I accidentally assigned the traefik dashboard port to the temporal UI port (8233) in one of my early calls, and when I navigated to localhost:8233 traefik did an HTTP302 to .../dashboard/. Subsequent requests (when the port was actually forwarded to temporal UI) still did the redirect to a non existent path. My ape-descendent mind was used to temporal seamlessly redirecting to an actual existing path (and I never really focused on that path). Super facepalm.