Merging configuration files

Since version 8.1, MobiFlight Connector can merge several configuration files together.

The way this works is worth a bit of explanation, so that you can follow a sensible workflow. There is one important thing to consider: When you merge configuration files, you cannot later "unmerge" them.

It is of course totally possible to have just a single configuration file that has everything on your home cockpit, but there are two use cases that benefit greatly from the functionality of config merging:

• Plane-specific configurations - If you have some panels that you use for all aircraft and then type-specific ones that are used only for certain planes, it would be nice to make any changes or updates to just one file instead of all of the different plane-specifig configs that use the same panel.
• If you contribute to, or build openly designed panels and circuit boards using the [MobiFlight panel design template] (https://github.com/Mobiflight/mobiflight-templates) panel template and [open hardware MobiFlight panel repository] (https://github.com/Mobiflight/mobiflight-panels) they will generally have configuration files assocociated with them, and those also might get updated later.

By using a very simple workflow you can use "Merge config" to your advantage if you need separate config files for different aircraft.

• Consider each separate file as the "source" where all changes happen.
• Any files you actually use, are merges.
• Merged files are disposable - when you make a change, you just merge all needed separate files again and save over your previous merge.

It helps if you use some file naming convention, like S-panelname for "separate files" and then merged-aircraftname for the merged file.