Post by hlan on Jun 1, 2010 22:17:34 GMT 7
Hi Matt,
Sorry for the unnecessary injection of adrenalin. This was not my intention and I am glad reading that you recovered your N2200.
When I played with the configuration I sometimes messed things up but ROOTCMD always continued to work for setting things back.
I think the best thing to explore the configuration is downloading the zip file on Misha's site (sometimes it's easier to start from a working example than from scratch). I brushed things over a bit but have not yet posted the update (there seemed to be little interest / urgency and I have many other things to do). In the updated example the suggestion is to do as follows:
- Include in httpd.conf one line for the instruction: "include /raid/data/MyWWW/conf/httpd-include.conf".
Then file "/raid/date/MyWWW/conf/httpd-include.conf" calls any virtual host configuration file you may have, e.g. "/raid/date/MyWWW/conf/vhost-http-50004.conf".
By doing it this way you make - only once at the very beginning - a minimal low-risk modification in the N2200's httpd.conf, and from there on you never need to touch this file file anymore (no editing anymore, no copying).
Any customization then is controlled from the user folder in "/raid/date/MyWWW/conf/httpd-include.conf" and from your local vhost files (in the update I gave 3 examples for http, https, and https mutual authentication). Should for some reason something go badly wrong then it is easy to intervene via the share - just comment out lines in "/raid/date/MyWWW/conf/httpd-include.conf" or empty it out altogether :-)
You manipulation looks alright as for the configuration construct. Points I wonder are
- User folder protection (public=yes, browsable=yes)? Start off with no protection and tighten later?
- Does folder htdocs exist?
- Does the folder for the log files exist? (I guess Apache would create the log files if they do not exist but does not create the folders)? I suggest to remove the log file constructs for a start and add them back later?
Sorry for the unnecessary injection of adrenalin. This was not my intention and I am glad reading that you recovered your N2200.
When I played with the configuration I sometimes messed things up but ROOTCMD always continued to work for setting things back.
I think the best thing to explore the configuration is downloading the zip file on Misha's site (sometimes it's easier to start from a working example than from scratch). I brushed things over a bit but have not yet posted the update (there seemed to be little interest / urgency and I have many other things to do). In the updated example the suggestion is to do as follows:
- Include in httpd.conf one line for the instruction: "include /raid/data/MyWWW/conf/httpd-include.conf".
Then file "/raid/date/MyWWW/conf/httpd-include.conf" calls any virtual host configuration file you may have, e.g. "/raid/date/MyWWW/conf/vhost-http-50004.conf".
By doing it this way you make - only once at the very beginning - a minimal low-risk modification in the N2200's httpd.conf, and from there on you never need to touch this file file anymore (no editing anymore, no copying).
Any customization then is controlled from the user folder in "/raid/date/MyWWW/conf/httpd-include.conf" and from your local vhost files (in the update I gave 3 examples for http, https, and https mutual authentication). Should for some reason something go badly wrong then it is easy to intervene via the share - just comment out lines in "/raid/date/MyWWW/conf/httpd-include.conf" or empty it out altogether :-)
You manipulation looks alright as for the configuration construct. Points I wonder are
- User folder protection (public=yes, browsable=yes)? Start off with no protection and tighten later?
- Does folder htdocs exist?
- Does the folder for the log files exist? (I guess Apache would create the log files if they do not exist but does not create the folders)? I suggest to remove the log file constructs for a start and add them back later?