registry

Your Environment
Not applicable. The issue is related to documentation.

Describe the bug

The Google Cloud documentation is non existent, even worse it displays jibberish.

• Markdown File: https://github.com/verdaccio/verdaccio/blob/master/website/docs/google-cloud.md
• Docs Site Link: https://verdaccio.org/docs/google-cloud/

To Reproduce

1. Visit [Docs > Google Cloud](ht

The (still undocumented) feature is great for our purpose, but can you add the same functionality to the post-update hook (in the same manner, of course)?

I have added a script to the post-update to check the database-version. If they not match, the script returns exit 1. It would be great if the post-update hook could log a error- or warning-message, so the slack-notification gets a message (l

While I love minimal containers, ones that leave the package manager off make it difficult to work inside the container.

The GitLab example (thank you for that!) is an example where the job run inside the container - and with the package manager not present, it is challenging to add jq.

Since all the output of crane is json, would it be possible to install jq on the debug tag - or at least t

Issue Description

When i write a plugin, i can use "on" to specify where should it run.

Now, "on" support master/node, HOWEVER, when i want one plugin run on both master and node, i need to write two same plugin, and on

this is work:
skpm-build --output ../../../Library/ApplicationSupport/com.bohemiancoding.sketch3/Plugins/test.sketchplugin
bug, this is not work:
skpm-build --output ~/Library/ApplicationSupport/com.bohemiancoding.sketch3/Plugins/test.sketchplugin

With Trow moving to use Rocket 0.5, the way configuration is handled has changed. Rocket now uses the much more flexible figment system: https://docs.rs/figment/0.10.6/figment/index.html.

We can really clean up a lot of needlessly confusing code and also support of config file by taking advantage of figment. Basically the same figment config would be passed to the Trow frontend, Rocket and the

Most of our current tests mock away the DB because they're focused on the application logic and external API. We have seen changes breaking some DB queries without being caught by tests from time to time. We should improve the situation by adding tests that run the DB queries defined in our entity / DTO repositories and assert no DB error, just to ensure that the queries are consistent with the sc

Repro Steps

Follow steps from: https://github.com/oras-project/artifacts-spec/blob/main/docs/quick-start.md

At the oras discover step, note the output is:

oras discover $PUBLIC_IMAGE -o json | jq
{
  "digest": "sha256:a0fc570a245b09ed752c42d600ee3bb5b4f77bbd70d8898780b7ab43454530eb",
  "references": [
    {
      "digest": "sha256:6200e3cfb0a036bdc585f99cee2ace9926f327d58