Skip to content

docs: add detailed MapProxy Docker setup instructions - #2666

Merged
sensei-hacker merged 2 commits into
iNavFlight:maintenance-9.xfrom
JoseSzycho:master
Jul 7, 2026
Merged

docs: add detailed MapProxy Docker setup instructions#2666
sensei-hacker merged 2 commits into
iNavFlight:maintenance-9.xfrom
JoseSzycho:master

Conversation

@JoseSzycho

Copy link
Copy Markdown
Contributor

PR Description

This pull request adds a comprehensive Docker & Docker Compose setup tutorial to MAPPROXY.md.

Key Additions & Changes:

  • Docker Compose Setup: Added a containerized approach using Docker Compose with the official ghcr.io/mapproxy/mapproxy:6.1.1-dev image

  • iNav Configurator Instructions:

    • Outlined the steps to select MapProxy as the Map Provider.
    • Documented the exact URL and layer name configuration settings.
    • Added a troubleshooting tip for tab switching (navigating to another tab and back) if changes do not immediately update in the Mission Control tab.

@qodo-code-review

Copy link
Copy Markdown
Contributor

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@github-actions

Copy link
Copy Markdown

Branch Targeting Suggestion

You've targeted the master branch with this PR. Please consider if a version branch might be more appropriate:

  • maintenance-9.x - If your change is backward-compatible and won't create compatibility issues between INAV firmware and Configurator 9.x versions. This will allow your PR to be included in the next 9.x release.

  • maintenance-10.x - If your change introduces compatibility requirements between firmware and configurator that would break 9.x compatibility. This is for PRs which will be included in INAV 10.x

If master is the correct target for this change because it should never be included in any release, no action is needed.


This is an automated suggestion to help route contributions to the appropriate branch.

@sonarqubecloud

Copy link
Copy Markdown

@JoseSzycho
JoseSzycho changed the base branch from master to maintenance-9.x June 22, 2026 23:31
@b14ckyy

b14ckyy commented Jun 23, 2026

Copy link
Copy Markdown
Collaborator

That's awesome! Thank you! Especially for the Compose setup. I will definitely try that on my OMV Home Server as soon as I have time :)

@JoseSzycho

Copy link
Copy Markdown
Contributor Author

@b14ckyy Thank you! You are welcome.

My idea is to start contributing with the project, just small bits during my free time :)

I'll be waiting for the review, so I can learn from the reviewers feedback before I create some other small PRs 🚀

@sensei-hacker
sensei-hacker merged commit 91d8bc8 into iNavFlight:maintenance-9.x Jul 7, 2026
2 checks passed
@sensei-hacker

Copy link
Copy Markdown
Member

Thanks!

@JoseSzycho

Copy link
Copy Markdown
Contributor Author

Thanks to you and the Inav Team!

@sensei-hacker

Copy link
Copy Markdown
Member

Just an FYI for contributors: The tentative schedule for INAV 10 is to have a full release in mid December. That means RC2 needs to be in early to mid November, which places INAV 10.0RC1 at September 1. Please plan to have any new features for INAV 10.0 ready for RC1 no later than September 1. After that, 10.1 will follow about six to seven months later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants