DEV Community: arielro85

From Hermes outputs to a UI for Garage

arielro85 — Fri, 22 May 2026 18:42:51 +0000

It started, as side projects do, with another side project.

I'd been playing with Hermes Agent and watching it produce things — reports, generated images, scraped CSVs, scratch notes.

Useful stuff. And every time, the same nagging question: where does this go?

The desktop wasn't going to cut it. Neither was a folder I'd forget about by Tuesday. I wanted somewhere I could throw anything at and trust would still be there in a month — organized, addressable, mine. What I actually wanted was an S3 bucket on my own hardware.

Finding Garage

A bit of searching led me to Garage — a self-hosted, S3-compatible object store from Deuxfleurs. Lightweight, replicated, runs happily on a couple of cheap boxes. Exactly the shape I wanted.

I got it running. It worked. And then I hit the part nobody talks about: how do you actually look at your stuff?

The official path is the garage CLI plus something like mc or aws s3. Fine — but a small wall of friction every time I just wanted to glance at what the agent dumped overnight.

I didn't want to aws s3 ls my way to an answer. I wanted to open a tab.

Door

So I built one. A web UI in front of Garage with a low, specific bar:

Open a tab, see my buckets.
Browse files like folders.
Drag-and-drop upload.
Click an image, see the image.
Click a report, read it.
Manage keys, permissions, and the cluster from the same place.

I called it Door. Your garage door.

Still very early and actively in development — this started as tooling for my own side projects and agent workflows. But it's already become one of those tabs I keep open all day.

imaerials / garage-door-ui

Garage Admin UI

A web-based administration interface for Garage — a self-hosted S3-compatible distributed object store.

Built with React 19, Vite 6, shadcn/ui, TanStack Query, and the Garage v2 admin API.

Features

Cluster

Live node status, health tiles, per-node storage bars
Aggregate storage summary (total / used / free with color-coded progress bar)

Layout

View current node roles and staged changes
Apply, revert, or preview layout changes; full layout history

Buckets

List, create, and delete buckets
Manage key permissions per bucket (grant/revoke read, write, owner per key)
Configure S3 CORS rules with one click

Bucket Browser

Folder navigation with breadcrumb trail
Drag-and-drop file upload with per-file progress bars (multipart for files > 5 MB)
Paginated object listing (100 items per page, continuation token navigation)
Multi-select files with bulk delete
Create folders
Download and delete individual files
In-browser file preview — images, PDF, text, JSON, and code files without downloading

Access

…

View on GitHub

Full Stack Deployment with Ansible

arielro85 — Fri, 24 May 2024 18:31:02 +0000

A few months ago I started practicing ansible and some Javascript with React and NodeJs.
As a playground im using some EC2 instances in AWS, and I did not want to re configure everything everytime that I test the site . For this I wrote an Ansible playbook that performs all the required actions to get the app online.

High level overview of what it does:

Extracts the repository names from the frontend_git_repo and backend_git_repo variables.
Updates the system packages and reboots the machine if updates were installed.
Installs gnupg and curl, which are required for MongoDB.
Sets up the NodeSource repository and installs Node.js.
Checks if the MongoDB GPG key is already set up, and if not, it sets it up.
Creates a list file for MongoDB and updates the package list.
Installs MongoDB and starts the mongod service.
Installs pm2 globally, which is a process manager for Node.js applications.
Installs the Nginx web server and configures it.
Copies the SSH key to the EC2 instance.
Clones the frontend and backend repositories from GitHub.
Creates a new folder in the backend directory.
Deletes the copied SSH key from the EC2 instance.
Builds the frontend application and moves it to the appropriate directory.
Configures pm2 for the backend application and starts it.
Restarts the Nginx service.

All the actions above described , are handled by Ansible and a UI called Ansible Semaphore.

Everything is in this repo where you can find the "Mean Stack playbook" and the Ansible Semaphore Docker comppose file to build the controller.

I really recommend to use Ansible or any tool you want to avoid spending lot of time installing and configuring test services.

For sure there is lot of room for improvements, but it saves a lot of time.
My humble collaboration:

https://github.com/imaerials/ansible-home-lab

DevContainers in WSL with Docker and without Docker Desktop

arielro85 — Sat, 28 Oct 2023 15:14:06 +0000

A time ago I decided to migrate all my code development to VSCode DevContainers.
As a WSL user, I was facing some issues when tried to create the containers from VsCode.
Visual Studio code was not able to find the Docker binary cause it was searching it in Windows and not in the WSL instance.
To fix this in VScode Settings configure the following ones:

dev.containers.dockerPath set to /usr/bin/docker
dev.containers.executeInWSL must be checked
dev.containers.executeInWSLDistro only required if you have more than 1 distro in WSL.

With the configurations mentioned above you should now be able to create DevContainers within WSL with docker binary installed.

Hope this little article help improving your coding skills.

Installing MongoDB in WSL2 with Ubuntu-22.04

arielro85 — Thu, 20 Apr 2023 18:40:18 +0000

These last days I've been with no time to practice coding, and one thing stopping me was that I didn't have my dev environment as I would like to.
So this week I decided to write this article on how I did to install MongoDB (latest) on my WSL setup.

Head to root folder

cd /

Install GNUPG

sudo apt-get install gnupg

Issue following command to import GPG keys

curl -fsSL https://pgp.mongodb.com/server-6.0.asc | \
   sudo gpg -o /usr/share/keyrings/mongodb-server-6.0.gpg \
   --dearmor

Create List file

echo "deb [ arch=amd64,arm64 signed-by=/usr/share/keyrings/mongodb-server-6.0.gpg ] https://repo.mongodb.org/apt/ubuntu jammy/mongodb-org/6.0 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-6.0.list

Reload Packages

sudo apt-get update

Install Mongo db Packages

sudo apt-get install -y mongodb-org

Create DB Folder

mkdir -p data/db

Apply permissions

sudo chown -R `id -un` data/db

Run MongoD

mongod

Verify

You should be able to see something like Waiting for connections","attr":{"port":27017,"ssl":"off" on the terminal.

Hope it helps"