It seems like spamming the login button or more generic spamming calls causes the databases to be locked.

The /status router should return the current version of the backend. In addition it should be excluded from the validation middleware.

response is {"auth": false, "server_message": "Nickname oder Passwort ist falsch."} but still some weird app version outdated message is displayed

Front camera is chosen when scanning qr-code on an ios device. Makes it hard to scan.

Our web-UI still uses the HTTP default port 80 even though we're encrypting our data using HTTPS. We should adjust the port to another one within the next release.

test

While creating the beerking backend docker image I discovered that somehow the version checker fails. Since I'm not familiar with the frontend codebase please make sure the version header ist send correctly.

Should we limit the match history?

e.g. only last 10 matches and if the user whats to display more he has to do an extra click ("load more...").

Backendsided we (or I) should implemented at least major testcases. In addition we could think about some CICD tools.

There is no difference in the response for a non existing email address and an already existing username.

Pretty much same implementation:
63102b1

Since we're running our file server behind a reverse-proxy it's not necessary to not serve files at root level anymore.

Since we're using one codebase for web-UI and Android app we should be able to remove the cordova core from the repo.

Because of guidelines