Provide sample data for contributors external to CSH wishing to contribute

Bắt đầu bằng cách xem xét thư mục tools và cấu hình tệp dump được tham chiếu trong inc/config.env.php, sau đó kiểm tra cách schema cơ sở dữ liệu hiện tại được tạo và nạp dữ liệu. Công việc được xem là hoàn tất khi một cộng tác viên bên ngoài có thể khởi tạo cơ sở dữ liệu cục bộ và nạp dữ liệu mẫu thực tế mà không cần truy cập vào các bản dump ITS riêng tư hoặc thực hiện lặp lại các migration thủ công.

Since ScheduleMaker data is mainly powered by daily SIS data dumps that are from RIT ITS (and presumably somewhat private), the ability to maintain CSH is somewhat limited to only CSH members who are trusted with access to this data or the databases created from them (using the tools dir of this repo presumably).

While the S3 dependency (seemingly for storage of generated schedule images based on the code) seems relatively easy to substitute with another S3 installation, and a new database can be created pretty easily, populating that database is much harder, if not impossible to set up independently of CSH.

Since Schedulemaker has had no commits in over a year and has at least one relatively major bug that hasn't been addressed in this time (#310) it seems as though it may be useful to allow the rest of the RIT open source community to run local dev versions of this code to develop their own fixes and improvements.

I propose this be done by:

• providing documentation or a script that makes it easy to initialize a new, empty database using the current schema (without needing to run every single time-consuming migration)
• providing one or more complete sample data dumps (including all of the dump files, either made-up with fake/sample data, or using a real ITS-provided data dump from some number of years ago) to allow contributors to populate their empty databases with realistic-enough data to allow schedulemaker to work and populate data locally.
• If scuedulemaker is going to continue to become unmaintained, provide access to the real, production data dumps from ITS, or the scheduleMaker DB that is generated from them so that someone who wants to maintain a fork of the app (whether inside or outside CSH) can continue providing this service to students