From bd02fbc3fcf51cf946f3479fc06fb2034d2567bc Mon Sep 17 00:00:00 2001 From: Austin Date: Sun, 26 Jun 2016 01:30:52 -0500 Subject: Update package version to 2.1.0 --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 5635692..d0d0c6d 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "pomf", - "version": "2.0.2", + "version": "2.1.0", "description": "Kawaii file host", "homepage": "https://pantsu.cat/", "repository": { -- cgit v1.2.3 From 77022be248c5ce3e2a92022271277b046130f1ae Mon Sep 17 00:00:00 2001 From: Austin Date: Sun, 26 Jun 2016 01:34:31 -0500 Subject: Reword SQLite migration That was bad --- README.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/README.md b/README.md index ec2101b..8b4a2e6 100644 --- a/README.md +++ b/README.md @@ -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._ -- cgit v1.2.3