back to home

RackulaLives / Rackula

Open-source drag-and-drop rack layout designer

View on GitHub
935 stars
35 forks
174 issues

AI Architecture Analysis

This repository is indexed by RepoMind. By analyzing RackulaLives/Rackula in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.

Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.

Source files are only loaded when you start an analysis to optimize performance.

Embed this Badge

Showcase RepoMind's analysis directly in your repository's README.

[![Analyzed by RepoMind](https://img.shields.io/badge/Analyzed%20by-RepoMind-4F46E5?style=for-the-badge)](https://repomind.in/repo/RackulaLives/Rackula)
Preview:Analyzed by RepoMind

Repository Overview (README excerpt)

Crawler view

Drag and drop rack visualizer --- What _Is_ This Plan your rack layout. Drag your devices in, move them around, export it. It runs in your browser. You can close the tab whenever you want. What It _Do_ • **Drag and drop devices** into your rack so you can frown at them • **Real device images** so it actually looks like your gear, not sad grey boxes • **Export to PNG, PDF, SVG** for your documentation or for printing and staring at • **QR code sharing** - your layout lives in a URL, scan it and it just shows up But _Why?_ You might ask, why should I make an imaginary rack like some sort of IT cosplay? And to that I would say, "fine then! don't! SCRAM!" but also, consider: • **Plan your layouts** before you build them. It's a lot easier to move your mouse than that 4U server full of hard drives. Your shoulder will thank you. • **Document existing layouts** so you know what is where. • **Because you can** Get Started **Use it right now:** count.racku.la Selfhost with Docker Docker Run Docker Compose Then open and get after it. Persistent Storage (Self-Hosted) For layouts that persist across sessions: See Self-Hosting Guide for details. For production/self-hosted API security: • should be your real app URL (restricts which browser origins can call the API). • protects API / routes (optional, strongly recommended). If unset, write routes remain open. • controls centralized auth gate behavior: • : auth gate disabled (best for local/trusted development only) • : use an OpenID Connect provider (requires provider config plus ) • : local auth mode (requires ; tracking: #1117) • is required when auth mode is enabled (minimum 32 characters). Use a random secret and rotate it when needed. • Current stable auth hardening: deny-by-default gate, signed session cookies, timeout/rotation policy, CSRF enforcement. • Current auth flow maturity: OIDC/local login provider wiring is still in progress. • For HTTPS deployments, set (compose templates default to this). Only set for local HTTP testing. • Session hardening defaults are enabled when auth is on: • cookie, , in production • bounded absolute + idle session lifetime • CSRF checks on state-changing cookie-authenticated requests Generate strong secrets: Set values in a file beside : Or pass them inline: Build from source Serve the folder however you like. It's just files. Documentation • Architecture Overview • Technical Overview • Contributing Guide Built With Claude This project was built using AI-assisted development with Claude. I told it what to build and then said "no, not like that" a lot. The AI did a lot of typing. Commits with substantial AI contributions are marked with tags because we're not going to pretend otherwise. Acknowledgements Built for the r/homelab and r/selfhosted communities. Colours from Dracula Theme. Device data from NetBox devicetype-library. See ACKNOWLEDGEMENTS.md for full credits. Star History Licence MIT - Copyright (c) 2025 Gareth Evans