17 |
18 | ## Technology stack
19 |
20 | For specific components supported in each of these functional areas, see our current
21 | [[Engine Yard Technology Stack|cloud-tech-stack]].
22 |
23 |
--------------------------------------------------------------------------------
/pages/cloud-support.md:
--------------------------------------------------------------------------------
1 | # Engine Yard Cloud Support
2 |
3 | Engine Yard support plans offer access to the leading Ruby on Rails support organization
4 | with years of experience supporting applications of all sizes. Engine Yard includes a base
5 | level of support with every Engine Yard account, enabling all Engine Yard customers to ask
6 | questions through our [[online support|http://support.cloud.engineyard.com]].
7 |
8 | Have a question about how to use the Engine Yard product? How to choose the best Ruby
9 | runtime? Our team is ready and waiting to help you out. Need more help? Engine Yard offers a
10 | range of support options to help you deploy and maintain your applications in a production
11 | environment.
12 |
13 | ## Base Support
14 | Base Support customers have access to our [[online support|http://support.cloud.engineyard.com]]
15 | system to request deployment help, provide feedback or ask questions. For customers with Base Support,
16 | Engine Yard will respond to all tickets as quickly as possible. Base Support customers should anticipate
17 | a response within no more than **3 business days** following your inquiry.
18 |
19 | **[[Learn more|http://www.engineyard.com/support-plans]] about our support options.**
20 |
21 | ## Standard Support
22 | Customers that upgrade to Standard Support get unlimited access to the Engine Yard support
23 | team during business hours including assistance with installation, configuration and troubleshooting
24 | of supported components.
25 |
26 | **[[Learn more|http://www.engineyard.com/support-plans]] about Standard Support.**
27 |
28 | ## Premium Support
29 | Premium Support includes all the benefits of Standard Support and with the addition of unlimited
30 | access to the Engine Yard support team during business hours, proactive monitoring of alerts
31 | generated by your applications, and 24x7 support response for critical issues causing application
32 | unavailability or site down-time.
33 |
34 | **[[Learn more|http://www.engineyard.com/support-plans]] about Premium Support.**
--------------------------------------------------------------------------------
/pages/cloud-updates-march-2012.md:
--------------------------------------------------------------------------------
1 | # Engine Yard Cloud updates March 2012
2 |
3 | The updates described are either important (where you need to take action) or of interest (you might want to know about these changes but you don't need to do anything).
4 |
5 | Minor: Engine Yard stack upgrade
6 | 7 | March 1st, 2012 8 | 9 | The following changes have been made to the Engine Yard stack: 10 | 11 | * For Rails 3 applications that use MySQL, database-adapter detection has been improved to prevent deployment errors related to the database gem. 12 | * Upgraded JRuby to 1.6.7 from 1.6.6. 13 | * Fixed a problem related to the PostgreSQL server restarting after configuration changes; the PostgreSQL server now *reloads* after configuration changes. 14 | 15 | These changes are applied when you upgrade your environment. 16 | 17 | 18 | 19 | [1]: #update1 "update1" 20 | [2]: #update2 "update2" 21 | [3]: #update3 "update3" 22 | [4]: #update4 "update4" 23 | [5]: #update5 "update5" 24 | [6]: #update6 "update6" 25 | [7]: #update7 "update7" 26 | [8]: #update8 "update8" 27 | [9]: #update9 "update9" 28 | [10]: #update10 "update10" 29 | [11]: #update11 "update11" 30 | [12]: #update12 "update12" 31 | [13]: #update13 "update13" 32 | [14]: #update14 "update14" 33 | [15]: #update15 "update15" 34 | [16]: #update16 "update16" 35 | [17]: #update17 "update17" 36 | [18]: #update18 "update18" -------------------------------------------------------------------------------- /pages/collaboration.md: -------------------------------------------------------------------------------- 1 | # Collaboration 2 | 3 |  4 | 5 | Have you always wanted to be able to share your account (or one of your accounts) with other developers? Or as a developer, you wish you only needed one login account to access different projects? 6 | 7 | Now you can, with Collaboration for Engine Yard Cloud. 8 | 9 | Steps to getting started: 10 | 11 | - [[Getting Started with Collaboration|account-collaboration]] 12 | 13 | Only the account owner needs to request the Collaboration feature. They can share their account with other users who haven't requested access to the Collaboration feature. -------------------------------------------------------------------------------- /pages/create-your-bundler-gemfile.md: -------------------------------------------------------------------------------- 1 | # Create your Bundler Gemfile 2 | 3 | Bundler is an amazing tool for handling the gems that you use with your application. The screencast below gets you up and running with Bundler. Make sure to install Bundler before viewing the screencast with `gem install bundler`. For more information, see the [[Bundler website|http://gembundler.com]]. 4 | 5 | 6 | 7 | -------------------------------------------------------------------------------- /pages/create-your-rails-application.md: -------------------------------------------------------------------------------- 1 | # Create your Rails Application 2 | 3 | To get started with creating your first Rails 3 application, follow the directions in the screencast to create a simple blog with Rails 3. 4 | 5 | 6 | 7 | 8 | 9 | If you want further resources for learning Ruby on Rails read the [[Resources for Getting Started with Ruby on Rails|http://www.engineyard.com/blog/2010/resources-for-getting-started-with-ruby-on-rails/]] blog post. 10 | 11 | -------------------------------------------------------------------------------- /pages/customize-unicorn.md: -------------------------------------------------------------------------------- 1 | # Customize Unicorn 2 | 3 | Unicorn does not employ keep files for its configuration file. This page describes how to customize Unicorn without a keep file. 4 | 5 | The process is: 6 | 7 | 1. [Create an alternate Unicorn configuration file.][1] 8 | 2. [Start Unicorn with Bundler instead of running the system Unicorn.][2] 9 | 10 |To create the customized Unicorn configuration file and restart Unicorn
11 | 12 | 1. Add this line to the file `/data/_myapp_/shared/config/env.custom` (where _myapp_ is the name of your application): 13 | 14 | UNICORN_CONF="/data/_myapp_/shared/config/custom_unicorn.rb" 15 | 16 | This specifies an alternate configuration file for Unicorn. 17 | 18 | 2. Copy `/data/_myapp_/shared/config/unicorn.rb` to `/data/_myapp_/shared/config/custom_unicorn.rb`. 19 | 20 | 3. Edit the `/data/_myapp_/shared/config/custom_unicorn.rb` with the customizations that you want. 21 | 22 | 4. Restart Unicorn so that the customizations take effect: 23 | 24 | /engineyard/bin/app_myapp reload 25 | 26 | 27 |To start Unicorn in Bundler
28 | 29 | 1. Add the Unicorn gem to your Gemfile: 30 | 31 | gem 'unicorn' 32 | 33 | 3. Run these commands to update your Gemfile.lock: 34 | 35 | bundle install 36 | 37 | git commit -a -m "Gemfile updated for Unicorn" 38 | git push origin 39 | 40 | [1]: #topic1 "topic1" 41 | [2]: #topic2 "topic2" 42 | 43 | This is what the env.custom file looks like: 44 | cat env.custom 45 | #!/bin/bash 46 | # 47 | # Custom environment variables for Trinidad should go here. 48 | # 49 | # Note: there are several functions at the top of env that you can use 50 | # here, including: 51 | # 52 | # - set_jvm_memory MEM: set JVM max memory 53 | # set_memory "2G" 54 | # - add_java_option OPT: add to the JAVA_OPTS environment variable 55 | # add_java_option -Djava.io.tmpdir=/var/tmp 56 | # 57 | 58 | -------------------------------------------------------------------------------- /pages/data-feedback.md: -------------------------------------------------------------------------------- 1 | #Provide Feedback to the Engine Yard Data Team 2 | 3 | 4 | 5 | -------------------------------------------------------------------------------- /pages/database-pg-configure.md: -------------------------------------------------------------------------------- 1 | #Place holder for a topic about configuring a PostgreSQL database 2 | 3 | Keep topics parallel with configuring the -------------------------------------------------------------------------------- /pages/deploy-unix-package.md: -------------------------------------------------------------------------------- 1 | # Add unix packages to your application 2 | 3 | You can add additional software packages to your application within Engine Yard Cloud. Packages are added at the account-level. After a package is applied to specific environment, it cannot be removed from that environment. (Although, after a package is dissociated from an application, new environments for that application do not have the package.) 4 | 5 | ##To configure additional software packages for your application within Engine Yard Cloud. 6 | 7 | 1. In the Dashboard, click the name of the application you want to modify. 8 | 2. Click the Unix Packages icon. 9 | 3. Search for your package. 10 | For example `rabbitmq` for RabbitMQ. 11 | Results are returned under the heading "Available Unix Packages". 12 | 4. Click Add ->. 13 | The package is added to the Selected list. 14 | 5. To install the package on an existing environment: 15 | a. Click Go to dashboard. 16 | b. Click the environment name. 17 | c. Click Apply. 18 | 6. To install the package on new environment: 19 | a. Click Go to dashboard. 20 | b. Create and boot a new environment for the application. 21 | 22 | ## To remove a software package 23 | 24 | 1. In the Dashboard, click the name of the application to remove the software package from. 25 | 2. Click the Unix Packages icon. 26 | 3. Click x Remove for the package. 27 | This removes the package from the UI but does not remove the package from any currently running environments. 28 | -------------------------------------------------------------------------------- /pages/deployment-maintenance-pages.md: -------------------------------------------------------------------------------- 1 | # Application maintenance pages 2 | 3 | Engine Yard provides a default maintenance page, but you are encouraged 4 | to customize them to suit your application. Further, you can even change 5 | your maintenance page on every deploy to give deploy-specific feedback 6 | (e.g. "we are doing a database upgrade, please sit tight"). 7 | 8 | When a rollback is performed, the maintenance page used is the one 9 | contained in the latest deploy. This prevents showing users a message from 10 | an old deploy. 11 | 12 | ## Priority 13 | When a maintenance page is requested to be displayed, Engine Yard Cloud looks for 14 | HTML files and displays them in the following priority: 15 | 16 | 1. `public/maintenance.html.custom` 17 | 2. `public/maintenance.html.tmp` 18 | 3. `public/maintenance.html` 19 | 4. `public/system/maintenance.html.default` 20 | 21 | ## Commands 22 | To enable or disable your maintenance pages, use the [[Engine Yard CLI|ey_cli_user_guide]] 23 | and run the following commands. 24 | 25 | - Enable your maintenance page: 26 | ey web enable 27 | - Disable your maintenance page: 28 | ey web disable 29 | -------------------------------------------------------------------------------- /pages/diagnose-errors-on-engine-yard-cloud.md: -------------------------------------------------------------------------------- 1 | # Diagnosing Errors on Engine Yard Cloud 2 | 3 | This document describes some common error conditions you might see while setting up your Engine Yard Cloud environment. 4 | 5 | ## Common Error Conditions 6 | 7 | ### 1. Insufficient Capacity Error 8 | 9 | This message is displayed when EC2 is unable to provision servers for your environment due to transient overcapacity in your selected availability zone. To get around this, we recommend waiting a few minutes and retrying. If the error persists, you can try a different instance size or availability zone. You can choose a new one from the Edit Environment page. 10 | 11 | ### 2. Gem Not Found Error 12 | 13 | While deploying an application, you might get an error condition because Gems required for your application are not found on the instance. You can add, remove and edit Gems for each application by clicking on the "Add Rubygems" link in the "Applications" tab on your environment. 14 | 15 | ### 3. Bundler Error 16 | 17 | The easiest way to use Bundler is to include the Bundler gem (with the appropriate version) in your list of Gem dependencies. Then include the appropriate Bundler command (e.g. "bundle install") in your "Migrate with" command text-box. You can edit this when by clicking the "Deploy" link for your application, and this command will then run as as part of the post-deploy process. 18 | 19 | ### 4. Deploy Failed Error 20 | 21 | If your deploy fails for other reasons, you can check the deploy logs for information to help debug the problem. You can locate the "Deploy Logs" tab on your environment in the Dashboard. You can scroll down to the bottom of the logs section to see output from the process that caused the deploy failure. If you have multiple instances in the environment, make sure to check the logs of the instance that failed. 22 | 23 | -------------------------------------------------------------------------------- /pages/environment-cluster.md: -------------------------------------------------------------------------------- 1 | # Clustered environments 2 | 3 | ## Cluster architecture 4 | 5 |  6 | 7 | 8 |Add an instance to a cluster
9 | 10 | You can grow your cluster by adding additional application, database, or utility instances as needed. 11 | 12 | ###To add an instance to a cluster 13 | 1. On the Environment page, click Add. 14 | 2. Select one of the following: 15 | * Add Application Server 16 | * Add Database Slave 17 | * Add Utility Server 18 | 3. Click Add to Cluster. 19 | 20 |More information
21 | 22 || For more information about... | See... | 25 |
|---|---|
| Adding a database slave | [[Add a database slave to an existing environment|database-environments#topic3]] | 28 |
Environment options
16 | 17 | * ### Environment Name 18 | Use underscores to separate words instead of spaces. Common environment names are: myapp_production, myapp_staging, myapp_testing, myapp_qa, myapp_ci, etc. 19 | 20 | * ### Framework Environment 21 | Select an option to set the RAILS_ENV, MERB_ENV or RACK_ENV for applications in this environment. 22 | 23 | * ### Application Server Stack 24 | Select an application server to serve your Rails or Ruby application in this environment. 25 | 26 | If you need to run more than one application on an environment, choose Passenger. 27 | 28 | If you will be running only one application on an environment (this is more common practice), then choose Unicorn. Engine Yard has found Unicorn to be reliable, easier to monitor, and to have less downtime during deployment. 29 | 30 | * ### Runtime 31 | Select a runtime to run your applications in this environment. 32 | 33 | * ### Domain Name 34 | Set your domain name for this environment. This is the domain you intend to use for this application. If you are only adding one application to this environment, leave the Domain field blank (not set). 35 | 36 | * ### Region 37 | Select an AWS region for your environment. The default option is usually fine. 38 | 39 | * ### SSH Keys 40 | Select the ssh keys you want to have installed on instances in this environment. 41 | 42 | * ### Backups 43 | Select the frequency and amount of backups and snapshots you want to keep for this environment. 44 | -------------------------------------------------------------------------------- /pages/environment-delete.md: -------------------------------------------------------------------------------- 1 | # Delete an environment 2 | 3 | **Important!** Before deleting an environment, make sure that there is nothing on that environment that you need to keep. Deleting is permanent. 4 | 5 | ##To delete an environment 6 | 7 | 1. In the Dashboard, click the environment name. 8 | 2. If the environment is running, click Stop. 9 | 3. Click Delete. -------------------------------------------------------------------------------- /pages/environment-intro.md: -------------------------------------------------------------------------------- 1 | # Environments on Engine Yard Cloud 2 | 3 | **Environment** is an overloaded term. Here at Engine Yard when we refer to your 4 | 'environment' we are talking about the cluster of instances that collectively run 5 | an application or set of applications. 6 | 7 | An environment includes Application Instance(s), Database Instance(s), and possibly 8 | one or more Utility Instances. For more information about instances types, see [[Compute instances on Engine Yard Cloud|instance-types]]. 9 | 10 | ## Topics 11 | 12 | * ### [[Create an environment|environment-create]] 13 | Learn how to create a new environment to deploy your instance(s). 14 | 15 | * ### [[Upgrade an environment|environment-upgrade]] 16 | Learn how to upgrade an environment to the latest version of the Engine Yard Cloud stack. 17 | 18 | * ### [[Clone an environment|environment-clone]] 19 | Learn how to make a copy of an existing environment. 20 | 21 | * ### [[Rebuild an environment|environment-rebuild]] 22 | Learn how to rebuild an environment with minimal downtime. 23 | 24 | * ### [[Delete an environment|environment-delete]] 25 | Learn how to delete an environment on Engine Yard Cloud. 26 | 27 | * ### [[Clustered Environments|environment-cluster]] 28 | Learn about our clustered architecture and how to add an instance to a cluster. 29 | 30 | * ### [[Change an instance size|change-an-instance-size]] 31 | Learn how to change the size of an instance in an environment. 32 | 33 | * ### [[Multi-Region support|using-multi-region-with-engine-yard-cloud]] 34 | Learn how to deploy your application in different geographic regions. 35 | 36 | * ### [[High availability for clustered environments|environment-high-availability]] 37 | Learn how to use high availability to create redundancy in a clustered environment. This protects your environment if there are problems in one zone of a region. 38 | 39 | * ### [[Using snapshots|using-snapshots]] 40 | Learn how to use snapshots in your environment. 41 | -------------------------------------------------------------------------------- /pages/faq_home.md: -------------------------------------------------------------------------------- 1 | # Engine Yard FAQs 2 | 3 | * [[Engine Yard Cloud FAQs|cloud_faq]] 4 | * [[Deployment FAQs|deployment-faqs]] 5 | * [[Trial FAQs|http://www.engineyard.com/products/cloud/trial-faq]] 6 | -------------------------------------------------------------------------------- /pages/generating_ssh_keys.md: -------------------------------------------------------------------------------- 1 | # Using SSH on Engine Yard Cloud 2 | 3 | If you need to access an instance in your applications environment, you can 4 | login via [[SSH|http://en.wikipedia.org/wiki/Secure_Shell]]. You will need 5 | to setup SSH keys on your local development machine, add the keys to your 6 | Engine Yard account, and install the keys in any of your environments. The following 7 | topics help you with each of these processes. 8 | 9 | ## Topics 10 | 11 | * ### [[Setup local SSH keys|ssh-setup]] 12 | Learn how to generate an ssh keypair on your local machine. 13 | 14 | * ### [[Add a key to Engine Yard Cloud|ssh-add-to-cloud]] 15 | Learn how to add your SSH public key to your Engine Yard account. 16 | 17 | * ### [[Install keys to your application environments|ssh-install]] 18 | Learn how to install your keys to instances in your applications environment. 19 | 20 | * ### [[Connect to an instance via SSH|ssh-connect]] 21 | Learn how to connect to your instance via SSH. 22 | 23 | * ### [[Troubleshooting|ssh-troubleshooting]] 24 | Tips to help you troubleshoot issues related to SSH on Engine Yard Cloud. 25 | -------------------------------------------------------------------------------- /pages/getting-started-intro.md: -------------------------------------------------------------------------------- 1 | #Get started with Engine Yard Cloud 2 | 3 | ##Topics 4 | 5 | 1. ### [[Video tutorial: set up a trial account and deploy a sample application|getting-started-video-tutorial]] 6 | Watch a screencast that shows how to set up an Engine Yard account and deploy an application. 7 | 8 | 2. ### [[Tutorial: set up a trial account and deploy a sample application|getting-started-deploy-todo]] 9 | Learn how to sign up for a free Engine Yard account and deploy a Rails 3 application on it. 10 | 11 | 3. ### [[Sign up for an Engine Yard account|sign-up-for-engine-yard-cloud]] 12 | Learn how to sign up for a full Engine Yard account. 13 | 14 | 4. ### [[Get started|getting_started_home]] 15 | Learn how to create an Engine Yard application in your new account and to boot an environment to run it in. 16 | 17 | 5. ### [[Setup your local environment|setup-environment]] 18 | Learn about setting up your local environment for Ruby on Rails development on Windows, Mac OS X, or Linux. 19 | 20 | 6. ### [[Host your code on GitHub|host-your-code-on-github]] 21 | Learn a few GitHub basics. 22 | 23 | 7. ### [[Introduction to basic git commands|basic-git-commands]] 24 | Learn a few key git commands. 25 | 26 | 8. ### [[Create your Bundler Gemfile|create-your-bundler-gemfile]] 27 | Watch a screencast about using Bundler to manage Ruby gems. 28 | 29 | 9. ### [[Create your Rails application|create-your-rails-application]] 30 | Watch a screencast showing how to deploy a Rails 3 application. 31 | 32 | 10. ### [[Tutorial: How to deploy a sample Rails 2 application on a trial account|tutorial_deploy_fat_free_crm]] 33 | Learn how to deploy a Rails 2 application, fork a GitHub repository, add Ruby gems, create SSH keys, and troubleshoot deployment. 34 | 35 | -------------------------------------------------------------------------------- /pages/getting-started-video-tutorial.md: -------------------------------------------------------------------------------- 1 | # Video tutorial: Set up an account and deploy an application 2 | 3 | This video shows how to set up a trial Engine Yard account and deploy a Rails 3 application on it -- all in 3 minutes. 4 | 5 | 6 | 7 | 8 | 9 | For a step-by-step tutorial on how to set up an account and deploy a Rails 3 application, see [[Tutorial: How to deploy a sample application on a trial account|getting-started-deploy-todo]]. 10 | -------------------------------------------------------------------------------- /pages/haproxy-stats.md: -------------------------------------------------------------------------------- 1 | # View your HAProxy stats 2 | 3 | In order to gain a better picture of the current availability of your application, we generate a password so you can securely review your HAProxy stats for your application cluster. 4 | 5 | **Note:** You must be running at least two application instances to view HAProxy stats. 6 | 7 | Your password is generated for each environment you've got running. 8 | 9 | ## To display HAProxy stats 10 | 11 | 1. Navigate to the Environment page. 12 | 13 | 2. Click the HAProxy Stats link. 14 | The link only appears if you are running multiple application instances in this environment. 15 | A page of information recorded by HAProxy on the current connections appears. 16 | 17 |  18 | 19 | 3. Refresh the page to get the latest stats. 20 | 21 | ## Further reading 22 | 23 | Go to [[HAProxy's documentation|http://haproxy.1wt.eu/#docs]] for more information how to interpret the stats. 24 | 25 | 26 | -------------------------------------------------------------------------------- /pages/host-your-code-on-github.md: -------------------------------------------------------------------------------- 1 | # Host your code on GitHub 2 | 3 | After your local machine is setup and you have created your first Ruby on Rails application, place your code in a git repository. You have options on where to host your code, but the simplest is hosting it on [GitHub](http://www.github.com). This page describes how to host your code on GitHub. 4 | 5 | ##To host your code on GitHub 6 | 7 | 1. Create a [[GitHub|https://github.com/]] account. 8 | 2. After logging in, create a new repository. (Click New repository.) 9 | 3. Give your project a name and description and click Create Repository. 10 | 4. Follow the GitHub instructions to connect your local git repository with your GitHub repository. 11 | **Note:** If your code is in a Subversion (SVN) repository, see [[GitHub:Help Import from Subversion|http://help.github.com/import-from-subversion/]]. 12 | 13 |  14 | 15 | After you have completed the GitHub, your application code is stored remotely on GitHub. Whenever you make any local changes in your git repository and want to have it pushed to your remote GitHub repository, type `git push` while inside of your local repository; git will push your newly committed code to GitHub. 16 | 17 | **Important!** Make sure to put your Rails root directory at the root level of your git repository. Don't put it in a subdirectory. (The Rails root directory is the one that contains the app, config, and public directories.) 18 | 19 |More information
20 | 21 || For more information about... | See... | 24 |
|---|---|
| Setting up your local machine | [[Set up your local environment|setup-environment]]. | 27 |
| hosting your code on GitHub | this [[Spanish translation of the Host your Code on GitHub tutorial|http://www.decisionesinteligentes.com/guides/github-como-repositorio]], courtesy of Mario Alberto Chavez Cardenas of [[Decisiones Inteligentes|http://www.decisionesinteligentes.com/]] and [[Tiajuana.rb|http://tijuanarb.org/]]. | 30 |
8 | Note: You will not be able to recover your IP address after it 9 | has been deleted. 10 |
11 | 12 | ## Delete an address 13 | 14 | * Login to your Engine Yard account. 15 | * Click the IP Addresses menu item. 16 | * Locate the ip address(es) you want to delete. 17 | * Click the Delete link. 18 | * Click OK when asked to confirm. -------------------------------------------------------------------------------- /pages/ips-intro.md: -------------------------------------------------------------------------------- 1 | # IP addresses on Engine Yard Cloud 2 | 3 | Engine Yard Cloud uses Amazon AWS [[Elastic IP Addresses|http://aws.amazon.com/ec2/]]. 4 | Each Engine Yard account is initially allotted five IP addresses to associate with your 5 | environments. 6 | 7 | 8 | ## Topics 9 | 10 | * ### [[Manage your IP addresses|ips-manage]] 11 | Learn how to add, attach, and detach IP addresses in your environments, and to get more IP addresses for your account. 12 | 13 | * ### [[Delete your IP addresses|ips-delete]] 14 | Learn how to delete IP addresses from your Engine Yard account. 15 | 16 | * ### [[Configure your domain and DNS for Engine Yard Cloud|ips-setup-dns]] 17 | Learn how to configure DNS and domain settings for your environments. -------------------------------------------------------------------------------- /pages/ips-setup-dns.md: -------------------------------------------------------------------------------- 1 | # Set up your domain and DNS for Engine Yard Cloud 2 | 3 | Anyone can access your web application on Engine Yard Cloud by the generic http://ec2-xxx-xx-xxx-xxx.compute-1.amazonaws.com/. However, most users would rather have www.myapp.com to be the point of access. How can we accomplish that with Engine Yard Cloud? 4 | 5 | Domain Name System (DNS) services are not offered on Engine Yard Cloud. If you are currently using Engine Yard name servers, you need to register with a DNS service provider and update your registrar to use that provider's name servers. Check with your registrar; they may also offer control of your DNS zone records. 6 | 7 | ## Setup Engine Yard Cloud to work with a DNS provider 8 | 9 | This procedure uses the specific example of [[DNSimple|http://www.dnsimple.com]] as the service provider. Other service providers require similar steps. 10 | 11 | ### Steps for setup: 12 | 13 | 1. Create an account with DNSimple if you haven't already. 14 | 15 | 2. Log into DNSimple. 16 | 17 | 3. Click Domains. 18 |  19 | 20 | 4. Click ADD A DOMAIN. 21 | 22 | 5. Add your domain if you have one already, if not, you can create one. 23 | The status changes to Active after your domain has been added. 24 |  25 | 26 | 6. Click MANAGE. 27 | 28 | 6. Click ADVANCED EDITOR. 29 |  30 | 31 | 7. Click ADD A RECORD. 32 |  33 | 34 | 8. Go to cloud.engineyard.com and log in. 35 | 36 | 9. Under Server Tools, click IP Addresses. 37 | 38 | 39 | 10. Locate the IP address of the environment of the application that you want the domain name to point to. 40 |  41 | 42 | 11. Insert the IP address from step 11 into Address* field, and click ADD RECORD. 43 |  44 | 45 | 12. Confirm that the record was added correctly. 46 |  47 | 48 | 13. Verify your DNS settings work by accessing your page via your domain name. 49 |  50 | 51 | 52 | 53 | -------------------------------------------------------------------------------- /pages/issue-delete-application.md: -------------------------------------------------------------------------------- 1 | # Stopping an application running on a multi-application environment 2 | 3 | If your application is running in a multi-application environment, it continues to run *even* after you detach the application from the environment and delete the application. 4 | 5 | Follow this procedure to stop the application without bringing down the environment and stopping the other application(s) running on that environment. 6 | 7 | ##To stop an application running on a multi-application environment: 8 | 9 | 1. Detach the application from the environment. (On the Dashboard, click the environment, and then click "Detach app_name from this environment" at the bottom of the page.) 10 | 11 | 2. Delete the application. (On the Dashboard, click the application name, and then click the x icon.) 12 | 13 | 3. SSH into the application master instance. 14 | 15 | 4. Type to delete nginx files and directories related to that application: 16 | 17 | rm -rf /etc/nginx/servers/myapp* 18 | 19 | where `myapp` is the name of your application. The asterisk is necessary to remove files such as myapp.conf and myapp.ssl.conf. If your application uses keep files, remove them too. 20 | 21 | 22 | 5. (Optional) Type to sanity check the remaining configuration: 23 | 24 | sudo /usr/sbin/nginx -t 25 | 26 | 6. Type to reload nginx configurations: 27 | 28 | sudo /etc/init.d/nginx reload 29 | 30 | 7. If the application is running in a clustered environment, repeat Steps 3 to 6 for any application slave instances. 31 | 32 |More information
33 | 34 || For more information about... | See... | 37 |
|---|---|
| SSHing into an instance | [[Connect to your instance via SSH|ssh-connect]]. | 40 |
Enable alerts
14 | 15 | 1. In Engine Yard Cloud, click Dashboard. 16 | 2. Select an environment by clicking the environment name. 17 | 3. On the Environment page, click Enable email alerts. 18 | 5. Specify an email address to receive alerts. 19 | 6. Click Update Alert Settings. 20 | 21 | Follow the above steps for each environment that you would like to receive 22 | alerts. For instance you may not need to receive alerts for your staging 23 | environment, but rather you would want alerts for your production environment. 24 | 25 |View alerts
26 | 27 | **Note:** You can view the alerts, even if you have not enabled email alerts. 28 | 29 | 1. In Engine Yard Cloud, click Dashboard. 30 | 2. Select an environment by clicking the environment name. 31 | 3. On the Environment page, click View All Alerts. -------------------------------------------------------------------------------- /pages/rails-faq.md: -------------------------------------------------------------------------------- 1 | # Rails FAQ -------------------------------------------------------------------------------- /pages/rubinius-faq.md: -------------------------------------------------------------------------------- 1 | # Rubinius FAQ -------------------------------------------------------------------------------- /pages/rubinius.md: -------------------------------------------------------------------------------- 1 | #Rubinius 2 | 3 |  4 | 5 | The [[Rubinius 2|http://rubini.us]] interpreter is now a candidate for testing on Engine Yard Cloud. 6 | 7 | - Get access through the [[Early Access Features page|beta-intro#topic2]] or the [[sign-up|signup-rubinius]] page 8 | - [[Using Rubinius|using-rubinius-on-cloud]] 9 | - [[Using Rubinius with a trial account|beta-rubinius-environment-with-cloud-trial]] 10 | -------------------------------------------------------------------------------- /pages/ruby-193.md: -------------------------------------------------------------------------------- 1 | #Using Ruby 1.9.3 with Engine Yard Cloud 2 | 3 | Ruby 1.9.3 is currently in Beta support on Engine Yard Cloud. 4 | 5 | Ruby 1.9.3 offers faster loading times for Rails 3.x applications. For more information about this release, see [[Ruby 1.9.3 p0 is released |http://www.ruby-lang.org/en/news/2011/10/31/ruby-1-9-3-p0-is-released/]]. 6 | 7 | To upgrade your application to Ruby 1.9.3 from an earlier Ruby version, follow steps outlined in [[Migrate to Ruby 1.9.2|migration-to-newer-ruby]] (substitute "1.9.3" for "1.9.2"). 8 | 9 | -------------------------------------------------------------------------------- /pages/ruby-faq.md: -------------------------------------------------------------------------------- 1 | # Ruby FAQ -------------------------------------------------------------------------------- /pages/set-time-zone-for-an-cloud-instance.md: -------------------------------------------------------------------------------- 1 | # Set the time zone for an instance 2 | 3 | ## Steps to change the time zone: 4 | 5 | 1. Identify the desired time zone inside `/usr/share/zoneinfo`.6 | It may be common name like `EST5EDT` or identified by a popular city 7 | belonging to the time zone (e.g., `Australia/Sydney`). 8 | 9 | 2. Create or overwrite the symbolic link `/etc/localtime` pointing to the 10 | one identified above: `ln -sf /usr/share/zoneinfo/Australia/Sydney /etc/localtime` 11 | 12 | Newly created processes will now respect the new time zone. It is also a 13 | good idea to "Update instances" in your Dashboard. 14 | 15 | To make this change persist when a new instance is created, we suggest 16 | putting the command to create a symbolic link in Step 2 above in a deploy 17 | hook (anything **except for** ''after_restart'' hook will do). 18 | See [[How To Use Deploy Hooks|use-deploy-hooks-with-engine-yard-cloud]] for 19 | help with deploy hooks. 20 | -------------------------------------------------------------------------------- /pages/signup-mysql.md: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /pages/signup-node.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | -------------------------------------------------------------------------------- /pages/signup-rubinius.md: -------------------------------------------------------------------------------- 1 | #Request access to Rubinius Alpha 2 | 3 | 4 | 5 | -------------------------------------------------------------------------------- /pages/ssh-add-to-cloud.md: -------------------------------------------------------------------------------- 1 | # Add an SSH keypair to Engine Yard Cloud 2 | 3 | To use a public key generated for your development machine, the key must be uploaded through the Dashboard. 4 | 5 | ##To add an SSH key to Engine Yard Cloud 6 | 7 | 1. Locate and copy the public key on your local machine. 8 | The default location of this file is `~/.ssh/id_rsa.pub` 9 | 2. In your Dashboard, click SSH Public Keys. 10 | 3. Click Add a new SSH public key. 11 | 4. Enter a name for the key. 12 | 5. Paste the key (from Step 1) into the Public Key field. 13 | 6. Click Add Key. 14 | You receive a confirmation that your ssh public key has been created and added to your 15 | Engine Yard account. 16 | 17 | ## Next step 18 | 19 | [[Install your public key|ssh-install]] to your application environment(s). -------------------------------------------------------------------------------- /pages/ssh-connect.md: -------------------------------------------------------------------------------- 1 | # Connect to your instance via SSH 2 | 3 | After you have [[setup your keys|ssh-setup]] locally, [[added your keys|ssh-add-to-cloud]] 4 | to Engine Yard Cloud and [[installed the keys|ssh-install]] to your applications environment, you 5 | are now ready to connect to your instance(s) via an SSH client. 6 | 7 | There are two methods to start an ssh session: 8 | 9 | 1. ### Manually start a console session 10 | * Open Terminal or your preferred ssh client. 11 | * SSH using your own ip address and username `deploy`. For example: 12 | 13 | ssh deploy@123.123.123.123 14 | 15 | * SSH using your own amazon hostname and username `deploy`. For example: 16 | 17 | ssh deploy@ec2-123-123-123-123.compute-1.amazonaws.com 18 | 19 | * ### Use our automated SSH link 20 | * Go to your **Dashboard**. 21 | * Click an environment you want to connect to. 22 | * Click the **SSH** link. 23 | * You should receive a prompt to launch an ssh client. **Accept this prompt**. 24 | 25 | 26 | ### Outcome 27 | 28 | You should now be connected to an instance via an ssh session. 29 | -------------------------------------------------------------------------------- /pages/ssh-install.md: -------------------------------------------------------------------------------- 1 | # Install a public key to an environment 2 | 3 | After a key is uploaded your Engine Yard account, it needs to be associated with one or more 4 | environments. This ensures that instances contained within the environment 5 | have the ssh key installed and are accessible via an SSH client. 6 | 7 | The process to install an ssh key: 8 | 9 | * [[Update the environment|ssh-install#update]] with the ssh key. 10 | * [[Deploy keys|ssh-install#deploy]] to environment instances. 11 | 12 | 13 |
To update an environment with an ssh key
14 | 15 | 1. In your Dashboard, click the environment name. 16 | For example, the "production" environment of the "MyApp" application. 17 | 3. On the Environment page, click Edit Environment. 18 | 6. Locate the SSH Keys section and select the keys you want to install. 19 | 20 |  21 | 22 | 7. Click Update Environment to save your changes. 23 | 8. (Optional) Repeat these steps for each environment you want to install a key on. 24 | 25 | 26 |To deploy keys
27 | 28 | After an environment has been updated with one or more new keys, the keys need to be 29 | deployed to the environment instances. 30 | 31 | 1. In your Dashboard, click the environment that you want to deploy your key(s) to. 32 | 2. Click Apply to install the keys. 33 | 34 | After the keys are deployed, you can connect to your instances via ssh. 35 | 36 | ## Next step 37 | 38 | [[Connect via SSH|ssh-connect]] to your application instance(s). -------------------------------------------------------------------------------- /pages/ssh-intro.md: -------------------------------------------------------------------------------- 1 | # Using SSH on Engine Yard Cloud 2 | 3 | If you need to access an instance in your applications environment, you can 4 | login via [[SSH|http://en.wikipedia.org/wiki/Secure_Shell]]. You will need 5 | to setup SSH keys on your local development machine, add the keys to your 6 | Engine Yard account, and install the keys in any of your environments. The following 7 | topics describe each of these processes. 8 | 9 | ## Topics 10 | 11 | * ### [[Setup local SSH keys|ssh-setup]] 12 | Learn how to generate an ssh keypair on your local machine. 13 | 14 | * ### [[Add a key to Engine Yard Cloud|ssh-add-to-cloud]] 15 | Learn how to add your SSH public key to your Engine Yard account. 16 | 17 | * ### [[Install keys to your application environments|ssh-install]] 18 | Learn how to install your keys to instances in your applications environment. 19 | 20 | * ### [[Connect to an instance via SSH|ssh-connect]] 21 | Learn how to connect to your instance via SSH. 22 | 23 | * ### [[Windows and SSH keys|ssh-windows]] 24 | Learn how to generate SSH keys and add them to Engine Yard Cloud on Windows. 25 | 26 | * ### [[Troubleshooting|ssh-troubleshooting]] 27 | Tips to help you troubleshoot issues related to SSH on Engine Yard Cloud. 28 | -------------------------------------------------------------------------------- /pages/steps-to-recover-from-us-east-outage.md: -------------------------------------------------------------------------------- 1 | # Steps to recover from a US-East outage 2 | 3 | **If data retention is more important to you at this time, we are recommending that you wait it out now until full operation is restored. Looking at the AWS status page now (http://status.aws.amazon.com), it doesn't sound like this can be too much further away.** 4 | 5 | **Steps to recover if multi-region is not an option** 6 | 7 | *Trying a different subzone* 8 | 9 | Some customers have been able to utilize our multi-region beta feature to move to another availability zone. However, it may be best to first try and create on East in a different sub zone since this would be the simplest option. Amazon is stating that all but one subzone in the US East region is operating properly. Unfortunately, the zone labels are assigned differently on a per-client basis to aid in load balancing -- so we recommend using trial-and-error by selecting a specific zone in the “Edit Environment” link on the Environment page. 10 | 11 | *Note about snapshots* 12 | 13 | Taking snapshots can fail if your volume is affected by the EBS problem. Normally when an environment is terminated we initiate snapshots of the volumes required to bring the environment back up to its previous state. This can fail for the environment affected by this problem. If you choose to take down the environment, it can result in data loss. 14 | 15 | **Steps to recover if multi-region is an option** 16 | 17 | Follow the directions on [[Moving your site to US West|moving-your-site-to-us-west-zone]] -------------------------------------------------------------------------------- /pages/systemtimer-gem-ki.md: -------------------------------------------------------------------------------- 1 | #SystemTimer gem is not supported in Ruby 1.9.2 2 | 3 | Currently, Ruby 1.9.2 does not support the SystemTimer gem. 4 | 5 | If you are using the SystemTimer gem, either remove it as a dependency or use the following code to prevent errors: 6 | 7 | gem 'SystemTimer', :platforms => [:ruby_18] -------------------------------------------------------------------------------- /pages/trouble-termination-failed.md: -------------------------------------------------------------------------------- 1 |Termination Failed error when shutting down an instance
2 | 3 | Occasionally, Amazon cannot shut down an instance when a termination request is made. If this happens, you get a "Termination Failed" message. 4 | 5 | The Instances list on the Environment page shows "Termination Failed" for one or more instances. 6 | 7 |  8 | 9 |To resolve a Termination Failed error
10 | 11 | 1. Do one of the following: 12 | 13 | * Click Retry to try again to terminate the instance. If the instance does not terminate within 10 minutes, you see another "Termination Failed" message. 14 | 15 | * Click Force to force-terminate the instance. 16 | 17 | Important! If you select Force, the termination snapshot might not be good. If you later boot a cluster and use a "force-terminated" snapshot for the application instance, make sure to test the instance. -------------------------------------------------------------------------------- /pages/tutorials_home.md: -------------------------------------------------------------------------------- 1 | # Tutorials 2 | 3 | Welcome to the Tutorials section. You can find information here that is focused on helping you learn to get started as a Ruby or Rails developer. 4 | 5 | * [[Setup Environment]] 6 | * [[Basic Git Commands]] 7 | * [[Create your Rails Application]] 8 | * [[Host your Code on GitHub]] 9 | * [[Create your Bundler Gemfile]] 10 | 11 | If you have ideas for tutorials you'd like to see, please [[docs@engineyard.com|email us]]. 12 | 13 | Check out this [[http://www.decisionesinteligentes.com/guides|Spanish translation of the tutorials]], courtesy of Mario Alberto Chavez Cardenas of [[http://www.decisionesinteligentes.com/|Decisiones Inteligentes]] and [[http://tijuanarb.org/|Tiajuana.rb]]. 14 | -------------------------------------------------------------------------------- /pages/usage-graphs.md: -------------------------------------------------------------------------------- 1 | # Viewing usage graphs on Engine Yard Cloud 2 | 3 | Engine Yard Cloud provides usage data gathered by the [[rrdtool|http://oss.oetiker.ch/rrdtool/]] for you to be able to review and analyze. 4 | 5 | ## To view usage graphs: 6 | 7 | 1. Login to your account. 8 | 2. Click an environment name from your Dashboard. 9 | 3. Click Graphs for the instance. 10 | 4. Click any metric link to view usage graphs for that metric. 11 | 12 |  13 | -------------------------------------------------------------------------------- /pages/using-multi-region-with-engine-yard-cloud.md: -------------------------------------------------------------------------------- 1 | # Using Multi-Region on Engine Yard Cloud 2 | 3 | 4 | With Multi-Region in Engine Yard Cloud, an entire environment and its instances 5 | can be located in a particular geographic region around the world. 6 | 7 | If a majority of your application users are based in a certain region, then locate your environment in the region that is closest to those users. This can lower latency and response 8 | times for your users in that region. 9 | 10 | 11 | These AWS regions are supported: 12 | 13 | * US East (N. Virginia), us-east-1 14 | * US West (N. California), us-west-1 15 | * US West (Oregon), us-west-2 16 | * EU West (Dublin), eu-west-1 17 | * Asia Pacific (Singapore), ap-southeast-1 18 | * Asia Pacific (Tokyo), ap-northeast-1 19 | * South America (Sao Paulo), sa-east-1 20 | 21 | 22 | 23 | 24 |  25 | 26 | 27 | ## Current limitations 28 | 29 | * Environments cannot be migrated to a new region (the region cannot be changed). 30 | * Environments can be cloned, but only in the same region. 31 | * IP addresses are assigned to a region -- and thus cannot be moved to a different region. 32 | * All limitations regarding the number of instances, IP addresses, and snapshots are per-region. 33 | * Pricing within each region is subject to change. 34 | 35 | ## To boot an environment in any region 36 | 37 | When [[creating a new environment|environment-create]], select the 38 | region this environment should be deployed to. Finish configuring this 39 | environment and click Create Environment. 40 | 41 | When the environment has been saved, configure your environment instances on the next page 42 | and boot. This environment is now being deployed in the Region you selected. 43 | 44 |More information
45 | 46 || For more information about... | See... | 49 |
|---|---|
| Moving your application to a different region | [[Moving your application to a different region|moving-your-site-to-us-west-zone]]. | 52 |