magnetikonline / docker-html5-validator

Docker self contained W3C/HTML5 validator instance.

Docker W3C/HTML5 validator instance

Dockerfile for the creation of a self contained W3C Markup validator (with HTML5 validation) instance for fast/offline validation of authored HTML documents.

Setup of such a configuration can be tricky and a little messy so having all this in an isolated and automated way seemed like a good idea.

Building

To build the Docker image, run the following:

$ ./build.sh

This will take some time - performing the following tasks:

• Install Ubuntu base (16.04 LTS), Apache HTTP server, OpenJDK 8, supervisord and a few others.
• Download latest W3C validator source and Validator.nu vnu.jar portable HTML5 validator jar.
• Configure Perl/CPAN.
• Install and configure W3C validator (including Validator.nu setup).
• Start Apache and Validator.nu under supervisord.

That's the boring/messy stuff out of the way - your new Docker image should now be built.

Alternatively you can pull this image directly from Docker Hub:

$ docker pull magnetikonline/html5-validator

Running

To start the image, run the following:

$ ./run.sh

This will start the image in a new backgrounded container, exposing the following ports:

• Port 80 (Apache2) presented to host on 8080.
• Port 8888 (Validator.nu Java server) presented to host on 8888.

Running the container on alternative local ports is controlled via docker run --publish arguments.

With this complete you should now be able to browse to http://localhost:8080/ and be presented with a working W3C validator instance.

docker-html5-validator's Issues

except localhost, nothing else is working

hi,

except localhost, it's not working because your apacheserver is always resend result in localhost.
So I know that you certainly only want the usecase of a docker engine installed on the localmachine where you are working out but there are a lot more usecase;
For example, you can imagine someone working on a tablet or a phone to rapidly make changes to an html file and he want to test it. So because of your one usecase, he will have to connect to the online website to validate the modification he just did.
Other usercase, every windows computer doesn't allow to use docker because of the CPU which has not vt-x etc. ... And sometimes you don't have internet but just your intranet so it could be great if you could change it to make it work on 0.0.0.0 and not only localhost? if it is possible. If I had the time right now I would gladly do it myself but I will have to wat a few more weeks if I have to do it myself and it would be great if I could use it right now....

Allow Private IPs

Thank you for creating this container.

I would like to check HTML on a non-public address.
Can you Edit validator.conf and change Allow Private IPs = no to Allow Private IPs = yes?
http://blog.simplytestable.com/installing-the-w3c-html-validator-with-html5-support-on-ubuntu/

Thank you for your cooperation.

build not working

Hi,

first of all - nice idea - thanks for creating this :).

I ran into the following error:

~/p/dockerhtml5validator git:master ❯❯❯ ./build.sh
Password:
2014/06/19 22:29:53 Post http:///var/run/docker.sock/build?  
rm=1&t=magnetikonline%2Fhtml5validator: dial unix /var/run/docker.sock: no such file or 
directory

Any idea what's wrong? As you have written in the README, trying to use docker pull did not work.

Thanks

Andy

Sometimes results deviate from the live W3C Validator

Hello,

Thanks a ton for this great self contained W3C Markup validator. I had been checking the results after building this container, but the results sometimes vary from the live W3C Validator (http://validator.w3.org/).

These are the names of some sites for which you would see that the results deviate from the hosted one:

grantwatch.com
merruk.com
tarnegarco.com

It would be helpful if the validator container can be updated and it can be made to return results similar to the live one to avoid ambiguity. Thought this info would be of some help to you and thanks once more for this great repo.

Thanks,
Avik