Open
Conversation
Contributor
Dumbris
commented
Jul 2, 2025
Dumbris
commented
- Add roadmap for MCPProxy-Go 1-Year Plan (2025-2026) focusing on security, compliance, and enterprise readiness. Outline key priorities, phases, deliverables, and success metrics to enhance project direction and community engagement.
- Replace outdated ROADMAP.md with a new development roadmap for MCPProxy-Go, emphasizing security, personal productivity, and registry integration. The updated document outlines implementation phases, core principles, and success metrics to enhance user experience and project direction.
…ity, compliance, and enterprise readiness. Outline key priorities, phases, deliverables, and success metrics to enhance project direction and community engagement.
…xy-Go, emphasizing security, personal productivity, and registry integration. The updated document outlines implementation phases, core principles, and success metrics to enhance user experience and project direction.
Dumbris
added a commit
that referenced
this pull request
Nov 3, 2025
Added comprehensive configuration support for Docker recovery settings to allow customization of health check intervals, retry behavior, and notifications. Changes: - Added DockerRecoveryConfig struct in internal/config/config.go with: - Configurable check intervals (exponential backoff) - Maximum retry attempts setting - Per-notification type toggles (start, success, failure, retry) - Persistent state toggle - Added helper methods for DockerRecoveryConfig: - GetCheckIntervals() with defaults - IsEnabled(), ShouldNotifyOn*(), ShouldPersistState() - GetMaxRetries() - Updated tray app to support environment variable configuration: - MCPPROXY_DOCKER_RECOVERY_INTERVALS: comma-separated durations - MCPPROXY_DOCKER_RECOVERY_MAX_RETRIES: max attempts - MCPPROXY_DOCKER_RECOVERY_NOTIFY_ON_*: notification toggles - MCPPROXY_DOCKER_RECOVERY_PERSISTENT_STATE: enable/disable state - Updated handleDockerUnavailable() to use configured intervals - Updated triggerForceReconnect() to respect notification settings - All notifications and state persistence now respect config settings - All E2E tests passing (25/25) Default configuration: - Intervals: 2s, 5s, 10s, 30s, 60s (exponential backoff) - Max retries: 0 (unlimited) - All notifications enabled except retry notifications - Persistent state enabled 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
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
1 participant
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.