Reset the database
It is often useful to restart RadGrad with a new database. This involves:
- Stopping the current RadGrad service.
- Dropping the MongoDB RadGrad database.
- Edit the settings.json file to point to the new database to load on startup.
- Update the settings in mup and restart the RadGrad service.
Stop RadGrad
First, stop the RadGrad service:
Sample invocation and results:
Drop database
Second, drop the database by invoking this command:
Sample invocation and results:
Edit settings
Third, edit the app/.deploy/settings.json file to specify the new database.
This usually involves changing the value of the field "databaseRestoreFileName".
Deploy with updated settings
Next, invoke mup deploy to rebuild and redeploy RadGrad.
Sample invocation and results:
Check status of deployment through logs
To ensure that what you wanted to have happen actually happened, check the logs with mup logs:
Sample invocation and results:
Run mup logs, record new admin password!
Note that when you start up the system with a new database, a new admin password will be generated and the log file will be the only place it is made available. The log is only available until the next deploy of the system, so be sure to invoke mup logs
, find the log message with the new admin password, and record it someplace safe.