-
Notifications
You must be signed in to change notification settings - Fork 4
Gateway Tunnelling Development Setup Improvements #110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…tral instance and edge gateway Docker profiles for development
…tral instance and edge gateway Docker profiles for development
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR enhances the Gateway Tunnelling documentation by adding a comprehensive "Gateway Tunnelling Development Setup" section. The new content provides detailed instructions for running both the central instance and edge gateway locally for development and testing purposes, complementing the existing production setup sections.
Key Changes
- Added detailed development setup instructions including Docker compose configuration for both central instance and edge gateway profiles
- Provided specific environment variable configurations and port mappings for local debugging
- Included reference to the integration test that validates the setup
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This PR introduces some more documentation about how to run the central instance and edge gateway locally for development, by giving some pointers about what needs to be changed in the Docker compose files, including a Git diff that people can just apply using their IDEs.