Repository navigation
Finalize naming & clean up old stackable cockpit #47
Description
We have the stackable-cockpit repo which contains web stuff from the previous cockpit UI.
By now it's clear that we're going to go with the stackable-ui project.
Now we need to figure out how to clear this up
- Decide: Rename stackable-ui, move into stackable-cockpit, keep separate
- Decide: Name for the UI
- Delete old web stuff from stackable-cockpit
- Update docs
Related PRs:
Metadata
Metadata
Assignees
Labels
No labels
Activity
labrenbe commentedon Apr 9, 2026
Before we can make a decision we should discuss if we want the backend for Stackable UI to stay SvelteKit or move to Rust
Option 1 = backend for is Rust:
backend code lives in stackable-cockpit repo, Svelte frontend replaces old frontend in
web.Option 2 = backend stays SvelteKit
Should move into own repo and probably reuse the stackable-cockpit name. The current backend =
stackable-cockpitdbecomes a utility/proxy to talk to Kubernetes. The stackable-cockpit repo is renamed to reflect the new role.lfrancke commentedon Apr 9, 2026
Having just learned my lesson from the Portal: It can become very painful having the two separate.
Especially if the Backend is a "Backend for Frontend". I'd definitely keep that as SvelteKit. That could then talk to other backend bits like
stackable-cockpitdas you mentionedlabrenbe commentedon Apr 9, 2026
I've discussed this with @Techassi today and we think this would be a good topic for the onsite week as there a pros and cons for both options. I've already added it to our agenda.