🚧 Development Update – DockStat

[Its4Nik]

Hey everyone!

Development on DockStat has been paused briefly while I worked through some challenges with theming. My old, self-built theme handler only worked ~10% of the time, so instead of wrestling with it further, I’ve decided to return to DaisyUI as the component library (a little homage to DockStat v1).

Here’s what’s next on the roadmap:

• 📃 Pages - Default Pages, like "/settings", "/" and so on...
• 🔌 Plugin Renderer – to support dynamic plugin usage
• 🗂️ Page Structuring & Navigation – laying down the foundation for smooth navigation
• ✨ More improvements – additional enhancements and features to follow

A quick note for the future:

• DockStat will not include a custom-built UI library.
• Support for custom themes via DockStore might be added, depending on how well it can integrate with DaisyUI.

Finally, since I’m in the middle of moving, development will slow down for around two weeks. Expect smaller fixes and updates during this time.

Thanks for your patience and support! 🚀

[Its4Nik]

Update

With the latest commit I am closer then never before a breakthrough with the development of DockStat.

This commit features:

• Adapter based integration

  The Docker Adapter is the only supported one but who knows. The point of this is to abstract and modularise to keep The DockStatAPI / DockStast Backend extensible with other solutions like a kubernetes integration. Also plugins will be handled here.

• Full typesafety across deep chained functions thanks to strict typesafety
• Finally got externalised ssh2 and cpu-features working with vite config
• And much more smaller changes

---

I am stoked to say that I am approaching a stage where I can finally stop beginning over and over again. Altough the theme handler might make a come back 👀 . There are no development screenshots, since there is no ui currently only for basic api testing, but soon.

Here are the mentioned commits:

df5cf7f
179b008

[Its4Nik]

Update

So as you can see in the current dev branch by now I am rewriting the React-Router framework (apps/dockstat), again.

I am sorry, but I failed last time at keeping structure, but I will do better this time. I already made a huge process of getting ElysiaJS's Eden treaty working and implementing a translation layer between React-Router and ElysiaJS. It was a bit tricky to be hones, but I think I did it quite elegant.

So where are we at now?

I can finally say that now I am happy with my typesafety everywhere. I mean, I can just import the treaty and use it anywhere in a loader or action across all routes in react router and still even then I still have strict typesafety everywhere without those annoying const tmp = await fetch("...").json() as MYTYPE.

But it looks like I have to use a custom Bun.socket for WebSocket support since RR cannot handler WebSockets through loaders / actions.

Also there are improvements accross my Plugin-Integration-Plan. But thats for another day, better said when i can finally get them working...