503 service unavailable validating URLs about linter HOT 7 CLOSED

I'll try to see what I can figure out going through the logs. If you depend on this as part of a workflow, you might consider cloning it and installing on a local server; it's completely unencumbered open-source.

from linter.

Sorry, your request fell off of the logs, and I don't really see any evidence of a crash or bad status; may be a Heroku routing issue. I would suggest running locally to see if you can reproduce the issue; you can attach a log if you find something.

from linter.

OK thanks for the info, I will have a go at a local install. It's only intermittent, so it's clearly a transient problem. Thanks for looking into it for me.

from linter.

Seems to work fine locally so must be a network issue. I'm considering integrating into our build, but is it possible to use the backend validator without spinning up a web server? Ideally I would just run a command e.g. linter http://www.mysite.com/mypage.html and it would output the JSON saying if it was valid or not.

from linter.

You can use the linter as a library gem. If you look at the Parser module, you can use this to parse and reason over your input to get back a list of found issues. You could also use other methods in that module, or from the rdf-reasoner gem.

from linter.

@gkellogg In the end I just made our tests download rbenv and linter and then called the parser directly, writing the json to stdout. Seems to work ok so far, I'll see how the reliability goes!

Not sure if it is worth feeding back anything to here, I suspect there's nothing but plumbing there. But if you want any of it I'm happy to do a PR here too!
guardian/frontend-sanity-tests#16

from linter.

Thanks, don't really see anything there that's generically useful. If you come up with something in the future, please reach out again.

from linter.