Verdaccio
-
|
Your Environment
Describe the bug docker-compose.yaml version: '3.1'
services:
verdaccio:
image: verdaccio/verdaccio
container_name: "verdaccio"
networks:
- node-network
environment:
- VERDACCIO_PORT=4873
ports:
- "4873:4873"
volumes:
- "./storage:/verdaccio/storage"
- "./config:/verdaccio/conf"
- "./plugins:/verdaccio/plugins"
user: "root:root"
networks:
node-network:
driver: bridge
config.yaml storage: ./storage
auth:
htpasswd:
file: ./htpasswd
max_users: -1
uplinks:
npmjs:
url: https://registry.npmjs.org/
packages:
'@*/*':
access: $authenticated
publish: davs
'**':
access: $authenticated
publish: davs
proxy: npmjs
logs:
- { type: stdout, format: pretty, level: http } |
Beta Was this translation helpful? Give feedback.
Answered by
mbtools
Nov 25, 2024
Replies: 4 comments 5 replies
-
|
i have the same issue. are there any updates on this problem? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I also have the same issue. I couldn't find a way to keep the packages listed on the ui so i gave up and stop upgrading. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Oh good I thought it was just me |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
5 replies
-
|
I have a set of data that used to run on version 5.31. data path admin@NAS2:/$ ls /volume1/docker/verdaccio
conf plugins storage
admin@NAS2:/$ ls /volume1/docker/verdaccio/storage/
data
admin@NAS2:/$ ls /volume1/docker/verdaccio/storage/data
outils zutilsdocker container config / docker run config.yaml #
# This is the default config file. It allows all users to do anything,
# so don't use it on production systems.
#
# Look here for more config file examples:
# https://github.com/verdaccio/verdaccio/tree/master/conf
#
# path to a directory with all packages
storage: /verdaccio/storage/data
# path to a directory with plugins to include
plugins: /verdaccio/plugins
# https://verdaccio.org/zh-CN/docs/configuration
security:
api:
migrateToSecureLegacySignature: true
web:
title: Verdaccio
# comment out to disable gravatar support
# gravatar: false
# by default packages are ordercer ascendant (asc|desc)
# sort_packages: asc
# convert your UI to the dark side
# darkMode: true
# logo: http://somedomain/somelogo.png
# favicon: http://somedomain/favicon.ico | /path/favicon.ico
# translate your registry, api i18n not available yet
# i18n:
# list of the available translations https://github.com/verdaccio/ui/tree/master/i18n/translations
# web: en-US
auth:
htpasswd:
file: /verdaccio/conf/htpasswd
algorithm: bcrypt
# Maximum amount of users allowed to register, defaults to "+inf".
# You can set this to -1 to disable registration.
# max_users: 1000
# a list of other known repositories we can talk to
uplinks:
npmmirror:
url: https://registry.npmmirror.com/
npmjs:
url: https://registry.npmjs.org/
packages:
'@*/*':
# scoped packages
access: $all
publish: $authenticated
unpublish: $authenticated
proxy: npmmirror
'**':
# allow all users (including non-authenticated users) to read and
# publish all packages
#
# you can specify usernames/groupnames (depending on your auth plugin)
# and three keywords: "$all", "$anonymous", "$authenticated"
access: $all
# allow all known users to publish/publish packages
# (anyone can register by default, remember?)
publish: $authenticated
unpublish: $authenticated
# if package is not available locally, proxy requests to 'npmjs' registry
proxy: npmjs
# 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
max_body_size: 1000mb
middlewares:
audit:
enabled: true
max_body_size: 1000mb
# log settings
log: { type: stdout, format: pretty, level: http }
#experiments:
# # support for npm token command
# token: false
# # disable writing body size to logs, read more on ticket 1912
# bytesin_off: false
# # enable tarball URL redirect for hosting tarball with a different server, the tarball_url_redirect can be a template string
# tarball_url_redirect: 'https://mycdn.com/verdaccio/${packageName}/${filename}'
# # the tarball_url_redirect can be a function, takes packageName and filename and returns the url, when working with a js configuration file
# tarball_url_redirect(packageName, filename) {
# const signedUrl = // generate a signed url
# return signedUrl;
# }
# This affect the web and api (not developed yet)
#i18n:
#web: en-US
listen: 0.0.0.0:4873
.verdaccio-db.json {"list":["outils","zutils"],"secret":"xxxx same as inhtpasswd "} |
Beta Was this translation helpful? Give feedback.
-
|
what does the verdaccio log show? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
You get the results from cache (304). Empty your browser cache. Also try turning off cache in config: web:
html_cache: false |
Beta Was this translation helpful? Give feedback.
-
|
I can log in normally, so the configuration file is correct. However, the repository path inside the container is empty. It might not be the content of the host machine that I mapped. So, later I mapped them separately, it works now.Thanks. # -v /volume1/docker/verdaccio:/verdaccio
-v /volume1/docker/verdaccio/conf:/verdaccio/conf \
-v /volume1/docker/verdaccio/storage:/verdaccio/storage \
-v /volume1/docker/verdaccio/plugins:/verdaccio/plugins \ |
Beta Was this translation helpful? Give feedback.
Answer selected by
mbtools
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#3943 fixed by #3944