H5ai - a beautified Apache index
larsjung.de
H5ai - a beautified Apache index
1–10 of 14 posts
Re: H5ai - a beautified Apache index
#2Re: H5ai - a beautified Apache index
#3Link to source and some screenshots, since the site is quite slow right now: https://github.com/lrsjng/h5ai
Re: H5ai - a beautified Apache index
#4Link to source and some screenshots, since the site is quite slow right now: https://github.com/lrsjng/h5ai
http://webcache.googleusercontent.com/search?q=cache%3Alarsj...
At first I thought this was kind of overkill for such a 'simple' function but the example of Github shows how important effective presentation of a file list can be. To the average web user the default Apache listing can look 'broken' whereas I would have no problem directing a client to the URL of an index that looked like this.
Re: H5ai - a beautified Apache index
#5Re: H5ai - a beautified Apache index
#6Re: H5ai - a beautified Apache index
#7This is quite nice, however, if you are wanting to serve static content I no longer believe Apache the proper tool for the job. Use cherokee, lighttpd or nginx, they are all faster and have decent file interfaces.
Re: H5ai - a beautified Apache index
#8Re: H5ai - a beautified Apache index
#9Re: H5ai - a beautified Apache index
#10Link to source and some screenshots, since the site is quite slow right now: https://github.com/lrsjng/h5ai
As always, Chrome users, prefix the address in the omnibox with 'cache:' to get http://webcache.googleusercontent.com/search?q=cache%3Alarsj... At first I thought this was kind of overkill for such a 'simple' function but the example of Github shows how important effective presentation of a file list can be. To the average web user the default Apache listing can look 'broken' whereas I would have no problem directing…