Add more documentation

docs/API.md

@@ -36,6 +36,8 @@ If the key is invalid returns a 404, same with all children API Endpoints
 
 ## File Deletion - `/edit/<key>/delete` (also `/delete/<key>` for backwards compatibility.)
 
+Accepts GET and DELETE - as long as it has the keys.
+
 Deletes the file with the corresponding key. This is immediate and permanent.
 
 ## File expiry Change - `/edit/<key>/ttd`

docs/DB.md

@@ -0,0 +1,26 @@
+# Database documentation
+
+Database should store everything in 1 db, multiple 2 or 3, because easy.
+
+## files.db
+
+### files table
+
+- **file** as text - contains the filename
+- **expiry** as int - contains unix time of when the file will be deleted - AS COMPUTED BY ENGINE MODE. (this is kept as is, never changed after initial upload)
+- **expiry_override** - _can_ contain unixtime of when the file will actaully be deleted, if it's set, this is used for overriding files.
+- **views** - counts up for each view to the file.
+- **isDeleted** - simple flag to archive the thing in the DB.
+- **adminkey** - key for deletion and setting expiry_override
+- **accessed** - last time the file was accessed
+- **filesize** - size of the file, in kb or something idk
+
+### qrscan table
+
+- **time** as int - when the qr code was scanned
+- **ip** as text? - who scanned it.
+- **version** as int - simple int for the version of qrcode, so I can track what edition the qrcodes are. (/qr1/2/3/4/5/6)
+
+### stats table
+
+Hopefully we can move away from having a separate stats table, and use metrics generated from the files table instead.

static/site.webmanifest

@@ -0,0 +1 @@
+{"name":"","short_name":"","icons":[{"src":"/android-chrome-192x192.png","sizes":"192x192","type":"image/png"},{"src":"/android-chrome-512x512.png","sizes":"512x512","type":"image/png"}],"theme_color":"#ffffff","background_color":"#ffffff","display":"standalone"}