dag.Host() | Dagger | Page 1

slim glacier Feb 20, 2025, 12:03 AM

#

Oh really? didn't realize it was a big blocker

#

Is it a "won't" or "can't" situation?

lime badge Feb 20, 2025, 12:05 AM

#

This is the main part that doesn't fit today #1339366755134472282 message

#

@rotund lance might have more context beyond the idea at the end of that thread

#

I can get around my blocker if I demo with non-modules dagger. But I don't think its worth the tradeoff if people want to see examples

slim glacier Feb 20, 2025, 12:09 AM

#

Sorry didn't mean to fork that other thread

#

I'll comment in there

rotund lance Feb 20, 2025, 12:10 AM

#

haven't had time to look into it yet, but it seems like a pretty complicated feature has to be implemented to support turning a module object into a service. I wouldn't bank on being able to do it in a short timeframe for a demo

slim glacier Feb 20, 2025, 12:16 AM

#

yeah looks like it - sorry @lime badge I completely misjudged how difficult this would be

lime badge Feb 20, 2025, 12:18 AM

#

yeah to be fair enabling dag.Host() wasn't so bad, but it wasn't actually what I needed

slim glacier Feb 20, 2025, 12:19 AM

#

@lime badge I think running it in a container, and enabling dagger-in-dagger, is more realistic, and I think we can make it not too terrible

lime badge Feb 20, 2025, 12:19 AM

#

should only take a minute to find out because I had a version like that already

slim glacier Feb 20, 2025, 12:20 AM

#

I think the generated client feature by @willow summit might come in handy

lime badge Feb 20, 2025, 12:25 AM

#

Agreed - at least then the 'webhook server' can be dagger sdk and it can call module functions. This is how @boreal swan had it setup for the hackathon https://github.com/aluzzardi/langdag/blob/main/examples/agent/main.go

#dag.Host()