use apache instead of fakewww

[GoogleCodeExporter]

Instead of using fakewww, it'd probably be good to make use of apache 
(especially for the RPMs). I've attached an ndt.conf that can be placed in 
/etc/httpd/conf.d and will function just like fakewww (listen on port 7123, 
etc).

It'd be good to have others comment on whether the RPMs should default to using 
this, and if others could test, that'd be great. Also, if folks who are better 
versed in apache-isms could make sure I'm not doing anything stupid with the 
config file, that'd be good.

Original issue reported on code.google.com by AaronMat...@gmail.com on 21 Apr 2013 at 4:38

Attachments:

• ndt.conf

[GoogleCodeExporter]

+1 on serving via Apache vs. fakewww - that's the mode in which I've run it for 
a while w/o issue.  In the config, I think your <Directory> stanza needs to be:

    <Directory /usr/ndt/>
        DirectoryIndex tcpbw100.html
        AllowOverride None
    </Directory>

You may also wish to send the logs to /var/log/httpd, vs. /var/log/ndt

As far as making this the default, as long as you continue to run on :7123, you 
should be fine.  If you want to serve it on 80/443 (to make the site easier to 
discover, simplify firewall configuration, etc.), you'll need to work out the 
interaction with the other content served via Apache, using vhosts or rewrites.

Original comment by thr...@gmail.com on 22 Apr 2013 at 4:54

[GoogleCodeExporter]

Hi Aaron,

isn't this already implemented in the upcoming NDT-3.7.0?

Original comment by jslawin...@soldevelo.com on 25 Jun 2014 at 8:29

[GoogleCodeExporter]

Original comment by jslawin...@soldevelo.com on 25 Jun 2014 at 8:30

• Added labels: Milestone-Future

[GoogleCodeExporter]

I committed the apache config file above, but getting the RPM to use it is more 
work.

Original comment by AaronMat...@gmail.com on 25 Jun 2014 at 2:26