etsy / deployinator

Deployinate!

Home Page:http://etsy.me/deployinator

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Can't access custom Deployinator properties in `config/base.rb`

mrtazz opened this issue · comments

I'm defining custom attributes via attr_accessor in the local Deployinator configuration and then set it to an empty hash in config/base.rb. However it seems like for base config the Deployinator module from the vendorized gem is used. It works fine in config/development.rb and config/production.rb.

relevant sinatra stacktrace:

undefined method `cheffilez=' for Deployinator:Module

/path/deployinator/config/base.rb   46  in `'
1   /path/deployinator/vendor/bundle/ruby/1.9.1/bundler/gems/deployinator-438a82f58710/lib/deployinator/config.rb   4   in `require'
2   /path/deployinator/vendor/bundle/ruby/1.9.1/bundler/gems/deployinator-438a82f58710/lib/deployinator/config.rb   4   in `'
3   /path/deployinator/vendor/bundle/ruby/1.9.1/bundler/gems/deployinator-438a82f58710/lib/deployinator/base.rb 10  in `require'
4   /path/deployinator/vendor/bundle/ruby/1.9.1/bundler/gems/deployinator-438a82f58710/lib/deployinator/base.rb 10  in `'
5   config.ru   2   in `require'
6   config.ru   2   in `block in
'
7   /path/deployinator/vendor/bundle/ruby/1.9.1/gems/rack-1.6.0/lib/rack/builder.rb 55  in `instance_eval'
8   /path/deployinator/vendor/bundle/ruby/1.9.1/gems/rack-1.6.0/lib/rack/builder.rb 55  in `initialize'
9   config.ru   1   in `new'
10  config.ru   1   in `
'
11  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/rack/application_spawner.rb  225 in `eval'
12  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/rack/application_spawner.rb  225 in `load_rack_app'
13  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/rack/application_spawner.rb  157 in `block in initialize_server'
14  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/utils.rb 563 in `report_app_init_status'
15  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/rack/application_spawner.rb  154 in `initialize_server'
16  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/abstract_server.rb   204 in `start_synchronously'
17  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/abstract_server.rb   180 in `start'
18  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/rack/application_spawner.rb  129 in `start'
19  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/spawn_manager.rb 253 in `block (2 levels) in spawn_rack_application'
20  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/abstract_server_collection.rb    132 in `lookup_or_add'
21  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/spawn_manager.rb 246 in `block in spawn_rack_application'
22  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/abstract_server_collection.rb    82  in `block in synchronize'
23      prelude>    10:in `synchronize'
24  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/abstract_server_collection.rb    79  in `synchronize'
25  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/spawn_manager.rb 244 in `spawn_rack_application'
26  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/spawn_manager.rb 137 in `spawn_application'
27  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/spawn_manager.rb 275 in `handle_spawn_application'
28  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/abstract_server.rb   357 in `server_main_loop'
29  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/lib/phusion_passenger/abstract_server.rb   206 in `start_synchronously'
30  /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.15/helper-scripts/passenger-spawn-server  99  in `
'

@mrtazz You most likely need need to require your local deployinator configuration with the accessor included before you require deployinator/base but after you require deployinator

yup this is indeed an internal bug. Thanks! :)