sprocs and migrations

[trombonekenny]

I have the need for migrations in PrairieSchedule. I'd like to revisit the idea of modularizing the database initialization parts of PrairieLearn into PrairieLib.

I was thinking some way to pass in the project name and path into the migrations.init() function. The migrations table would need to be updated with a unique index and project so each one has its own numbers.

The sprocs stuff could use some updating too, like getting its file list from the directory (like migrations does). Maybe rename it to something like initializations since those are run each time the server runs.

Both functions could be pulled into the same library?

I'm just brainstorming before actually changing anything. Worth the effort?