mirror of https://github.com/statping/statping
Updated Issues and Solutions (markdown)
parent
bebb068dc6
commit
94530040ad
|
@ -17,4 +17,9 @@ If you notice a database error during migration, you can reset your Statping ins
|
||||||
- In your Statping directory (contains config.yml) run command: `statping export`. This will export all elements into a timestamped JSON file. This file will not include previous hits or failures.
|
- In your Statping directory (contains config.yml) run command: `statping export`. This will export all elements into a timestamped JSON file. This file will not include previous hits or failures.
|
||||||
- Delete `assets` folder if you have one.
|
- Delete `assets` folder if you have one.
|
||||||
- Delete and Recreate MySQL, Postgres database, or delete `statping.db`.
|
- Delete and Recreate MySQL, Postgres database, or delete `statping.db`.
|
||||||
- Import previous data by running: `statping import backup.json` (replace backup.json with your exported filename)
|
- Import previous data by running: `statping import backup.json` (replace backup.json with your exported filename)
|
||||||
|
|
||||||
|
## Deleting Old Records
|
||||||
|
|
||||||
|
- `DELETE FROM hits WHERE created_at < '2020-02-21 00:00:00';` // Delete hits older than
|
||||||
|
- `DELETE FROM failures WHERE created_at < '2020-02-21 00:00:00';` // Delete failures older than
|
Loading…
Reference in New Issue