oxequa/realize
Realize
Realize is a developer workflow orchestrator that monitors the filesystem for changes and automatically restarts applications, runs build scripts, and executes custom commands in response. It coordinates sequential command pipelines across setup, start, and cleanup phases, managing process lifecycles for multiple projects from a single declarative YAML configuration file.
The tool distinguishes itself by combining file-change-triggered automation with multi-project process management, allowing several independent projects to be watched and coordinated concurrently. It supports environment variable injection per project, path and pattern-based event filtering to restrict monitoring scope, and stream-based log redirection that captures stdout and stderr to external files for persistent review. A project initialization wizard guides users through creating a tailored configuration file for their workflow.
Realize also provides Docker Compose workflow orchestration for managing multi-container development environments, and enables custom command execution before or after file changes to extend the build pipeline. The tool exports build errors, console output, and warnings to log files for later debugging.
Features
- Build Pipeline Orchestration - Runs predefined build, compile, or cleanup command sequences automatically when source files are modified.
- Command Orchestration - Orchestrates sequential command chains for setup, start, and cleanup phases across multiple projects.
- Development Workflow Orchestrators - Manages setup, start, and cleanup command sequences with path-based event filtering and log redirection.
- File System Event Automation - Monitors directories for changes using OS-level file system events and triggers configured actions.
- File Watchers - Monitors the filesystem for modifications and automatically restarts applications or runs build scripts in response.
- Process-Level Auto-Restarts - Stops and restarts running application processes whenever their source files are changed to enable hot-reloading.
- Hot-Reloading Servers - Automatically restarts applications and runs build scripts when source files change for a fast edit-refresh cycle.
- Multi-Project Process Managers - Coordinates independent watchers, task pipelines, and environment settings for several projects concurrently through a shared configuration.
- Build Automation - Executes predefined build commands automatically when source files are modified during development.
- File-Change-Triggered Restarts - Monitors the filesystem for modifications and triggers automated actions like restarting applications or running build scripts.
- Source-Change Auto-Restarts - Stops and restarts a running application automatically whenever its source files are modified.
- YAML Configuration Files - Defines project workflows, watchers, commands, and environment variables in a structured YAML file.
- Filesystem Change Monitors - Watches the filesystem for modifications and triggers custom shell commands, build pipelines, or application restarts.
- Change-Triggered Builds - Runs a predefined build or compilation command in response to file changes before restarting the application.
- File-Change-Triggered Commands - Runs user-defined scripts before or after file changes, or globally, to extend the build pipeline.
- Build Log Exporters - Writes build errors, console output, and warnings to an external file for later review and debugging.
- File Extension Pattern Filters - Restricts monitoring scope by filtering file system events based on directory paths and file extension patterns.
- Environment Variable Injection - Injects project-specific environment variables into spawned processes to customize runtime behavior.
- Execution Log Redirection - Captures stdout and stderr from managed processes and writes output to external log files.
