Use the database for minter state

[escowles]

Fixes #801

[tpendragon]

Does this mean we can delete that minter_state class we have copied over?

[escowles]

We can copy the minter state from the state file to the database with the rake task:
rake active_fedora:noid:migrate:file_to_database

[tpendragon]

I mean can we delete this: https://github.com/pulibrary/plum/blob/master/app/models/minter_state.rb#L1

[escowles]

@tpendragon I think so — let me test it locally to see.

[escowles]

Yep, it works fine without app/models/minter_state.rb now.

[tpendragon]

I think it was a problem deploying before - can you try deploying that to staging?

[escowles]

I can try it, but it'll fail because of the plum-workers issue.

[coveralls]

Coverage remained the same at 100.0% when pulling aa47859ed6f2a82ffe473f0b9192343edd1ba421 on db-minter-state into cdb3096 on master.

[coveralls]

Coverage decreased (-0.1%) to 99.898% when pulling b3178fd99b2301c39412c28a89cc2ffb90480103 on db-minter-state into cdb3096 on master.

[escowles]

This build is deployed to staging and working now. To get the db minter working, I had to clear out an invalid seed before migrating the minter state (see instructions: https://gist.github.com/escowles/c5f1b505954ab368fa659614a2a85610)

[coveralls]

Coverage remained the same at 100.0% when pulling 11db702ab2d2942f3976298a471d3773ec64bfb9 on db-minter-state into cdb3096 on master.

[escowles]

One more thing before merging this: I changed the development database connect to use Postgres to make it easier to test — I'll change it back to sqlite now.

[coveralls]

Coverage remained the same at 100.0% when pulling 97899a2 on db-minter-state into cdb3096 on master.