|
| 1 | +# Engine Yard Cloud Deploy Options |
| 2 | +# |
| 3 | +#################################################################### |
| 4 | +# IMPORTANT |
| 5 | +# Commit this file into your git repository. |
| 6 | +# These options are loaded on the server during deploy. |
| 7 | +#################################################################### |
| 8 | +# |
| 9 | +# Valid locations: |
| 10 | +# * REPOSITORY_ROOT/config/ey.yml. |
| 11 | +# * REPOSITORY_ROOT/ey.yml |
| 12 | +# |
| 13 | +# Further information available here: |
| 14 | +# https://support.cloud.engineyard.com/entries/20996661-customize-your-deployment-on-engine-yard-cloud |
| 15 | +# |
| 16 | +# For advanced usage, see the source that loads this configuration: |
| 17 | +# https://github.com/engineyard/engineyard-serverside/blob/master/lib/engineyard-serverside/configuration.rb |
| 18 | +# |
1 | 19 | defaults: |
2 | | - copy_exclude: |
3 | | - - .git |
| 20 | + # Enables rails assets precompilation always and halts when the task fails. |
| 21 | + # |
| 22 | + # By default, assets are detected using app/assets and config/application.rb. |
| 23 | + # |
| 24 | + # If you use rails assets and you want Engine Yard to compile your assets |
| 25 | + # during deploy, set this to true. If you want to compile assets locally |
| 26 | + # before deploy, set this to false. Make sure you add `public/assets` to |
| 27 | + # `.gitignore` if you want Engine Yard to precompile your assets. |
| 28 | + # |
| 29 | + # For more control over assets, set precompile_assets: false and |
| 30 | + # run your precompile task in the deploy/before_compile_assets.rb deploy hook. |
| 31 | + # |
4 | 32 | precompile_assets: true |
| 33 | + |
| 34 | + # Override the assets:precompile rake task. This option will be used instead |
| 35 | + # of assets:precompile in the `rake assets:precompile` command. |
| 36 | + # |
| 37 | + #precompile_assets_task: assets:precompile |
| 38 | + |
| 39 | + # Asset strategies affect the way assets are stored on the server. |
| 40 | + # |
| 41 | + # * private |
| 42 | + # Store assets directly in public/assets for each deployment. |
| 43 | + # Previous assets are symlinked for continuity. |
| 44 | + # When assets are reused, they are copied using rsync. |
| 45 | + # |
| 46 | + # * shifting |
| 47 | + # Assets are kept in a shared directory on each server. |
| 48 | + # When new assets are compiled, old assets are shifted to a shared |
| 49 | + # last_assets directory. This has always been the default behavior. |
| 50 | + # |
| 51 | + # * shared |
| 52 | + # Assets are kept in a shared directory on each server. |
| 53 | + # When new assets are compiled, the same directory is used. |
| 54 | + # Assets will accumulate in this mode if a cleaning script is not run. |
| 55 | + # Use this strategy if you want to write your own asset cleaning script. |
| 56 | + # |
| 57 | + # * cleaning |
| 58 | + # Like shared, but a cleaning script is run before each new compile. |
| 59 | + # The script attempts to remove all files not mentioned by the old |
| 60 | + # manifest.yml, before it is replaced by the new manifest (leaving 2 |
| 61 | + # deployments worth of assets in the directory) |
| 62 | + # |
| 63 | + # "private" is recommended because it is the least error prone. |
| 64 | + # If you prefer faster compilation, "shared" can be quicker, but will require |
| 65 | + # custom scripting and will cause problems when rollbacks are used. |
| 66 | + # "shifting" is the default behavior. |
| 67 | + # |
| 68 | + #asset_strategy: private |
| 69 | + |
| 70 | + # This list of repository relative paths is checked for changes during |
| 71 | + # each deployment (when change detection is not disabled). If `git diff` |
| 72 | + # detects changes since the last deployment, fresh assets will be compiled. |
| 73 | + # |
| 74 | + # This option overrides the default list, so include the following |
| 75 | + # defaults if you need them. |
| 76 | + # |
| 77 | + #asset_dependencies: |
| 78 | + #- app/assets # default |
| 79 | + #- lib/assets # default |
| 80 | + #- vendor/assets # default |
| 81 | + #- Gemfile.lock # default |
| 82 | + #- config/application.rb # default |
| 83 | + #- config/routes.rb # default |
| 84 | + #- config/requirejs.yml # example of a custom asset dependency |
| 85 | + |
| 86 | + # When true, precompiles assets even if no changes would be detected by |
| 87 | + # running git diff with the asset_dependencies above. |
| 88 | + # |
| 89 | + # Default is false (always check git diff before asset compilation) |
| 90 | + # |
| 91 | + #precompile_unchanged_assets: false |
| 92 | + |
| 93 | + # Choose which servers should compile assets. |
| 94 | + # |
| 95 | + # Default behavior is to exclude util instances. |
| 96 | + # Specify :all to compile on all servers including util servers. |
| 97 | + # |
| 98 | + #asset_roles: :all |
| 99 | + |
| 100 | + # Bundle without different bundler groups: |
| 101 | + # Ex: bundle install --without '[bundle_without]' |
| 102 | + # |
| 103 | + # Default is "". |
| 104 | + # Leave blank to remove --without from the bundle install command. |
| 105 | + # |
| 106 | + #bundle_without: |
| 107 | + |
| 108 | + # Add extra options to the bundle install command line. |
| 109 | + # Does not override bundle_without, if specified. |
| 110 | + # |
| 111 | + # If the application's gems are vendored in the |
| 112 | + # repository, setting --local can speed up bundle. |
| 113 | + # |
| 114 | + #bundle_options: |
| 115 | + |
| 116 | + # Enable maintenance page during migrate action (default) |
| 117 | + # Setting this to false, disables maintenance page during migrations. |
| 118 | + # |
| 119 | + # CAUTION! No-downtime migrations requires careful migration |
| 120 | + # planning. Migrations must be non-destructive. The *previous* |
| 121 | + # deployment might serve pages during a partially migrated state. |
| 122 | + # For example, if you rename a column, all traffic served during |
| 123 | + # that migration will be broken until the new code is deployed. |
| 124 | + # |
| 125 | + #maintenance_on_migrate: true |
| 126 | + |
| 127 | + # Enable maintanence page during every deploy. |
| 128 | + # Unicorn and Passenger support no-downtime deploys, so the default |
| 129 | + # for these servers is false. Mongrel and some other servers default |
| 130 | + # to true to avoid downtime during server restarting. |
| 131 | + # |
| 132 | + #maintenance_on_restart: |
| 133 | + |
| 134 | + # If true, always run deployments in verbose mode. |
| 135 | + # |
| 136 | + #verbose: false |
| 137 | + |
| 138 | + # Hide the warning shown when the Gemfile does not contain a recognized |
| 139 | + # database adapter (mongodb for example) |
| 140 | + # |
| 141 | + # This warning is here to help new customers that accidentally have no adapter. |
| 142 | + # You may safely set this to true if you aren't using a common database. |
| 143 | + # |
| 144 | + #ignore_database_adapter_warning: false |
| 145 | + |
| 146 | + # You can add custom keys that will be available in your deploy hooks. |
| 147 | + # Custom keys will be available using config.key or config[:key] |
| 148 | + # |
| 149 | + #your_own_custom_key: custom info |
| 150 | + |
| 151 | + copy_exclude: |
| 152 | + - ".git" |
| 153 | + |
5 | 154 | ignore_gemfile_lock_warning: true |
| 155 | + |
| 156 | + |
| 157 | +#################################################################### |
| 158 | +# Environment specific options. |
| 159 | +# |
| 160 | +# The options you specify here will only apply to a single environment |
| 161 | +# that exactly matches the environment name key. |
| 162 | +# |
| 163 | +# Environment options will override the default options above. |
| 164 | +# |
| 165 | +environments: |
| 166 | + |
| 167 | + # These options will only apply to the EXAMPLE_ENVIRONMENT environment. |
| 168 | + #EXAMPLE_ENVIRONMENT: |
| 169 | + #precompile_unchanged_assets: true |
0 commit comments