Merged
Conversation
…nfiguration handling This commit introduces a new backend structure for managing both the Lab and Xatu stacks, aiming to enhance code maintainability and extend functionality. The refactor separates concerns related to each stack type and includes capabilities for editable configurations, service management, and environment variable overrides. Key changes include: - Creation of `labBackend` and `xatuBackend` to encapsulate operations specific to their respective stacks. - Introduction of standardized capability checks, allowing the frontend to adaptively display features based on stack capabilities. - Streamlined API responses, including stack capabilities in the stack information payloads. - Improved structure for configuration editing, allowing for async updates and management of profiles and environment variables through dedicated components. These changes are aimed at enhancing the user experience by providing better feedback on stack status and improving the flexibility of the configuration management interface. feat(stack): create StackBackend interface to unify stack management and add backend logic for managing services feat(stack): implement StackBackend methods for service control, logging, and config management feat(logs): improve logging stream management with context cancellation and liveness detection feat(compose): add Pull method to pull the latest service images fix(stack_context): enhance service health management and initialization logic for existing services fix(tui): handle potential panics when stopping health monitors and streaming logs
samcm
approved these changes
Feb 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit introduces a new backend structure for managing both the Lab and Xatu stacks, aiming to enhance code maintainability and extend functionality. The refactor separates concerns related to each stack type and includes capabilities for editable configurations, service management, and environment variable overrides. Key changes include:
labBackendandxatuBackendto encapsulate operations specific to their respective stacks.These changes are aimed at enhancing the user experience by providing better feedback on stack status and improving the flexibility of the configuration management interface.
feat(stack): create StackBackend interface to unify stack management and add backend logic for managing services
feat(stack): implement StackBackend methods for service control, logging, and config management
feat(logs): improve logging stream management with context cancellation and liveness detection
feat(compose): add Pull method to pull the latest service images
fix(stack_context): enhance service health management and initialization logic for existing services
fix(tui): handle potential panics when stopping health monitors and streaming logs