Peruser Frequently Asked Questions

This needs to be updated.

What operating systems does peruser work on?

I'm targetting Linux exclusively, myself, as that's what I need peruser to run on. Unfortunately, I can't do much with bug reports for operating systems other than Linux; however, I'll gladly accept any patches as long as they're compatible with Linux.

Does peruser support mod_ssl?

Experimental support for mod_ssl has been added as of version 0.2.0. Another option is to use an SSL-enabled reverse proxy, such as Pound, which also has load-balancing features. See  http://www.apsis.ch/pound/ for details.

Is peruser ready for production use?

In general, no. Although I run it on this production system, if it breaks I can usually fix it, or revert to an older version that does work. At this point the project needs developers and testers more than end-users. However, if you really want to run it on a production system, just be sure to test it thoroughly first, and remember there is no warranty. If it breaks, you get to keep both pieces :)

Is peruser as scalable as vanilla apache?

No. Regular apache uses its entire pool of processes to handle all incoming requests; while peruser allocates smaller pools of processes assigned to different virtual hosts. This can never be as efficient. My suggestion is to load up on RAM, and perhaps utilize the load-balancing features of Pound and run multiple webservers.

Is KeepAlive supported?

It is supported as of version 0.3.0.