Cookbook
From Resin 3.0
(Difference between revisions)
Line 31: | Line 31: | ||
; [[Cookbook: Security with User in Role ]] | ; [[Cookbook: Security with User in Role ]] | ||
; [[Cookbook: Security with Ssl ]] | ; [[Cookbook: Security with Ssl ]] | ||
+ | ; [[Cookbook: Custom Authenticator with FormLogin and UserInRole ]] | ||
+ | : creating a Custom Authenticator with form login | ||
== Proxy and Load Balancing == | == Proxy and Load Balancing == |
Revision as of 19:27, 15 November 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: Two Cluster Load Balancing
- Load balancing /foo and /bar to two separate backend clusters
- Cookbook: Resin administration
- Configuring the /resin-admin service on port :8081
- Cookbook: Resin behind SSL Load Balancer
- Redirects and SSL security handling with Resin as a backend
Installation
- Cookbook: Windows Service
- Installing and starting Resin as a windows service
Security
- Cookbook: Security with User in Role
- Cookbook: Security with Ssl
- Cookbook: Custom Authenticator with FormLogin and UserInRole
- creating a Custom Authenticator with form login
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