On my MariaDB installation where I have page compression enabled by default (https://mariadb.com/kb/en/innodb-page-compression/)
which the official documentation recommends on the page for COMPRESSED row format (https://mariadb.com/kb/en/innodb-compressed-row-format/).

While page compression is enabled by default, DB migrations that create new tables fail as ROW_FORMAT=COMPRESSED can not be us

Description
The docs confused me a bit today: the Renderers page lists the gpg renderer as a text renderer. At the same time the salt.rendereres.gpg page uses it as a data renderer (last in the pipeline). This confused me for

API documentation for nodejs client for hydra returns a 404

The link mentioned in the documentation: https://github.com/ory/hydra/blob/master/sdk/js/swagger/README.md

Describe the bug

Experimenting happy path on devfile registry, I tried to change the devfile registry policy to IfNotPresent instead of default Always but it was always resulting in error:

12:53:34] ✅  Post installation checklist [failed]
[12:53:34] → Failed to download image, reason: ImagePullBackOff, message: Back-off pulling image "che-devfile-registry-image:latest".
 ›   Err

I like how Simplepush presents a couple of different ways to generate push messages on their website:

https://simplepush.io/#libraries

How about having a similar feature directly in the server GUI? That would include the bits documented here https://gotify.net/docs/pushmsg