To see the changes persisted into the container run `docker-compose` build
`docker-compose down -v` no longer requires to reinstall gems/packages
It's also possible to have branches with different gemfiles, without having
to install between them constantly
* Fix boolean value in compose file. I just removed the variable altogether,
the iqdb site already checked against iqdbs_server.present? anyways
* Add checksum check for iqbd download
* Fix newline in iqdb patchfile
* Mark secrets as development only
* Parallelize test_parser build. I don't think there are enough files
to even hit the limit for me but good practice nontheless
* Rebuild postgres when test_parser changes. There has been no activity
in 6 years and I don't expect this to change
* Use alpine as the base image
* Parallelize bundle install
Using alpine as base make is feasable to use the provides vips library.
The version is actually newer than what was installed previously.
Other stuff I did:
* Set SECRET_TOKEN/SESSION_SECRET_KEY from docker-compose
* Mute elasticsearch startup logspam
* Execute image as root. This means mounted volume do'nt need to be chowned
* Reduces the image size by using alpine and cleaning up after some things
* Simplify the initial setup instructions slightly
* Access via localhost:3000 instead of e621.local
