Umlaut Deployment - Revision history

Jrochkind at 16:19, 19 June 2012

2012-06-19T16:19:30Z

Scotdalton at 15:02, 7 April 2011

2011-04-07T15:02:33Z

Scotdalton at 15:00, 7 April 2011

2011-04-07T15:00:57Z

Scotdalton at 14:59, 7 April 2011

2011-04-07T14:59:51Z

128.220.205.186: /* Apache Setup */

2010-09-27T14:03:54Z

‎Apache Setup

128.220.205.186 at 14:02, 27 September 2010

2010-09-27T14:02:44Z

Jrochkind: /* Setting up mongrel_cluster */

2009-06-19T15:17:52Z

‎Setting up mongrel_cluster

Scotdalton: /* Prerequisites */

2009-05-26T19:51:36Z

‎Prerequisites

Scotdalton: /* Apache Setup */

2009-04-27T19:22:12Z

‎Apache Setup

Scotdalton: /* Apache Setup */

2009-04-27T19:21:40Z

‎Apache Setup

← Older revision		Revision as of 16:19, 19 June 2012
Line 1:		Line 1:
		+	=WARNING: This is Outdated Documentation!!!!=
		+
		+	'''THIS IS OUTDATED DOCUMENTATION''' See new Umlaut documentation at http://github.com/team-umlaut/umlaut/wiki
		+	---------
		+
	[[Category:Umlaut]]		[[Category:Umlaut]]

