u/Kubaguette

▲ 5 r/Fedora

Hello guys!

About a week ago, I released the first version of my development environment manager, originally built just for Bazzite. The feedback from the community was very helpful (and honest), so I spent the last days reworking large parts of the project and discussing ideas with some of the Bazzite developers.

Today, I released EnvStation v1.0.0. It is now completely distro-agnostic and built to run on any immutable OS (Silverblue, Kinoite, Bazzite etc.). It is a native Rust/Tauri application designed for immutable Linux distributions like Fedora Atomic, Silverblue, Kinoite, Bazzite, and similar systems. The main goal is to simplify and unify the currently fragmented workflow between:

  • Distrobox containers
  • VS Code DevContainers
  • local terminal environments

What it actually does:

  • Unified Parity: Automatically keeps your setup across Distrobox (for your host terminal) and DevContainers (for your IDE) aligned.
  • 1-Click environment scaffolding: You can quickly create reproducible environments for Python, TS/JS, C# and more.
  • Drift Detection: Warns you if your container and IDE configs fall out of sync.
  • Native & Rootless: Uses user-level Podman, runs natively without Electron bloat.

I would appreciate your honest feedback! Maybe you discover some bugs, have suggestions for the codebase, or just want to point out things I could do more elegantly regarding UI/UX - In any case please let me know.

(I'll drop the GitHub link in the comments so the Automod doesn't get mad!)

u/Kubaguette — 7 days ago

Hey everyone,

I am the solo developer behind Bazzite Architect, a desktop application built with React, TypeScript, and Tauri. It is a graphical interface for managing "Distrobox" containers on Linux (specifically aimed at immutable distros like Bazzite/Fedora).

The goal of the app is to make a traditionally terminal-heavy, complex workflow feel accessible, clean, and native to a desktop environment.

I have attached some screenshots covering the main views (Dashboard, Environment Cards, Settings, etc.). I’m a developer first and a designer second, so I'd love your brutally honest feedback to help me polish the UI/UX for future upcoming releases. You can find the project repo here. It includes a GIF where you see the app in action.

I am specifically looking for feedback on:

- Information Density: The app needs to display statuses, image names, and storage sizes. Does the typography and spacing make this easy to scan, or is it overwhelming?

- Color Palette & Contrast: It is a dark-mode-first application. Is the contrast sharp enough, especially on the text and subtle borders?

- Overall Navigation: Does the top navigation bar feel intuitive for a desktop utility?

Thank you!

u/Kubaguette — 10 days ago
▲ 2 r/rust

Hello!

I built a Tauri v2 desktop app in Rust to orchestrate development environments on immutable Linux (Bazzite / Kinoite).

The core problem I ran into: On immutable systems, you can’t rely on a traditional “host-level” workflow. Instead, you end up juggling:

  • Distrobox containers (for terminal work)
  • VS Code DevContainers (for IDE)

Keeping those in sync manually becomes surprisingly messy, especially for workflows like Python/AI where you need strict environment isolation.

So I built Bazzite Architect: A small orchestrator that manages Podman (rootless), Distrobox, and DevContainers, and keeps them in sync via a local manifest.

Tech stack:

  • Frontend: React / TypeScript
  • Backend: Rust (Tauri v2)

Some implementation details I’d love feedback on:

  • I offload heavy system tasks to keep the Tauri UI thread responsive (~60fps target)
  • Directory size calculation uses bounded parallelism (rayon + jwalk) to avoid saturating SSD I/O
  • Bridging async/sync via tokio::spawn_blocking for system calls (Podman, filesystem ops)
  • I tried to document invariants carefully and justify every .unwrap() with // SAFETY: comments

What I’d love feedback on:

  • Are my async/sync boundaries sound?
  • Is my error handling overcomplicated or unidiomatic?
  • Are my Mutex / shared state patterns reasonable?
  • Any obvious architectural mistakes?

Here’s the repo.

Happy to get roasted — I want to improve and learn new stuff 🙂

Thanks!

u/Kubaguette — 11 days ago
▲ 22 r/Bazzite

Hey everyone,

When I switched to Bazzite, I was pretty overwhelmed by the immutable workflow. I didn't know how to use Distrobox properly, and it constantly annoyed me that my VS Code DevContainers and my Distrobox setups kept drifting apart. I just wanted to code without jumping into the terminal to run setup commands every single time.

So, I built Bazzite Architect – a native orchestrator written in Rust/Tauri.

It basically:

  • Syncs Distrobox and DevContainers automatically.
  • Scaffolds zero-config dev environments natively.
  • Handles the Podman storage relocation so your root drive doesn't fill up.

I'd really appreciate any feedback, feature suggestions, or constructive criticism you might have!

Automod deleted my last post when I added links, so I'll drop the GitHub repo (with showcase) in the comments!

reddit.com
u/Kubaguette — 13 days ago