Cookbook
From Resin 3.0
(Difference between revisions)
Line 14: | Line 14: | ||
: cluster configuration describing how to add multiple servers to a cluster | : cluster configuration describing how to add multiple servers to a cluster | ||
; [[Cookbook: Resin Load Balancing ]] | ; [[Cookbook: Resin Load Balancing ]] | ||
− | : Using Resin as a HTTP server, load balancing to backend application servers | + | : Using Resin as a HTTP server, load balancing to backend Resin application servers |
; [[Cookbook: Resin administration ]] | ; [[Cookbook: Resin administration ]] | ||
: Configuring the /resin-admin service on port :8081 | : Configuring the /resin-admin service on port :8081 |
Revision as of 23:33, 2 October 2010
The Resin Cookbook category contains single-configuration examples, each focused on a single Resin configuration.
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
- cluster configuration describing how to add multiple servers to a cluster
- Cookbook: Resin Load Balancing
- Using Resin as a HTTP server, load balancing to backend Resin application servers
- Cookbook: Resin administration
- Configuring the /resin-admin service on port :8081
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
Networking
- Cookbook: Throttling HTTP by Remote IP
- protecting the server against attacks by limiting connections from a single IP address