@@ Line 11: / Line 11: @@
 These two pages from the mongrel website on [http://mongrel.rubyforge.org/wiki/Apache Apache Best Practice Deployment] and [http://mongrel.rubyforge.org/docs/mongrel_cluster.html Using Mongrel Cluster] are pretty good how-tos for mongrel. But we will also take you through it here, with specific directions and Umlaut recommendations and pit-falls we ran into.
-Alternatively, based on Ross Singer's recommendation, scotdalton is using [http://code.macournoyer.com/thin/ thin] and Apache at NYU.  The setup is almost identical to mongrel and is detailed at [Umlaut Deployment with Thin and Apache]
+Alternatively, based on Ross Singer's recommendation, scotdalton is using [http://code.macournoyer.com/thin/ thin] and Apache at NYU.  The setup is almost identical to mongrel and is detailed at [[Umlaut Deployment with Thin and Apache]]
 == Quick start 'wizard' ==

@@ Line 11: / Line 11: @@
 These two pages from the mongrel website on [http://mongrel.rubyforge.org/wiki/Apache Apache Best Practice Deployment] and [http://mongrel.rubyforge.org/docs/mongrel_cluster.html Using Mongrel Cluster] are pretty good how-tos for mongrel. But we will also take you through it here, with specific directions and Umlaut recommendations and pit-falls we ran into.
-Alternatively, based on Ross Singer's recommendation, scotdalton is using [thin|http://code.macournoyer.com/thin/] and Apache at NYU.  The setup is almost identical to mongrel and is detailed at [Umlaut Deployment with Thin and Apache]
+Alternatively, based on Ross Singer's recommendation, scotdalton is using [http://code.macournoyer.com/thin/ thin] and Apache at NYU.  The setup is almost identical to mongrel and is detailed at [Umlaut Deployment with Thin and Apache]
 == Quick start 'wizard' ==

← Older revision		Revision as of 14:59, 7 April 2011
Line 10:		Line 10:

	These two pages from the mongrel website on [http://mongrel.rubyforge.org/wiki/Apache Apache Best Practice Deployment] and [http://mongrel.rubyforge.org/docs/mongrel_cluster.html Using Mongrel Cluster] are pretty good how-tos for mongrel. But we will also take you through it here, with specific directions and Umlaut recommendations and pit-falls we ran into.		These two pages from the mongrel website on [http://mongrel.rubyforge.org/wiki/Apache Apache Best Practice Deployment] and [http://mongrel.rubyforge.org/docs/mongrel_cluster.html Using Mongrel Cluster] are pretty good how-tos for mongrel. But we will also take you through it here, with specific directions and Umlaut recommendations and pit-falls we ran into.
		+
		+	Alternatively, based on Ross Singer's recommendation, scotdalton is using [thin\|http://code.macournoyer.com/thin/] and Apache at NYU. The setup is almost identical to mongrel and is detailed at [Umlaut Deployment with Thin and Apache]

	== Quick start 'wizard' ==		== Quick start 'wizard' ==

@@ Line 154: / Line 154: @@
 # ProxyPassReverse /findit balancer://umlaut_cluster/findit/
 </pre>
 === Dealing with bad query strings: More Apache Setup ===

@@ Line 5: / Line 5: @@
 Turns out there are several possible deploy environments for a Rails application. There is not necessarily one standard or best one at the moment, different people use different ones in different circumstances.
-Jonathan Rochkind at Hopkins uses mongrel, mongrel_cluster and Apache mod_proxy and mod_proxy_balancer on a unix system for his deploy environment.  He went down this road because it was what was recommended by the [http://www.pragprog.com/titles/rails2 Rails Agile Development book].  We may explore other deploy enviroments (such as 'passenger') in the future.  We would definitely not be optimistic about running Umlaut on Windows.
+Jonathan Rochkind at Hopkins uses mongrel, mongrel_cluster and Apache mod_proxy and mod_proxy_balancer on a unix system for his deploy environment.  He went down this road because it was what was recommended by the [http://www.pragprog.com/titles/rails2 Rails Agile Development book].  We may explore other deploy enviroments (such as 'passenger') in the future.  We would definitely not be optimistic about running Umlaut on Windows. *Lately mod_rails/Passenger is clearly the preferred Rails deployment in general, and jrochkind wants to find time to set it up and test it, but hasn't yet.*
 Since jrochkind is writing this documentation, he can only tell you how to do it how he did. You do need to have a verison of Apache that includes mod_proxy_balancer (> apache 2.2? ), but if you do, jrochkind is fairly happy with the solution.

@@ Line 80: / Line 80: @@
 The point of mongrel_cluster is to save configuration information for multiple mongrel instances in one configuration file, and then you can start, stop, or restart them all with one command, and without having to remember that config information each time (and possibly get it wrong or typod).
-By default, mongrel_cluster keeps that configuration file in a Rails app's config/mongrel_cluster.yml.   You could do that with Umlaut, but we like to keep your local config files in $Umlaut/config/umlaut_config instead (see [[Umlaut Local Configuration Architecture]]), so we recommend putting it in $Umlaut/config/umlaut_config. You can use the mongrel_rails command to write this config for you (see [http://mongrel.rubyforge.org/docs/mongrel_cluster.html Using Mongrel Cluster]; make sure to use the -C argument to put the config file in umlaut_config, if that's what you want), but here we'll just give you our actual mongrel_cluster.yml config, annotated. (You are certainly allowed to write it by hand).
+By default, mongrel_cluster keeps that configuration file in a Rails app's config/mongrel_cluster.yml.   You could do that with Umlaut, but we like to keep your local config files in $Umlaut/config/umlaut_config instead (see [[Umlaut Local Configuration Architecture]]), so we recommend putting it in $Umlaut/config/umlaut_config. You can use the mongrel_rails command to write this config for you (see [http://mongrel.rubyforge.org/wiki/MongrelCluster Using Mongrel Cluster]; make sure to use the -C argument to put the config file in umlaut_config, if that's what you want), but here we'll just give you our actual mongrel_cluster.yml config, annotated. (You are certainly allowed to write it by hand).
 <pre>

@@ Line 17: / Line 17: @@
 === Prerequisites ===
-* Instead 'mongrel' and 'mongrel_cluster' gems.
+* Install 'mongrel' and 'mongrel_cluster' gems.
 * Apache needs mod_proxy and mod_proxy_balancer (which means it needs to be apache >2.2 I think, and have those modules turned on).
 * You need to have access to an apache conf file to add some statements to hook your mongrel cluster up to the web.
 === To run ===

@@ Line 140: / Line 140: @@
 # Set up ProxyPass directive to reverse proxy to SFX for handling SFX journal subscription cgi posts
 # This should come before the cluster ProxyPass directive.
-ProxyPass /resolve/cgi/core/journal_subscription.cgi http://sfx.library.nyu.edu:8888/sfx_test/cgi/core/journal_subscription.cgi
+ProxyPass /resolve/cgi/core/journal_subscription.cgi http://your.sfx.host.edu:port/your_instance/cgi/core/journal_subscription.cgi
-ProxyPassReverse /resolve/cgi/core/journal_subscription.cgi http://sfx.library.nyu.edu:8888/sfx_test/cgi/core/journal_subscription.cgi
+ProxyPassReverse /resolve/cgi/core/journal_subscription.cgi http://your.sfx.host.edu:port/your_instance/cgi/core/journal_subscription.cgi
 # Now set up the ProxyPass directives to reverse proxy to that cluster