PipelineXGo

A minimal Go-based CLI daemon that runs quietly in the background, waiting for defined triggers and orchestrating pipelines of actions. Think of it as an automation engine designed to remove repetitive chaos from your workflow.

---

What is PipelineXGo?

PipelineXGo is about triggers → pipelines → actions.
You define what to watch, and what to do when something happens.

Examples of possible pipelines:

• A new .blend file appears in renderQueue/ → run Blender CLI, convert outputs, stitch into video, upload to Drive, log results.
• A fresh .cpp file drops into src/ → compile it, run tests, and push binaries to a release folder.
• A new dataset lands in data/ → preprocess, run ML training, and save metrics to a dashboard.

The Blender example is just one scenario. The goal is to make PipelineXGo flexible enough to handle any workflow you define.

---

Status: Work in Progress

This project is not finished yet. Right now it’s more of a sketch and a few proof-of-concept scripts. But the direction is clear:

• A minimal Go daemon that listens for file events.
• A pipeline engine that can chain multiple operations.
• A configuration layer (eventually with an Electron UI) so users can design their own pipelines without touching code.

---

Vision

PipelineXGo isn’t just another watcher. It’s an automation engine. A way to turn repetitive steps into smooth, orchestrated flows. A daemon that doesn’t just watch files — it treats each file as the start of a process.

---

Why Build This (if tools already exist)?

Yes, file watchers and CI/CD systems exist. But:

• They’re generic. They don’t care about your specific creative or technical workflow.
• They expect you to glue everything together with shell scripts.
• They don’t provide a user-friendly way to design pipelines visually.

PipelineXGo is being built to feel personal, minimal, and tuned for any workflow — whether creative, technical, or data-driven.

---

Roadmap

• Core Go daemon (file watching + trigger engine).
• Config format (YAML/JSON).
• Example integrations (Blender CLI, compilers, FFMPEG, ML scripts).
• External library hooks (like F.manage).
• Cloud uploads (Google Drive, S3).
• Markdown/HTML logging with links + previews.
• Electron UI for pipeline design.

---

Motto

“You focus on creating. PipelineXGo will handle the rest.”

---

Disclaimer

This project is under construction. Expect missing features, rough edges, and plenty of tinkering. But that’s the fun part — building something that doesn’t exist yet.

---

Planning

First Phase

first phase is focused on building the core Go daemon and config format.

first feature would be watching a folder for changes and triggering defined actions

We initially decided to use a C++ library to handle file operations, but we are now building our own go library to do all file operations.