I’m Finally Separating Git From My Backend

🎯 Kicked things off last week
Cleaned up my messy codebase — better folder structure, killed redundancy, and made my GitHub clone way easier to manage. But there’s still this one thing bugging me…

📖 The problem I’ve been avoiding
Right now, all my custom Git commands (init, add, commit, push, pull) are buried inside my backend folder. Which means if someone wants to use them — they’d have to grab my whole server. And honestly, that’s just bad design.

😅 Why I did it like this anyway
Back when I started this, I had zero clue how to build separate command modules. It felt like unnecessary headache when I could barely keep the project standing. So I stuffed everything in the backend just to keep moving.

⚡ Time to fix that mess
Now that my codebase isn’t a total dumpster fire, it’s finally time to tackle this. The plan? Separate the Git logic from the backend and build it as its own independent command system.

🤯 Real talk: I’ve never done this before
I know how to build web apps, sure. But making a mini version control system with custom add/commit/push commands? That’s uncharted territory for me.

💪 But that’s exactly why I’m excited
This is the kind of weird, uncomfortable problem I love. No idea how I’ll pull it off yet, but I’m pumped to figure it out — and learn how Git works under the hood while I’m at it.

🚀 If you’ve been here before…
Would love your thoughts, resources, advice, or even random chaos stories from when you built something weird like this. Drop ‘em in the comments. Or just send good luck vibes 😅.

Dev log continues… 🔥