Detailed upgrade instructions for metadata.yaml -> datasette.yaml
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.5k
- Forks
- 904
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 18
Description
Exception: Datasette no longer accepts plugin configuration in --metadata. Move your "plugins" configuration blocks to a separate file - we suggest calling that datasette..json - and start Datasette with datasette -c datasette..json. See https://docs.datasette.io/en/latest/configuration.html for more details.I think we should link directly to documentation that tells people how to perform this upgrade.
Originally posted by @simonw in https://github.com/simonw/datasette/issues/2190#issuecomment-1759947021
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the configuration documentation at https://docs.datasette.io/en/latest/configuration.html and review the metadata.yaml and datasette.yaml upgrade context in the issue. Add or link to instructions that explain the migration and the replacement configuration command; done means users can follow the documentation without relying on the original issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100