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

Problem with docker.yaml #72

Merged
merged 1 commit into from
Nov 16, 2016
Merged

Problem with docker.yaml #72

merged 1 commit into from
Nov 16, 2016

Conversation

josemanu
Copy link

There is a problem with the docker.yaml file.

auth:
   htpasswd:
     file:/verdaccio/config/htpasswd

The file property should point to /verdaccio/conf/htpasswd because folder /verdaccio/config dosen't exist and therefore dosen't let to create users.

Thank you for working on this great tool.

Regards

There is a problem with the docker.yaml file.

auth:
   htpasswd:
     file:/verdaccio/config/htpasswd

The file property should point to /verdaccio/conf/htpasswd because folder /verdaccio/config dosen't exist and therefore dosen't let to create users.

Thank you for working on this great tool.

Regards
@jmwilkinson
Copy link
Contributor

@josedepaz Thanks for this bug fix. I'm not sure where this config parameter is used. Do you know where we are using it in verdaccio?

@josemanu
Copy link
Author

josemanu commented Oct 26, 2016

Hi @jmwilkinson, this config parameter is used in /lib/plugins/htpasswd/index.js, line 30 self._path = Path.resolve(Path.dirname(self._sinopia_config.self_path), file) when the plugin is loaded with /lib/plugin-loader.js. This path comes from the original config.yaml location /verdaccio/conf/config.yaml using /lib/config-path.js to find the config path /verfaccion/conf/.

The config.yaml is set in the Dockerfile in the CMD.

CMD ["/usr/src/app/bin/verdaccio", "--config", "/verdaccio/conf/config.yaml", "--listen", "0.0.0.0:4873"]

@jmwilkinson jmwilkinson merged commit 03d66b0 into verdaccio:master Nov 16, 2016
@lock
Copy link

lock bot commented May 31, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators May 31, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants