Feature Request
When using the development environment commands of docker-compose, the system that appears seems to be in a fully functional state (database tables exist. migrations have run, admin user created) but the version table is not populated, leading to a 500 error when accessing the maintenance page as the admin user. Once either the install test or PHP pages are executed, the needed information is there.
How can we make CDash better?
Potential avenues:
Fully ready the system for user interaction as part of the startup process:
- Add
php artisan command for executing the install.php process
- Add automatic execution of the
install test
Or, warn the user
- Add documentation to highlight that tests are expected to be run before interacting, but can be bypassed with the install.php functionality.
Feature Request
When using the development environment commands of docker-compose, the system that appears seems to be in a fully functional state (database tables exist. migrations have run, admin user created) but the
versiontable is not populated, leading to a 500 error when accessing the maintenance page as the admin user. Once either theinstalltest or PHP pages are executed, the needed information is there.How can we make CDash better?
Potential avenues:
Fully ready the system for user interaction as part of the startup process:
php artisancommand for executing the install.php processinstalltestOr, warn the user