Skip to content

Create an example starter pelias.json #80

@orangejulius

Description

@orangejulius

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions