registry

Platform

• version: verdaccio/verdaccio:nightly-master
• platform: docker

Describe the bug
Most of the settings changed in the config.yaml file are not applied.

To Reproduce

web:
  title: "Custom Title" => works
  darkMode: false => works
  showInfo: false => don't works
  showSettings: false => don't works
  showThemeSwitch: false => don't works

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

From the cosign slack: https://sigstore.slack.com/archives/C01PZKDL4DP/p1645810670957869

Registries that don't accept non-distributable (aka foreign) layers by default (like distribution/distribution, see distribution/distribution#2795) may result in confusing errors, like

map[]; MANIFEST_BLOB_UNKNOWN: blob unknown to registry; sha256:bd0b37167cd3d731eb15196e

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