Fix README.md and GETTING_STARTED.md - Recommend sqlite for generation rather than mySQL #250
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The process works seamlessly with sqlite - mySQL requires more work.
Proposal: leave the mySQL documentation there, but add a comment recommending the use of sqlite for local generation.
(nb: I am making this issue and related pull request to test my workflow)
Actually, I see that GETTING_STARTED.md only has instructions for SQLite. I propose removing the mySQL information from README.md for consistency.
I would lean towards going the other way. I see your point where the GETTING_STARTED documentation assumes that MySQL is already installed, and doesn't explain creating the database. I would add that to the GETTING_STARTED documentation. While I think most development should be done against a local SQLite DB, various parts of the infrastructure still use the MySQL DB, (hub.hackerpublicradio.org, and even the main static site may still be built from the MySQL DB--but @ken_fallon would know if that is true). So it would be good to have those instructions for new developers.
I think emphasizing the use of SQLite is good though. Most people shouldn't need to install MySQL to help out.