Currently each time the bot crashes or the application is stopped, the complete invite configuration is lost, since its stored in an h2 database.
Have you considered replacing the h2 database with a regular database (for example postgres). Then the data which would be stored in the database would be persistent, which would suit the use of the bot better :)
In case youre interested in a PR, I could contribute that, since I already implemented it in my fork
Currently each time the bot crashes or the application is stopped, the complete invite configuration is lost, since its stored in an h2 database.
Have you considered replacing the h2 database with a regular database (for example postgres). Then the data which would be stored in the database would be persistent, which would suit the use of the bot better :)
In case youre interested in a PR, I could contribute that, since I already implemented it in my fork