Bring in historical event data from the current site, along with some documentation and a script for working with data from the production site.
Things left to do:
[x] Add updated_at timestamps to events
[x] Provide a way to go "back in time" on the event list page (probably via query string arg)
[x] Limit # of events fetched and rendered on event list page
[x] Limit events included in sitemap.xml
Interesting things in here
doc/migration/README.md describes the legacy database situation, and doc/migration/export-data.sh can export a viable CSV of event data using docker + mysql + sed (this could be extended in the future to export other interesting data)
rake import_events can process the above mentioned CSV to generate markdown files
The querystring arg ?from=yyyy-mm-dd can be used to go "back in time" on the event listing page to see what the page would look like with historical event data
There's about a million markdown files for events. I tried to keep those events in a single commit to make it possible to review this thing. Kramdown did a pretty good job of converting HTML back into Markdown. It's not perfect--there's still cruft from pasting from Microsoft Word and stuff, but all in all serviceable I think as a historical archive.
Bring in historical event data from the current site, along with some documentation and a script for working with data from the production site.
Things left to do:
updated_at
timestamps to eventsInteresting things in here
doc/migration/README.md
describes the legacy database situation, anddoc/migration/export-data.sh
can export a viable CSV of event data using docker + mysql + sed (this could be extended in the future to export other interesting data)rake import_events
can process the above mentioned CSV to generate markdown files?from=yyyy-mm-dd
can be used to go "back in time" on the event listing page to see what the page would look like with historical event data