Cookbook
From Resin 3.0
(Difference between revisions)
| Line 4: | Line 4: | ||
; [[Cookbook: Apache-style single webapp server ]] | ; [[Cookbook: Apache-style single webapp server ]] | ||
| + | : using /var/www/public-html as the single webapp | ||
; [[Cookbook: Webapps-style war deployment ]] | ; [[Cookbook: Webapps-style war deployment ]] | ||
| + | : using /var/www/webapps for .war deployment and expansion | ||
; [[Cookbook: Virtual Hosts using Hosts Directory ]] | ; [[Cookbook: Virtual Hosts using Hosts Directory ]] | ||
| + | : using /var/www/hosts/www.foo.com/webapps/ROOT for virtual hosts and webapps | ||
; [[Cookbook: Cluster with Two Servers ]] | ; [[Cookbook: Cluster with Two Servers ]] | ||
; [[Cookbook: Resin Load Balancing ]] | ; [[Cookbook: Resin Load Balancing ]] | ||
Revision as of 23:01, 2 October 2010
Contents |
Full Configurations
- Cookbook: Apache-style single webapp server
- using /var/www/public-html as the single webapp
- Cookbook: Webapps-style war deployment
- using /var/www/webapps for .war deployment and expansion
- Cookbook: Virtual Hosts using Hosts Directory
- using /var/www/hosts/www.foo.com/webapps/ROOT for virtual hosts and webapps
- Cookbook: Cluster with Two Servers
- Cookbook: Resin Load Balancing
- Using Resin as a HTTP server, load balancing to backend application servers
Security
Proxy and Load Balancing
- Cookbook: FastCGI
- using Resin to load balance to a backend FastCGI server like Ruby or PHP
- Cookbook: HttpProxy
- using Resin to load balance to a backend HTTP like Apache or IIS
