workflows

To manage background application processes, you can configure specific commands to run as workflows, set auto-start options, and define required ports for webview, console, or vnc output types. This ensures your services run continuously in the background.

Restarting a backend application after code changes is handled by targeting the specific workflow name, such as "Start Backend", and triggering a restart. This updates the running process with your new code while maintaining the configured port settings.

You can monitor workflow status to check if background processes are currently running, view their output logs, and verify open ports. This allows you to confirm that your configured application services are operating correctly on their designated ports.

The best way to remove unneeded background processes is to use the workflow removal feature, which safely stops and deletes the specified process. This cleans up your environment by terminating services you no longer need.

Yes, this process management approach supports webview, console, and vnc output types. Each output type has specific port requirements that must be configured when setting up the workflow for your application.

To configure a new workflow, you set up the desired run command, such as "npm run dev", and specify the port requirement, like port 5000. The workflow will start the process and monitor until that port becomes active.