Table of Contents
Current Revision: 10
MultiCloud Marketplace: https://www.rightscale.com/library/server_templates/Rails-Front-End-11H1/18226
The following MultiCloud Images (MCIs) are used by the ServerTemplate. The MCIs determine which operating systems and clouds are supported.
The email address that Apache uses to send administrative mail (set in /etc/httpd/conf/httpd.conf). By setting it to firstname.lastname@example.org emails are saved on the server. You can use your own email address, but your spam filters might block them because reverse DNS lookup will show a mismatch between EC2 and your domain.
Can be set to "worker" or "prefork" and defines the setting in httpd.conf. Use "worker" for Rails/Tomcat/Standalone frontends and "prefork" for PHP.
Sets the directory for your application's web files (/home/webapps/APPLICATION/current/). If you have multiple applications, you can run the code checkout script multiple times, each with a different value for APPLICATION, so each application will be stored in a unique directory. This must be a valid directory name. Do not use symbols in the name.
Sets the number of desired mongrel processes on the Rails server. Default: 6. If you use a larger number, make sure that it's low enough that no swapping occurs.
This input is specific to Rails applications. It's the port number of the first mongrel in the cluster. Ex: If APP_SERVER_PROCESSES = 8 and APP_SERVER_START_PORT = 8000, then the open ports will be 8000-8007.
If the MySQL administrator set up a restricted MySQL account for application servers to access the database, then specify the password of that account for this input. If there is not a restricted MySQL account then use the same value that's used for DBADMIN_PASSWORD. The application server will then have unrestricted access to the database.
If the MySQL administrator set up a restricted MySQL account for application servers to access the database, then specify the username of that account for this input. If there is not a restricted MySQL account then use the same value that's used for DBADMIN_USER. The application server will then have unrestricted access to the database.
The fully qualified domain name of the database server. (Ex: master.mydatabase.com) Application servers are designed to connect to the Master-DB by pointing to its DNS Hostname. RightScale's scripts are designed to update the Master-DB's A Record with its assigned private IP address so that application servers will communicate with the Master-DB over the private (not public) IP address.
Enter the name of the MySQL database schema to which applications will connect. The database schema was created when the initial database was first set up. This input will be used to set the application server's database config file so that applications can connect to the correct schema within the database. This input is also used for MySQL dump backups in order to determine which schema is getting backed up. Ex: mydbschema
The URI of the health check page, which is used by HAProxy for checking whether the site is up or not. You must create your own health check page, which returns HTTP 200 OK. The contents of the page are not relevant but its name should be unique (preferably a random number). The same page will be used by the load balancers to determine which application servers are "up" and capable of handling requests. For example, if you use '/hlthchk378923.html' (Note: be sure to include the slash before the filename), the health check page would be 'http://www.mydomain.com:80/hlthchk378923.html' and its content could be as simple as "OK."
Sets the name of the HAProxy load balance pool on frontends in /etc/haproxy/haproxy.cfg. Application severs will join this load balance pool by using this name. Ex: www
Sets the name of the backend application server in the (/etc/haproxy/haproxy.cfg) location. This value needs to be unique. Therefore, it is best to use the EC2_INSTANCE_ID ENV variable. Ex: Select "EC2_INSTANCE_ID" from the ENV input dropdown. Do not enter this value manually.
The IP address that HAProxy will be listening on. Normally, it should be set to localhost. Ex: 127.0.0.1
The port number that HAProxy will be listening on. Normally, it's set to 85. If you have multiple load balance pools, each pool must be assigned to a different port. Ex: 85
The fully qualified hostname of all the servers that have HAProxy installed on them for load balancing purposes. For example, if www.domain.com has two dedicated load balancers with HAProxy installed on them, you would enter www.domain.com as the LB_HOSTNAME. It is necessary that these hosts be registered with DNS with matching A Records so that the application servers will be able to connect to and disconnect from all the HAProxy servers and update their configuration files. Ex: www.domain.com
The name of the base HAProxy configuration file that will be used. This file will be modified according to the defined inputs. The current values are: haproxy_fullssl, haproxy_http, and haproxy_tcp. Ex: haproxy_http
A space-separated list of additional processes to monitor in the RightScale Dashboard. Ex: sshd crond
A space-separated list of pairs used to match the name(s) of additional processes to monitor in the RightScale Dashboard. Pair arguments are passed in using the syntax 'name/regex'. Ex: ssh/ssh* cron/cron*
The time interval (in seconds) that collectd uses to poll HAProxy for statistics. Default: 60
The URI for the HAProxy statistic report page, which lists the current session, queued session, response error, health check error, server status, etc., for each HAProxy group. Ex: /haproxy-status
Optional html page, relative to document root (i.e., "".../current/public"") to use as the contents of the maintenance message. If left blank, a basic Server in maintenance html message will be provided.
Optional path for a maintenance page, relative to document root (i.e., "".../current/public""). The file must exist in the subtree of the vhost, which will be served by the web server if it's present. If ignored, it will default to '/system/maintenance.html'.
Optional path to the configuration script on the local filesystem that will be run at mongrel startup. Ex: /path/to/config/script
Optional override for the log dir of mongrels (default: "rails_home"/log) Ex: /desired/path/2/log/files
The svn mode you would like to get your files in. Export is more secure, while checkout allows you to make changes and update them. Ex: [checkout,export]
The SVN password that is used to checkout the application code from SVN repository.
The SVN username that is used to checkout the application code from SVN repository.
The private SSH Key of another instance that gets installed on this instance. It allows this instance to SSH into another instance to update the configuration files. Select input type "key" from the dropdown and then select an SSH key that is installed on the other instance. You must select an SSH Key where its private material is available.
A value of 'env:RS_INSTANCE_UUID' is required for proper RightScale monitoring and logging.
The URL of your SVN repository where your application code will be checked out from. Ex: http://mysvn.net/app/
The hostname of the syslog server where log files will be sent. This input should be set to 'env:RS_SYSLOG' so that you can view your log files in the Dashboard.
Sets the system time to the timezone of the specified input, which must be a valid zoneinfo/tz database entry. If the input is 'unset' the timezone will use the 'localtime' that's defined in your RightScale account under Settings -> User -> Preferences tab. You can find a list of valid examples from the timezone pulldown bar in the Preferences tab. Ex: US/Pacific, US/Eastern
|Revision||Date Published||Description of Changes||Known Issues|
|10||Mar 22, 2011||Initial Release -- 11H1|
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.