Profile developer notes

Concepts and orientation

• Brouter-profiles repository serves just as a featured storage for the end user profiles and auxiliary files.
• Profile development is not done there, but in dedicated repositories hosting respective profile common templates.
• Majority of profiles are generated by a simple tweaking of parameters of the respective common profile template by the locally run (obsolete)Windows batch file sedbatch.bat Linux bash script sedbatch.
• I do it directly on the Android device, running the script in termux - Linux terminal emulator.
• The batch downloads respective templates from the Github, modifies them and saves then under specific profile named, putting inside the profile comment instead of the header comment placeholder.
• If the template reaches the release quality, the profiles are then manually pushed to Brouter-profile file repository.
• Some special on demand profiles are made by special treatment and usually are not maintained, even if sometimes their features do find their way into the template.

Issues, questions, feature requests

• Issues and questions related to the profile deployment, requests for new profile generated from a template, or requests for special profiles belong to BRouter-profiles project issues.
• Issues related to the profile templates, questions and requests about template development belong to respective separate projects/repositories ( Trekking-Poutnik, Hiking-Poutnik, Car-profile