Passing in environment variables? about eye HOT 6 CLOSED

Hi, yeah i understand the problem. Never used it.
There is little difference with bluepill, bluepill start new server every load (so start it with all local env variables), but eye not. So not easy to transfer env variables to already runned eye server (you can do it only with first load) with current config-parsing model.

So such variant works:

1.eye

Eye.app :some do
  env 'RAILS_ENV' => ENV['RAILS_ENV']
end

RAILS_ENV=dev eye load 1.eye

eye x -c

Current config: 
---
:settings: {}
:applications:
  some:
    :name: some
    :environment:
      RAILS_ENV: dev

after first load you can not change env variables:

RAILS_ENV=dev2 eye load 1.eye

eye x -c

Current config: 
---
:settings: {}
:applications:
  some:
    :name: some
    :environment:
      RAILS_ENV: dev

I prefer this variant:

common.rb

Eye.app :some do
  env 'RAILS_ENV' => RAILS_ENV
end

dev.eye

RAILS_ENV='development'
Eye.load('common.rb')

prod.eye

RAILS_ENV='production'
Eye.load('common.rb')

from eye.

Thank you, Kostya. I'll give this a shot! I didn't understand how the server works so this is helpful. On another note, if we manually kill/quit the server, can you reload it with a new environment?

This would not work:

RAILS_ENV=dev1 eye load 1.eye
RAILS_ENV=dev2 eye load 1.eye

But would this work?

RAILS_ENV=dev1 eye load 1.eye
eye quit
RAILS_ENV=dev2 eye load 1.eye

from eye.

yes this should work, but looks strange

from eye.

OK, thanks. Typically we only do this during a deploy, so our deploy generally is loading the config up, and when we re-deploy we shut all the jobs down (quit), deploy code, then fire up the new code, so that we don't have any old code being run by any of our background jobs.

Is there a better way you can see us using this? Thanks!

from eye.

if you do quit it not stops monitored processes. you should call stop.
my deploy here: https://github.com/kostya/eye/wiki/Deploy-with-capistrano

from eye.

Right, gotcha. Bluepill works the same way: a stop to quit the processes, then a quit to terminate the manager. OK, thanks for that link. You've been extremely helpful, thank you!

from eye.