| Where should I define my inputs?
What's the difference between Inputs, Actions, and Actions Inputs? | ||
The following parameters configure the Apache settings for the front-end machines.
ADMIN_EMAIL
Provide the email address that will receive apache notifications.
Text : admin@mysite.com
This setting tells Apache whether to use the threaded "worker" or to prefork.
Use worker for Rails/TomCat/Standalone front ends.
Use prefork for PHP.
The full documentation can be found in Apache official site.
Text :
The URI for the HAProxy maintenance page. URI is based on the document root path.
Text :
This option tells Apache whether it should serve the (static) content itself. Currently it will omit dynamic PHP and TomCat content (*.php, *.action, *.jsp, *do).
$ignore
Apache will redirect requests to the associated port of OPT_TARGET_BIND_ADDRESS.
$ignore
Set the timezone of the instance. The format follows standard timezone naming conventions (UTC, PST, EST, GMT, US/Eastern, America/Los_Angeles, etc.) See TZSET for more details. Default: UTC
Text: UTC
Define the optional, main virtual host port by using this input. This is often used by the application server template.
Text: 8088
The location where you want your application to be installed. Default: /home/webapps/$application/current
$ignore
The template will automatically deploy your application with these specified values.
The location where the application can be retrieved. Provide the name of the S3 bucket where the application is stored.
Text : my_app_bucket
The name of the application tarball (.war, .tar.gz, .zip, etc) that can be retrieved from the S3 bucket.
Text : my_app.war
Since we want to create backups of our database in S3, the templates require that you include your Amazon keys.
The template will automatically generate your database.yml file with these specified values.
The prefix that will be used for creating the backup filename. These parameters tell the Master-DB where to place the backups in S3. When backups are taken, the files will be named with the prefix that you define followed by a timestamp of when they were created so that you can easily verify the most recent backup. You can define whatever prefix that you want to use. Remember, you cannot use spaces in an S3 bucket's filename.
Text : production
The name of the S3 bucket where database backups will be stored.
Text : mysite_bucket
The password that users of the database will use to access your database. This value is used to set up the connection between the database and the application. You must use the same value that was defined in the Create a Redundant MySQL Setup tutorial.
Cred :
The username that users of the database will use to access your database. This value is used to set up the connection between the database and the application.You must use the same value that was defined in the Create a Redundant MySQL Setup tutorial.
Cred :
The password that will be used by a slave database in order to replicate data from the master database.
Cred :
The username that will be used by a slave database in order to replicate data from the master database.
Cred :
The name of the database that is used by the application, i.e. the schema of your database.
Text : app_schema_name
This parameter defines which MySQL config that you want to use. Set the it to dedicated-small, dedicated-large, or dedicated-xlarge depending on whether you are running a small, large or extra large instance respectively. The default is small. If you are not sure, you can double-check under the Info tab of the server.
Text : dedicated-small
Describes how the server will be used. The server is either a dedicated MySQL server or a shared MySQL server with other processes on the operating system. Make your selection from the pulldown menu.
Text : dedicated
Defines whether this instance should automatically initialize a Slave-DB at boot time. To make sure that the Slave-DB automatically initializes itself when it boots, set the INIT_SLAVE_AT_BOOT input parameter to True (default). Set to False if you do not want it to initialize at boot time. The only case where you would want to do this is if you don't already have a Master-DB instance running and you want to launch a Slave-DB.
Text : true
The DNS ID (Record ID) of the Master-DB. This value is generated when you create a subdomain using DNSMadeEasy. It's used to update the DNS record to point to the new Master IP address. ex: db-master.mysite.com
Text :
The DNS name of the Master-DB.
Text : master1.mysite.com
Defines the number of revolving backups for the Slave-DB to take. If you leave this parameter undefined, the default value (6) will be used. i.e. Only the last 6 backups will be saved to S3. The oldest backup is overwritten in order to write the new backup. By default, snapshots (backups) of a slave database are taken every 10 minutes. Default: 6
$ignore
Set this value to "no" or "false" will disable the compression of these backups which will take some of the CPU load off the slave. Setting it to any other value will enable compression which will decrease the storage size on S3. NOTE: You will only have to go to S3 in the event that you have no database server running or all running databases are corrupted.
$ignore
Defines the number of maximum MySQL connections that you want to allow to the master database at any given time. Once your deployment is operational, you might want to define a limit. Default: 500.
$ignore
The maximum amount of space (GB) to be partitioned to XFS format by LVM. The size in gigabytes that you want /mnt to be formatted. This is a tradeoff between disk capacity and boot time since larger sizes will take longer to format. Set to "max" to get the full capacity. Default: 60GB (small), 300GB (large, xlarge)
Text : Max
In order to handle the possibility of a failure, we will need to use a DNS record to refer to the Master-DB and Slave-DB instances. Therefore, the server will need to access your DNSMadeEasy username and password.
This parameter defines whether you want to register the public or private IP address.
Text : public
The following parameters configure HAProxy.
Define the group name or listener of a pool of application servers where you want HAProxy to place the new app server. When an application server connects to HAProxy, the application server tells HAProxy in which pool it should be placed.
Text : www
A unique name of the application server that is connected to HAProxy. HAProxy will use this name to identify each connected application server. The name must be unique.
Env: EC2 _INSTANCE_ID
The IP address that you want HAProxy to listen on. Normally, it is set to localhost (127.0.0.1). Default: 127.0.0.1
Text : 127.0.0.1
The port number that you want HAProxy to listen on. Default: 85 Each group must have a different port (or it can be the IP address (85).
Text : 85
The hostname where HAProxy is installed, so application servers will know where they should be connected. This value should be the same as the WEB_SITE_DNS value.
Text : www.mysite.com
The basic HAProxy configuration template that should be used to configure HAProxy. RightScale offers predefined haproxy_http and haproxy_tcp templates. Default: haproxy_http
Text : haproxy_http
The maximum number of connections per server. HAProxy cannot send more requests to a server if it has reached its maximum number of connections.
Text : 255
The URI for the HAProxy status page (current session, queued session, response error, health check error, server status, etc. HAProxy will display a status page for each HAProxy group.
Text : /haproxy-status
This option tells whether HAProxy should do session stickiness.
Text : true
The configuration script that you want to run in order to determine the health status of the mongrels. ex: lib/mongrel_health_check_handler.rb
Text :
Set to "true" to enable the native library for Apache Portable Runtime (APR).
Text : true
Set to "true" to enable Apache mod_jk for TomCat communication. (TomCat FrontEnd Server)
Set to "false" to disable Apache mod_jk for TomCat communication. (PHP FrontEnd Server)
Text: