- #DEPLOY RUBY RACK APP ELAASTIC BEANSTALK INSTALL#
- #DEPLOY RUBY RACK APP ELAASTIC BEANSTALK 64 BIT#
- #DEPLOY RUBY RACK APP ELAASTIC BEANSTALK UPDATE#
- #DEPLOY RUBY RACK APP ELAASTIC BEANSTALK FULL#
RollingUpdateEnabled: false #- development: MinSize: 0 MaxSize: 0 Cooldown: 900 aws :autoscaling :updatepolicy :rollingupdate: #- # Set "inactive_settings" for saving cost on blue green deployment # inactive: com ' aws:elasticbeanstalk:application: Application Healthcheck URL: '/ health' # Any environment variables - will be available in ENV aws :elasticbeanstalk :application :environment:įOO: ' bar ' RAILS_SKIP_ASSET_COMPILATION: true # Use if doing asset compilation before packaging (recommended) aws:autoscaling:launchconfiguration: EC2KeyName: eb-ssh SecurityGroups: ' acme- production- control ' aws:autoscaling:asg: MinSize: 1 MaxSize: 5 # Restrict to Reserved Instance zone: ' Custom Availability Zones ': us-east-1c ' Availability Zones ': Any 1 aws:elb:loadbalancer: SSLCertificateId: ' arn :aws :iam:: XXXXXXX :server- certificate/ acme ' LoadBalancerHTTPSPort: 443 aws:elb:policies: Stickiness Policy: true aws:elasticbeanstalk:sns:topics: Notification Endpoint: ' alerts. config:Ĭommand: rake db :seed leader_only: true #- options: Git: patch: # Run rake tasks before an application deployment 03- rake.
#DEPLOY RUBY RACK APP ELAASTIC BEANSTALK INSTALL#
# Install git in order to be able to bundle gems from git packages: config:Ĭommand: "ln -sf /usr/share/zoneinfo/America/Chicago /etc/localtime" # These are things that make sense for any Ruby application 02- ruby. # General settings for the server environment 01- environment. Verbose: true includes: # ensure '.' manifest is added when using assets:precompile exclude_dirs: # additional dirs that merge with default excludes exclude_files: smoke_test: |ĮbSmokeTester.
#DEPLOY RUBY RACK APP ELAASTIC BEANSTALK UPDATE#
0.0 running Ruby 2.2 ( Passenger Standalone ) strategy: inplace- update # default to inplace-update to avoid starting new environments keep_latest: 10 package:
#DEPLOY RUBY RACK APP ELAASTIC BEANSTALK 64 BIT#
#- app: acme region: us- east- 1 # Choose a platform from solution_stack_name: 64 bit Amazon Linux 2015.03 v2.
#DEPLOY RUBY RACK APP ELAASTIC BEANSTALK FULL#
#- # This is a sample that has not been executed so it may not be exactly 100%, but is intended to show # that access to full options_settings and. # This is a sample that has not been executed so it may not be exactly 100%, but is intended to show # that access to full options_settings and. A real-world exampleĭeploy version 1.1.3 of acme to production using the :environment parameter If specified to the eb:package task, the version will be available as the APP_VERSIONĮnvironment variable, specified in the aws:elasticbeanstalk:application:environment section of the. If not specified, version will be auto-generated via and MD5 hash of the package file. In aws:elasticbeanstalk:application:environment section of the. NOTE: if using the argument :environment, you must specify it for both the eb:package and eb:deploy, as eb:package is responsible for injecting the RACK_ENV and RAILS_ENV Where the task specifies, consider the :environment optional if you want to use the default of development or utilize the RAILS_ENV instead. Depending on the use case, each one can be DRYer than the other. Some people prefer to use RAILS_ENV, others prefer to use the :environment argument. Note that this location is configurable in the config/eb.yml file. This is the only file that will need to reside outside the repository. This should contain the access and secret keys generated from the selected IAM user. Given an application named 'acme': Step 1: Add ~/.aws/acme.yml