Lock file keeps in place after crash/abort

The flask app, uses a lock file/directory to initiate the migrations (so not all gunicorns do the same upgrade), although this is smart, if flask is aborted during starting, the lockfile can stay in place and prevent future starts of the process.

The lockfile: tmp/dashboard_init/ Where it happend:

app.py:78 init_lock = NamedAtomicLock('dashboard_init') `

a logic solution would be to remove the file if it exists, before gunicorn is started. Need discuss for proper solution

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information