Do not require database about gfregression HOT 5 OPEN

It previously didn't have a db. By not having a db, we ran into concurrency issues very easily when we had more than one user.

If every user is running there own instance, then yeah a dbless app is just fine.

I guess there could be an option to "save" the comparison.

from gfregression.

What were the root causes of the concurrency problems?

from gfregression.

Having two users using the same instance to test fonts. without persistency, the 2nd user will overwrite the 1st user's data.

from gfregression.

We also have a cmd line tool which uses GFR to gen diff screenshots. The state of a comparison must be saved so a url can be genned which is then passed to Browser Stack

from gfregression.

Hm. what would it take to make GFR resilient to users and command-line tools? Creating an instance per session?

from gfregression.