Execute the following commands, before pulling:
docker-compose up -d
docker-compose exec postgres pg_dump danbooru2 -U danbooru > backup.sql
docker-compose down
docker volume rm e621ng_db_data
Execute the following commands, after pulling:
docker-compose up -d
docker-compose exec -T postgres psql -d e621_development -U e621 < backup.sql
This also changes the name of the database and role.
Now seems like a nice opportunity to do so.
Remove whenever, it's not used in prod. Prod uses systemd timers.
This executes the daily task on container startup. My PC isn't going to
run when this would execute 99% of the time.
My intention was to share it between the test/main service (I think).
But since it's using the main one as a base anways it's already there.
This volume overlays on the one from newer builds, hiding js package changes.
public_packs_test is unused as well, remove.
* Allow modifying .env without git complainging about changes to commit
* Require COMPOSE_PROFILE=solargraph for solargraph to be included in the image
* Set required vscode settings for solargraph to correctly work in docker
* Clean up .solargraph.yml. All these removed values are the default
* Disable autocomplete in the rails console
* Add a compose service to run rubocop
* Upddate rubocop config
Added some, removed some, ordered alphabetically.
Before: 844 files inspected, 6871 offenses detected, 6095 offenses autocorrectable
After: 844 files inspected, 8024 offenses detected, 7538 offenses autocorrectable
Most of the new offences are because of Style/StringLiterals (1312)
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
