#developing custom frontends
1 messages ยท Page 1 of 1 (latest)
You could pretty easily cook up a new frontend - frontend_pretty.go is a bit of a beast, but you can see the general skeleton in frontend_dots.go, and yoink parts of pretty.go over as needed
or, do you mean web UI?
I was thinking of CLI first, then depending on how that goes, come back for guidance on web UI ๐
My goal is to grow my viz dev muscle (currently non-existent) so that eventually I can offer to pair on experiments, rather than being the "ideas guy who can't ship" in that area ๐
I really think we've only scratched the surface of what we can deliver, the potental is so huge. So, worth the time investment
ah nice lol. happy to help!
I'm going to focus on logs (per my comment in other threads)
What I'd love to prototype is a heroku-style log viewer
yeah, that's the thing really, we may be at a local maxima but the cost of getting going on completely different ideas is pretty high, knowing how many things there are to deal with, and not having much certainty going in
have you tried the dots frontend? it's very very close to that, it uses a heroku-style prefixed writer already
Yeah, cost of experimentation is too high... In the past, whenever we've faced this problem in the past, the most effective solution has been to make our loops cheaper and faster.
In this case I think it just means - more people on the team familiar with the code, and willing & able to try things themselves
So I'm trying to dogfood that approach on myself (easier said than done..)
cc @void jackal as we talked about the same... basically "fast and furious 2.0"
2 fast 2 furious
๐
Actually how hard would it be for me to prototype something that is 1) CLI but also 2) querying cloud data? Is there an API I can hit that will get me all the telemetry data?
yeah - you could yoink bits and pieces from dagviz for that, can link to code in DMs
@hushed swallow had a pet project idea to bring that functionality into the CLI, like dagger replay <url> or something (throwaway name)
indeed I did, I ran out of time ๐ข
it never materialized
it's ok. there are only so many justins ๐ซ
@ebon mist on the otel producer side, where did you end up on the new status API?
still room for suggesting ideas?
I'm thinking of an increased specialization of "statuses" between 1) tasks (beginning, end, error/success), 2) messages (no duration, no error/success), and 3) checks (a special case of task for tests, linting etc, which we could filter to produce reports etc)
it's an extremely trimmed down API now: https://github.com/dagger/dagger/pull/9327/files#diff-6d45938d3a99ad730e8d639cd2218f57c90828f1deeaad17c073cad22bfd0b50