Makes more sense to run `./bin/setup` from the root.

* Move the `make run` target into the project root's Makefile
* Update paths in lighttpd.conf to correspond to its new location

I want to be able to run `make run` from the project root.

Include the new step 2 of installation, starting the program with `brew
services`.

After the license has been added, the daemon must be restarted in order
for the license to be recognised.

License the software with the GNU AGPLv3+ with the exception of the
'aquatic-prime' and 'paddle' libraries and 'aquatic-prime' binary, which
are licensed under the GNU GPLv3+.

Forgot to change this when I changed the function signature.

Published my local fork publicly with the base64 format change.

For whatever reason, the environment variables in my `.htaccess` weren't
getting passed to my FastCGI executables on my production server.

Wasn't sure how to get them passed to the programs, so decided instead
to compile the env variables into the binaries.

To do that, we source the environment file before building the release
builds in the Docker container.

Got this error from the production MySQL server:

    (details: Error 1235: This version of MySQL doesn't yet support
    'multiple triggers with the same action time and event for one table')

Change our triggers so we only have one for `BEFORE INSERT`.

Ended up with this error when running my migrations against the
production server:

    error: migration failed in line 0: BEGIN;

    CREATE TABLE purchasers (
        id INT AUTO_INCREMENT PRIMARY KEY,
        name VARCHAR(255) NOT NULL,
        email VARCHAR(255) NOT NULL,
        secret VARCHAR(255),
        created_at DATETIME NOT NULL DEFAULT UTC_TIMESTAMP(),
        updated_at DATETIME NOT NULL DEFAULT UTC_TIMESTAMP()
    );

    CREATE TRIGGER purchasers_updated_at
        BEFORE UPDATE
        ON purchasers FOR EACH ROW
            SET NEW.updated_at = UTC_TIMESTAMP();

    COMMIT;
     (details: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'UTC_TIMESTAMP(),
        updated_at DATETIME NOT NULL DEFAULT UTC_TIMESTAMP()
    );

    CR' at line 6)

Using MySQL 5.6.34 in production and MariaDB 10.3.10 locally. Guess you
can't use `DEFAULT UTC_TIMESTAMP()` there.

To use `UTC_TIMESTAMP()`, create a couple new triggers to set the
timestamp in the `created_at` and `updated_at` columns.