feat: publish a yaml schema

[ankushg]

Problem

When planning a rack, I often find myself editing the raw YAML so I can get things Just Right, and then re-importing it into Rackula for the pretty GUI :)

But it's also tricky to make sure I don't make any errors when manually defining ports and such

Proposed solution

Add an autogenerated jsonschema to the repo and reference it in the yaml files with

# yaml-language-server: $schema=https://raw.githubusercontent.com/RackulaLives/Rackula/master/schema/rack-spec.json

or similar

This would allow editors to validate against the schema when hand-editing things!

Alternatives considered

No response

How important is this to you?

Nice to have

[ggfevans]

Hey @ankushg thanks for bringing this up! You have an excellent point, and it actually is really helpful to know that you are even looking / editing the YAML. I was considering to myself whether people actually would. This confirms that A) totally people are and B) we could make the YAML config more visible/accessible.

I am currently in the midst of changing the schema to support multi-rack and bayed rack config, so I have avoided making it more front-and-center though this is a good reminder to do so.

I am going to convert this to a discussion because there is more to be said here, though I should say I am glad you brought this up.

[ggfevans]

@ankushg a couple further questions around how you are using the raw files:

• I am wondering how you are doing that right now. Are you using the save > opening the zip > editing the YAML file > load > see whats changed pattern? It is the only way I can think of someone doing this right now but thought Id confirm
• you mentioned getting things Just Right, what is it that you are finding is missing that needs tweaking to get there taht could not be done by the regular UI?

[ggfevans]

On interfaces: eg Adding interfaces to custom device types: is this for documentation purposes, or are you hoping to use the connection/cabling features? (We have port-based connections in progress, #362 )

[ggfevans]

On the git workflow: You mentioned checking YAML into your homelab git repo. What else is in there? (Ansible playbooks, docker-compose files, documentation?) Curious if there's an ecosystem we should play nice with.

[ankushg]

Haha thanks! I juuust built my mini 10" rack with all my stuff, so I'm hoping to document things now while the knowledge is still fresh :)

For one, it definitely makes me think a .zip export is lame and will need to be reconsidered.

I definitely understand the usefulness of a zip export if someone has custom images, but that isn't a feature I currently use

On the position ordering: The "reorder devices by position" OCD - can you elaborate: is that purely aesthetic, or does it help you reason about the rack when reading the YAML? (Wondering if we should auto-sort on save)

definitely helps me reason about the rack better!

On interfaces: eg Adding interfaces to custom device types: is this for documentation purposes, or are you hoping to use the connection/cabling features?

both :)

---

Also one more thing is that I often edit the yaml directly to prune device types that I created in the UI but no longer need!

[ankushg]

On the git workflow: You mentioned checking YAML into your homelab git repo. What else is in there? (Ansible playbooks, docker-compose files, documentation?) Curious if there's an ecosystem we should play nice with.

right now it's mostly docs, docker-compose files, komodo resource definitions, and some scripts with templates to make it easier for me to spin up a new stack

I would definitely be interested in some way to keep the rack layout config (yaml or otherwise) synced to a git repo somehow :)

[ggfevans]

no promises on the git sync, though that is something that I would really be keen on. It would take a significant shift in the app in terms of handling auth so it is a ways off, for now it will need to be more file-based. That said, I use git for most every important note in my own environment so I think I need to provide it in my tool to feel 'authentic'

re: device ordering and device type pruning, I will look into cleaning this up either via a UI approach or automatic if possible.

[ggfevans]

Created issues for custom device type cleanup (v0.7.0):

• feat: Add trashcan indicator for unused custom device types #830 - Trashcan icon on unused types with quick delete + undo
• feat: Add cleanup prompt on export/save #831 - Prompt before export/save offering cleanup
• feat: Add bulk cleanup dialog in Settings #832 - Bulk cleanup dialog in Settings

Design: docs/plans/2026-01-20-custom-device-type-cleanup-design.md