Make generation of valhalla.json optional

[brad-4k]

Hello,

We are running multiple instances, all sharing a network mounted volume that is mapped to /custom_files which contains the valhalla.json file. The problem we are having is that when all the instances start, they are all trying to regenerate the valhalla.json file and at times, some fail because they are all trying to write to the file.

What is the reason for generating the json file?

It should be a simple change to /valhalla/scripts/configure_valhalla.sh to check if the file exists and not generate a new one if it does.

What are your thoughts?

[nilsnolde]

Our expertise is proprietary but can be purchased under [email protected].

[brad-4k]

Thank you Nils for the response.

I should have been a little more clear in my question. The main point was to find out if this would break other peoples use cases.

I'm happy to make the change and commit but if this wouldn't be considered should I just fork the repo?

[nilsnolde]

Ah right, if that was the idea, then jep, I'd recommend forking.