Re: rake about > Environment staging

tom
2012-06-14T15:11:46Z

good points rick, it lead me to the issue: my system-user groupmembership
was wrong. i added for some other reasons my system user to the root and
some other groups...that messed everythign up. using a new user, same rvmrc
& Gemfile works again as expected.
thx


On Mon, Jun 11, 2012 at 3:30 PM, Rick
<richard.t.lloyd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> I''m not really too up on rvm but I wonder...
>
> Is it possible that your work environment, specifically the login shell
> that you are using to type commands in a terminal window, includes an alias
> for rake?  Since staging is not one of the three default environments for
> RoR it had to be created with all rules for it''s use somewhere
"outside"
> the vanilla system.
>
> What I''m thinking is that somewhere you have a runtime command
file (eg.:
> .bashrc, .cshrc, .profile, ...) that contains a line:
>          *alias rake=''rake RAILS_ENV=staging''*
>
> To find out if this is so, type:
>          *alias rake*
>
> Rick
>
>
> On Sunday, June 10, 2012 7:19:30 AM UTC-4, der_tom wrote:
>>
>> inline
>>
>> On Sun, Jun 10, 2012 at 12:30 PM, Colin Law
<clanlaw-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>wrote:
>>
>>> On 10 June 2012 11:19, tom
<tomabroad-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>>
>>> Top posting still :(
>>>
>>> > yes, thats correct
>>> >
>>> > RAILS_ENV=development rake db:migrate
>>> >>> runs in staging env.
>>>
>>> I don''t understand why you then went on to ask
>>> >> > where does rake get the environment info if i ommit
''RAILS_ENV''
>>> when
>>> >> > executing a rake command?
>>>
>>> Two points (please reply inline so that it makes it easier to
follow
>>> the thread.  Thanks
>>>
>>> 1. How do you know that rake db:migrate is running in staging
>>> environment?
>>> > because the migrations are being executed on the staging-db
(eg adding
>>> a new colum)
>>> 2. Please post database.yml here.
>>>
>>
>> >> database.yml is pretty much standard:
>>
>> staging:
>>   adapter: mysql2
>>   encoding: utf8
>>   reconnect: false
>>   database: myproject_staging
>>   pool: 5
>>   username: myproject_dbuser
>>   password: myproject_dbuser
>>   socket: /var/run/mysqld/mysqld.sock
>> development:
>>   adapter: mysql2
>>   encoding: utf8
>>   reconnect: false
>>   database: myproject_development
>>   pool: 5
>>   username: myproject_dbuser
>>   password: myproject_dbuser
>>   socket: /var/run/mysqld/mysqld.sock
>> test:
>>   adapter: mysql2
>>   encoding: utf8
>>   reconnect: false
>>   database: myproject_test
>>   pool: 5
>>   username: myproject_dbuser
>>   password: myproject_dbuser
>>   socket: /var/run/mysqld/mysqld.sock
>> production:
>>   adapter: mysql2
>>   encoding: utf8
>>   reconnect: false
>>   database: myproject_production
>>   pool: 5
>>   username: myproject_dbuser
>>   password: myproject_dbuser
>>   socket: /var/run/mysqld/mysqld.sock
>>
>>
>> >> as i said, starting webrick works fine in different
environments,
>> whereas rake tasks always use "staging", no matter what
specify. here a
>> sample of a migration:
>> rails g migration add name_to_testbooks name:string
>> /home/tom/.rvm/gems/ruby-1.9.**3-p194@mygemset/gems/railties-**
>> 3.2.1/lib/rails/script_rails_**loader.rb:11: warning: Insecure world
>> writable dir /home/tom in PATH, mode 040777
>> /home/tom/.rvm/gems/ruby-1.9.**3-p194@global/gems/bundler-1.**
>> 1.4/lib/bundler/runtime.rb:**211: warning: Insecure world writable dir
>> /home/tom in PATH, mode 040777
>>       invoke  active_record
>>       create    db/migrate/20120610111033_**add.rb
>> tom@debian6ror3:~/rails3/**myproject$ RAILS_ENV=development rake
>> db:migrate --trace
>> /home/tom/.rvm/gems/ruby-1.9.**3-p194@global/gems/bundler-1.**
>> 1.4/lib/bundler/runtime.rb:**211: warning: Insecure world writable dir
>> /home/tom in PATH, mode 040777
>> ** Invoke db:migrate (first_time)
>> ** Invoke environment (first_time)
>> ** Execute environment
>> ** Invoke db:load_config (first_time)
>> ** Invoke rails_env (first_time)
>> ** Execute rails_env
>> ** Execute db:load_config
>> ** Execute db:migrate
>> ==  Add: migrating ==============================**
>> =============================>> -- add_column(:testbooks, :name,
:string)
>>    -> 0.3212s
>> ==  Add: migrated (0.3216s) ==============================**
>> ====================>>
>> ** Invoke db:_dump (first_time)
>> ** Execute db:_dump
>> ** Invoke db:schema:dump (first_time)
>> ** Invoke environment
>> ** Invoke db:load_config
>> ** Execute db:schema:dump
>>
>>
>> furthermore, removing staging from the database.yml results in rake
>> telling me that it doesnt find a staging adapter - even though when i
run
>> in ''''dev mode"
>>
>> @rvm i installed a user-rvm, straight from the docs. does that
interfere?
>>
>> @ill setup a new user and rvm  again, then reusing the GEMFILE/rvmrc
>>
>>
>>
>>
>>
>>
>>
>>> Colin
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Ruby on Rails: Talk" group.
>>> To post to this group, send email to
rubyonrails-talk@googlegroups.**com<rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
>>> .
>>> To unsubscribe from this group, send email to
>>>
rubyonrails-talk+unsubscribe@**googlegroups.com<rubyonrails-talk%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
>>> .
>>> For more options, visit this group at http://groups.google.com/**
>>>
group/rubyonrails-talk?hl=en<http://groups.google.com/group/rubyonrails-talk?hl=en>
>>> .
>>>
>>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Talk" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/rubyonrails-talk/-/c1sYuOVIS5oJ.