Auto-build a SQLite file using a runner on every push

[alexpawlowski]

Is your feature request related to a problem? Please describe.
A potential app to guide developers in the Knoxville area to locations of where groups meet, group contact, etc need a centralized relational database that is reasonably up to-date. This repo already has this information, but is de-centralized to make it easier for each group to keep their information up to date. It would be great if there was a way to combine the relations inherent in this collection of yml files into a single SQLite file that could be embedded into a mobile app.

Describe the solution you'd like
I'd like to see a Travis CI runner or some other service take the collection of yaml files listed here and produce a SQLite file that could be broadcast as a new release upon every push to the master. Mobile Apps that are developed could watch for new releases at a specified frequency (this information will probably not change often, maybe once a year).

Describe alternatives you've considered
I have only seen SQLite files built from scratch and have not delved into what a programatticly built SQLite database would look like. SQLiteBiter may be a tool to use for this in connection with a runner, I am not sure. (hopefully there's a straight pythonic way to do this)

Additional context
I can provide a template for the nested logic that is inherent for the build of the website.

[alexpawlowski]

Hey @costrouc could you take a look at this? I can add stuff as needed.

[costrouc]

Yeup will do! So thoughts right now. On each commit a CI runner would generate a sqlite database. It will be tiny < 10 mb and queries. This sqlite database will be published via https://datasette.readthedocs.io/en/stable/publish.html and deployed on a free their instance. This will expose a rest API, csv API, and adiliby to download entire dataset. And now a rest API is provided for mobile apps etc.

[costrouc]

Looking into this today!