···1414 cp gof3r /usr/local/bin
15151616COPY docker-entrypoint.sh /entrypoint.sh
1717+COPY my-mini.cnf /my-mini.cnf
17181819RUN chmod 755 /*.sh
19202020-# TODO: Restore from S3 after we launch the database in the background2121+# TODO: Do something to reduce the MySQL footprint, or get bigger machines
···2233It's essentially "[mysql:5.6](https://registry.hub.docker.com/_/mysql/)" from the official builds on Docker Hub, with a twist. You can find an automated build on [Docker Hub](https://registry.hub.docker.com/u/andrioid/mysql-from-s3/).
4455+Note: This is pretty early and I'm still fighting with a few bugs. It's a work in progress.
66+57## Introduction
6879
81099-MySQL server that will seed the database from a gzipped dump file on S3 when run for the first time.
1111+MySQL server that will seed the database from a gzipped dump file on S3 when run for the first time. I use s3gof3r to stream the compressed dump file from S3.
1212+10131111-I use s3gof3r to stream the compressed dump file from S3.
1414+### MySQL 5.6 and small VPS machines
1515+According to a [bug](https://github.com/docker-library/mysql/issues/3) MySQL 5.6 is not intended to run on tiny boxes. I'm not content with that, so if the server detects that your memory is below 1GB it will load a secondary configuration that will do the following:
1616+1717+- Lower the memory footprint as much as possible
1818+- Disable InnoDB
1919+- Disable Performance Metrics
12201321## Use Cases
1422