Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V5.21.1 Doesn't considers logo #3612

Closed
arathore-gaming opened this issue Feb 15, 2023 · 4 comments · Fixed by #3636
Closed

V5.21.1 Doesn't considers logo #3612

arathore-gaming opened this issue Feb 15, 2023 · 4 comments · Fixed by #3636

Comments

@arathore-gaming
Copy link

For web i have given logo as a .png file but web interface still shows default verdaccio logo.
This was working fine in v5.20.1 for me, issue occurred after upgrading

@juanpicado
Copy link
Member

Thanks, I was afraid this might happens, could you share your config so I can reproduce ?

@arathore-gaming
Copy link
Author

arathore-gaming commented Feb 16, 2023

Following is the config -

# path to a directory with all packages
storage: ./storage
# path to a directory with plugins to include
plugins: ./plugins

web:
  enable: true
  title: Ingenuity NPM Repo
  gravatar: true
  darkMode: true
  scope: "@quest"
  showInfo: false
  showSettings: true
  showFooter: true
  showSearch: true
  showDownloadTarball: true
  showRaw: false
  logo: http://10.0.0.217:8082/images/logo.png
  favicon: http://10.0.0.217:8082/images/favicon.ico
  pkgManagers:
    - npm

auth:
  htpasswd:
    file: ./htpasswd
    # Maximum amount of users allowed to register, defaults to "+inf".
    # You can set this to -1 to disable registration.
    # max_users: 1000
    # Hash algorithm, possible options are: "bcrypt", "md5", "sha1", "crypt".
    algorithm: bcrypt # by default is crypt, but is recommended use bcrypt for new installations
    # Rounds number for "bcrypt", will be ignored for other algorithms.
    rounds: 10

packages:
  '@quest/*':
    # scoped packages
    access: $authenticated
    publish: arathore
    unpublish: arathore

# You can specify HTTP/1.1 server keep alive timeout in seconds for incoming connections.
# A value of 0 makes the http server behave similarly to Node.js versions prior to 8.0.0, which did not have a keep-alive timeout.
# WORKAROUND: Through given configuration you can workaround following issue https://github.com/verdaccio/verdaccio/issues/301. Set to 0 in case 60 is not enough.
server:
  keepAliveTimeout: 60

middlewares:
  audit:
    enabled: true
    
security:
  api:
    jwt:
      sign:
        expiresIn: 360d
        notBefore: 1
    web:
      sign:
        expiresIn: 360d

# log settings
logs: { type: file, path: verdaccio.log, format: pretty-timestamped, level: http }

listen: 0.0.0.0:4873

# experiments:
#  # support for npm token command
#   token: false
#  # support for the new v1 search endpoint, functional by incomplete read more on ticket 1732
#   search: false
#  # disable writing body size to logs, read more on ticket 1912
#   bytesin_off: false

@juanpicado
Copy link
Member

Thanks, I'll work on this and just wait the next release, when is ready I'll post here again.

@juanpicado
Copy link
Member

https://github.com/verdaccio/verdaccio/releases/tag/v5.21.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants