There are a lot of options in persistConfig that aren't mentioned in the README. We should add a section to the README that documents each option you can declare in a persistConfig.

As stated in the title, we need to add basic promtool tests for all the alerts we have in mixin. At the very least, they will help us to catch templating issues with our alerts.

Describe the bug

Phone verification is not sent after the user signs up.

Detailed Description and Steps to Reproduce

I'm using aws-amplify for my React Native project. I want to sign users with phone number and send SMS immediately after they sign up. I tried to do that using eu-central-1 (Frankfurt), us-east-1 (N. Virginia), and eu-west-2 (London). Although I see that t

I read the docs of dexie-export-import thoroughly, however I didn't find a way how to add onto the current database when importing the data. It either completely replaces the whole table or merges and overwrites any row with the same id.

What I'd like to do is to import the data with new id's, while keeping the old data in the table intact.

Here is an issues with detailed description: NekR/offline-plugin#77

Where is the list of abbreviations used in the standard? The term "UA" is used extensively throughout the text but not explained anywhere...

https://html.spec.whatwg.org/commit-snapshots/009a7316ad7f1b69de978101b043b9b29878d975/#table-of-contents

We want to have consistent and structured logs to improve the ability to filter and analyse longhorn-manager logs.
Currently the controller uses the global logrus package logger, the task here would be to switch the log calls to the instance logger that was implemented in longhorn/longhorn-manager#661

While doing this also improve the log messages, where possible.
For an example of a successf