We could take over the current default config settings as defaults in the code, to be able to deploy with a minimal config?
Otherwise, we could take the settings in the live API and have them as defaults.
That would lead to an OOTB ors behaving similarly to the live API, and any change users do to it will have to be explicitly configured.
Anything changing the defaults does then need to be properly documented.
That should be done in application.yml, which is shipped anyways. Documentation should reflect that.
After a lengthy discussion we concluded the following solution:
the ors-config.yml the users get are auto-generated by commenting out non-necessary lines from application.yml
this file activates the default car profile on heidelberg.osm.gz like we did before for the example setup for docker
We could take over the current default config settings as defaults in the code, to be able to deploy with a minimal config? Otherwise, we could take the settings in the live API and have them as defaults.
That would lead to an OOTB ors behaving similarly to the live API, and any change users do to it will have to be explicitly configured. Anything changing the defaults does then need to be properly documented.
That should be done in
application.yml, which is shipped anyways. Documentation should reflect that.After a lengthy discussion we concluded the following solution:
heidelberg.osm.gzlike we did before for the example setup for docker