Overhaul database package

perf/DESIGN.md

 DESIGN
 ======
 
 
 Overview
 --------
 Provides interactive dashboard for Skia performance data.
 
 Code Locations
 --------------
@@ skipping 179 matching lines @@
     $ mysql -h 173.194.104.24 -u root -p
 
 
     mysql> use skia
 
     mysql> show tables;
 
 Initial setup of the database, the users, and the tables:
 
 * Create the database and set up permissions. Execute the following after
-  you connect to a MySQL database (not necessary for SQLite).
+  you connect to a MySQL database.
 
     CREATE DATABASE skia;
     USE skia;
     CREATE USER 'readonly'@'%' IDENTIFIED BY <password in valentine>;
     GRANT SELECT ON *.* TO 'readonly'@'%';
     CREATE USER 'readwrite'@'%' IDENTIFIED BY <password in valentine>;
     GRANT SELECT, DELETE, UPDATE, INSERT ON *.* TO 'readwrite'@'%';
 
 * Create the versioned database tables.
 
   We use the 'migratedb' tool to keep the database in a well defined (versioned)
   state. The 'db_conn_string' flag allows to specify the target database.
   By default it will try to connect to the production environment.
   But for testing a local MySQL database can be provided. If it cannot
-  connect to MySQL it will fall back to SQLite.
+  connect to MySQL it will fall back to a local "test" MySQL database.
 
   Bring the production database to the latest schema version:
 
      $ migratedb -logtostderr=true
 
   Bring a local database to the latest schema version:
 
      $ migratedb -logtostderr=true -db_conn_string="root:%s@tcp(localhost:3306)/skia?parseTime=true"
 
-  Bring a local SQLite database to the latest schema version:
-
-     $ migratedb -logtostderr=true -db_conn_string=""
-
 
 Nginx
 -----
 
 Nginx acts as a proxy to the backend app, which is configured to run on port
 8000, and serves the app on port 443 (HTTPS). Port 80 just redirects to 443.
 The config for the nginx server is held in setup/sys/perf_nginx, which is copied
 into place during installation. Nginx is monitored and kept running by monit.
 
 
@@ skipping 223 matching lines @@
 
 But sysv init only handles starting and stopping a program once, so we use
 Monit to monitor the application and restart it if it crashes. The config
 is in:
 
     /etc/monit/conf.d/perf
 
 Installation
 ------------
 See the README file.