I’m building a validated Docker Compose hub — and you can contribute

Tumic — Mon, 13 Apr 2026 13:48:00 +0000

If you’ve worked with Docker, you’ve probably done this more than once:

search for a docker-compose.yml
copy it
fix errors
add missing env variables
make it actually work

Repeat… every time you need a new service.

The problem

There are tons of Docker Compose examples online, but:

many are outdated
many don’t include .env setups
many break when you actually run them
and most aren’t designed for reuse

👉 You don’t know if something works until you try it.

What I built

I launched:

👉 https://dockercomposehub.com

It’s a hub of production-ready Docker Compose templates designed to be:

copy-paste friendly
clean and minimal
ready to run

What makes it different

Every template is validated before it’s published.

That means:

✅ Docker Compose structure is checked
✅ Required services and configs are present
✅ Security issues are flagged (unsafe mounts, privileged mode, etc.)
✅ The setup is actually run and verified

👉 Only templates that pass all checks are listed.

Why this matters

Most examples online are basically:

“Here’s a config… good luck”

But small issues break everything:

wrong env variable names
missing volumes
incompatible versions
unsafe defaults

👉 Validation turns templates into something you can actually trust.

I want this to be community-driven

Right now it’s early — and that’s where you come in.

Instead of one person maintaining templates, I want to build:

👉 a shared library of validated Docker Compose setups

You can submit your templates

If you’ve built something that works well, you can share it:

single services (Postgres, Redis, Grafana…)
full stacks (app + database + reverse proxy)
niche or production-ready setups

Every submission goes through the validation pipeline before being published.

What makes a good submission?

✅ uses .env (no hardcoded secrets)
✅ includes persistent volumes
✅ clean and minimal
✅ actually works

Bonus:

security best practices
real-world usage
sensible defaults

Why contribute?

Help other developers save time
Share something you’ve already built
Get credited on the platform
Help define a standard for Docker Compose templates

The goal

To create a place where:

👉 You don’t Google “docker compose X” anymore
👉 You just search, copy, and run a validated setup

If you’ve ever written a compose file that worked well —
that’s already valuable.

Would love to see what you’ve built 🙏

I Built a Browser-Based Clipboard Sync Tool That Works on Any Device

Tumic — Fri, 13 Mar 2026 10:24:48 +0000

I switch between my phone, tablet, and laptop constantly. Like many developers, I often copy links, notes, commands, or small files that I want to access on another device.

But surprisingly, moving small pieces of information between devices is still awkward.

Most of the time I end up doing one of these:

emailing something to myself
sending it through a chat app
saving it in a notes app
uploading it to cloud storage

All of that just to move a link or a small snippet of text.

So I decided to build a small side project to solve this problem.

The Idea

The goal was simple:

Create a temporary shared clipboard between devices that works instantly.

No accounts.

No installation.

No setup.

Just open a webpage on multiple devices, enter the same room code, and share content instantly.

That project became ClipSync.

How It Works

ClipSync uses a simple concept: temporary rooms.

Each room acts as a shared clipboard where devices can send and receive content in real time.

Workflow:

Open ClipSync on two or more devices
Enter the same room code
Anything you paste appears instantly on the other devices

You can share:

text
images
files

All connected devices see updates in real time.

Real-Time Sync

To make syncing instant, the application uses WebSockets.

When a user sends text or uploads a file, the server broadcasts the event to every device connected to the same room.

This allows updates to appear immediately without refreshing the page.

Technology Stack

The project is intentionally simple.

Backend

Node.js
Socket.io for real-time communication
Redis for temporary storage

Frontend

Typescript
Modern browser APIs
Responsive layout for mobile and desktop

Redis stores room data and automatically expires entries after a set time.

Temporary Storage

ClipSync is designed for quick temporary sharing, not long-term storage.

Rooms automatically expire after 24 hours.

There are also some limits to keep the service stable:

maximum 30 items per room
maximum 5 files per room
maximum file size of 25 MB
maximum text length of 30,000 characters

If limits are exceeded, the oldest items are removed automatically.

Cross-Platform by Default

Because ClipSync runs entirely in the browser, it works on:

Windows
macOS
Linux
Android
iOS

Any device with a modern browser can join a room and start sharing content instantly.

Why I Built It

This project started as a small experiment, but I quickly realized how often I needed something like this.

Sometimes the simplest tools solve everyday annoyances better than complex solutions.

Instead of installing apps or creating accounts, I just wanted something that works instantly when needed.

Try It

If you're curious, you can try ClipSync here:

https://clipsync.live

I'm always interested in feedback from other developers. If you have ideas for improvements or features, I'd love to hear them.

Forem: Tumic