workflows

To manage persistent background daemons, you can bind a shell command to a persistent workflow that runs until explicitly stopped. This supports lifecycle management like start, restart, and removal for active background processes.

Web server processes often stop after installations due to environment changes. This workflow orchestration automatically restarts persistent processes after package or module installations, ensuring continuous uptime during development.

Yes, you can bind an interactive terminal or TUI to a persistent workflow. The orchestration tool supports persistent tasks across development and production environments, allowing you to manage interactive sessions alongside background services.

The best way to access logs for active background services is through the workflow's built-in log monitoring. It exposes logs for active workflows, allowing you to monitor persistent processes and track their output during execution.

Yes, this workflow orchestration supports automatic restarts for long-running processes. It automatically restarts persistent workflows after installations and provides lifecycle management to manually start, restart, or remove tasks as needed.

You can configure a workflow to keep your main dev server running by binding your npm run dev command to a persistent workflow. This ensures the process remains active and automatically restarts after module installations.