Switch from MariaDB to files

Using a database is way more complex (see the commit statistics of this
commit) than using files to store recipe data. Also administration and
usage is simpler.

2 files changed, 0 insertions, 43 deletions

diff --git a/sql/0001_migration.sql b/sql/0001_migration.sql
deleted file mode 100644
index 9502e6c..0000000
--- a/sql/0001_migration.sql
+++ /dev/null
@@ -1,18 +0,0 @@
-
---------------------------------------------------------------------------------
-
--- This migration script adds the initial version of the Ceres database.
--- Run this migration via `sudo mariadb -u root < 0001_migration.sql`.
-
--- create database for ceres, add ceres user and set privileges
-CREATE DATABASE IF NOT EXISTS ceres;
-
--- select correct database for the rest of this script
-USE ceres;
-
--- create meta table and set database schema version
-CREATE TABLE IF NOT EXISTS meta (
-	identifier varchar(80) PRIMARY KEY NOT NULL UNIQUE,
-	value varchar(80) NOT NULL
-);
-INSERT INTO meta (identifier,value) VALUES ('version', '1');
diff --git a/sql/0002_migration.sql b/sql/0002_migration.sql
deleted file mode 100644
index 7c99616..0000000
--- a/sql/0002_migration.sql
+++ /dev/null
@@ -1,25 +0,0 @@
-
---------------------------------------------------------------------------------
-
--- This migration creates the initial version of the database layout.
-
--- Run this command as Linux user `ceres` with this command:
--- `mariadb < 0002_migration.sql`.
-
--- set database for this script
-USE ceres;
-
--- create recipe table
-CREATE TABLE IF NOT EXISTS recipes (
-	id INT UNSIGNED PRIMARY KEY NOT NULL AUTO_INCREMENT,
-	title varchar(80) NOT NULL DEFAULT '(no title)',
-	upstream_url varchar(200) NOT NULL DEFAULT '',
-	description_markdown text NOT NULL DEFAULT ''
-);
-
--- update database schema version
-UPDATE meta
-SET
-	value='2'
-WHERE
-	identifier='version';