Raftt runs your containers but slightly modifies the container behavior to improve the development experience. The container's main process is Raftt's lifeguard process - instead of the process you defined in the docker-compose file, K8s manifest, Helm chart or the image itself.
The Raftt Process Lifeguard
Lifeguard runs your main process when it starts but stays alive even if the process dies. This behavior allows for easier debugging capabilities, as it prevents the container from terminating and losing its state when it crashes. Keeping the container up also allows better development velocity because you can quickly restart the main process.
raftt stop and
raftt restart only affect the user's main process, not the container itself, and
raftt rebuild rebuilds and reloads the container itself.
Additionally, lifeguard allows you to connect directly to any of the containers in your environment using