You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, our README here advises people to copy our full default.json file and use it as a starter pelias.json. This is not really good because it locks people into all the defaults, and forces them to start with a super long config.
While it would be a little more work, ideally we would have a "starter" pelias.json explicitly for people to copy/paste as their initial pelias.json. This would only have a general framework of the full config and only have parameters that we expect people to override (like paths, etc). This would ensure that as we change the defaults, they will be propagated to most user's configs automatically over time.
The text was updated successfully, but these errors were encountered:
Currently, our README here advises people to copy our full
default.json
file and use it as a starter pelias.json. This is not really good because it locks people into all the defaults, and forces them to start with a super long config.While it would be a little more work, ideally we would have a "starter" pelias.json explicitly for people to copy/paste as their initial pelias.json. This would only have a general framework of the full config and only have parameters that we expect people to override (like paths, etc). This would ensure that as we change the defaults, they will be propagated to most user's configs automatically over time.
The text was updated successfully, but these errors were encountered: