diff options
| author | Austin <austi_gillm935@ahapps.anoka.k12.mn.us> | 2016-06-26 08:34:31 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-06-26 08:34:31 +0200 |
| commit | 77022be248c5ce3e2a92022271277b046130f1ae (patch) | |
| tree | 2f94606a2a4a657a4b90f9b9453a37c04c6f2937 | |
| parent | bd02fbc3fcf51cf946f3479fc06fb2034d2567bc (diff) | |
Reword SQLite migration
That was bad
| -rw-r--r-- | README.md | 7 |
1 files changed, 1 insertions, 6 deletions
@@ -104,12 +104,7 @@ configuration file. ### Migrating from MySQL to SQLite -MySQL is relatively complicated to administer, brings in many unneeded dependencies, and consumes -more resources than SQLite would, and result in worse performance for pomf. Additonally, poorly configured installations have the potential -to pose a security risk. - -Fortunately, it is incredibly simple to migrate your database. This may be done on a live server, and should require -zero downtime. +For older versions of Pomf you may want to migrate to SQLite. Fortunately, it is incredibly simple to migrate your database. This may be done on a live server, and should require zero downtime. _If doing this on a live server, you way wish to work in a subdirectory (or vhost, or equivelant), so that any complications or mistakes do not affect your main site. If you choose not to do so, know that mistakes in the changes outlined below, will only temporarily impact **uploading**, causing **Server error** to be displayed. None of these steps are destructive, and are easily reverted._ |