Frühere Vorfälle

The bot is responding again.
Reason for this incident was a misconfiguration (a forgotton slash command name here and there)

It seems the issue has resolved itself.

Everything is back online again.

• the backup service has been implemented
• pm2 is now being used instead of docker