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

Make config.host dynamic #5

Open
smonff opened this issue Apr 27, 2016 · 3 comments
Open

Make config.host dynamic #5

smonff opened this issue Apr 27, 2016 · 3 comments

Comments

@smonff
Copy link

smonff commented Apr 27, 2016

When you use the validator extensively, it sometimes makes sense to use a local instance of it, either because you don' t want to flood the validator, but also because, during the development process, all you files are not available from the outside world, and you don' t always work on open source projects.

If a parameter could be use for the config.host value, it would be appreciated.

@gchudnov
Copy link
Owner

Hi @smonff,
Thanks for feedback!

Agreed, that's a problem. I'll look into it.

@gchudnov
Copy link
Owner

gchudnov commented May 2, 2016

The support of a local instance is on the way..

Just added Dockerfile to deploy the validator locally.

@gchudnov
Copy link
Owner

gchudnov commented May 3, 2016

Relesed 2.0.0

Added an option to specify a custom server:

  • server - the "IP:PORT" string or the URL object of a custom validation server, e.g, '172.17.0.2:8080' or { host: '172.17.0.2:8080' } or { hostname: '172.17.0.2:8080', port: 8080 }

Added npm run scripts to run the validation server locally in a docker container.

An updated readme is here

Let me know if there are any problems.

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

No branches or pull requests

2 participants