How does Raftt handle environment state when switching between Git branches or features?
Raftt's Git workflow integration automatically manages environment states in the background. Developers can switch branches or work on multiple features without needing to create or destroy environments manually, as the platform handles these transitions seamlessly.
What happens if a container's main process dies during remote debugging with Raftt?
Unlike traditional container behavior where the container might capsize, Raftt allows for introspection and rerunning even if the main process dies. This enables developers to continue debugging and iterating quickly without losing their environment.
Can Raftt environments be shared with non-technical stakeholders, such as product leads, for review?
Yes, Raftt allows sharing a URL to a live remote development environment with teammates and product leads. This link remains accessible even if the developer switches to work on a different feature, enabling continuous access for review and collaboration without needing screen shares or meetings.
How does Raftt ensure that remote development environments are as close to production as possible?
Raftt focuses on providing production-like cloud environments. While it doesn't explicitly detail the exact mechanisms, the emphasis is on mirroring production configurations and dependencies within the remote environment to minimize discrepancies and ensure reliable testing.
What is the 'raftt up' command and what does it do?
The 'raftt up' command is a single command-line instruction that, when run from any context in a Git repository, automatically detects the current environment definition. This command is central to quickly spinning up and managing Raftt's remote development environments.
Does Raftt offer self-hosting options for its platform components?
Yes, the Enterprise tier of Raftt includes a self-hosting option, providing greater control over deployment and infrastructure for organizations with specific requirements.