From 1f3081471b33065c8af4a05b6320c41fd0891cae Mon Sep 17 00:00:00 2001 From: cube Date: Thu, 28 May 2026 00:41:11 +0000 Subject: [PATCH] Update README.md --- README.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 5336cdb..b13b51c 100644 --- a/README.md +++ b/README.md @@ -60,11 +60,9 @@ flask --app myriad register-admin --username EXAMPLE_USER --password EXAMPLE_PAS there are currently various ways to export and import data for use within myriad. individual member exports and imports deal only with the fields (though icons, stamps, and blinkies can be exported to a zip folder). they're designed to be used with an active database for whatever purpose the user requires. -the other option is to export the entire system to json or zip file. **importing an entire system is best used on a completely empty database, as it deals with inserting id fields**. a full system import is useful for when an update is released that requires the database to be re-initialised, you can quickly restore information and images you had before. +the other option is to export the entire system to json or zip file. **importing an entire system is best used on a completely empty database, as it deals with inserting id fields**. if the database is not completely empty, there may be some weird importing errors. a full system import is useful for when an update is released that requires the database to be re-initialised, you can quickly restore information and images you had before. -both are a little janky as they've just been implemented rather quickly to cover the base requirement of being able to migrate the database in some form. **don't rely on them, be sure to keep your own backups**. - -**individual member import via zip folder is not currently possible** +**please don't rely entirely on our software, be sure to keep backups of your own data**. # Development set up (Windows)