On Dec 12, 2011, at 6:34 PM, gato pardo wrote:

> 
> 
> >    I should remenber  that there are no great differences between 
> > development and production section in the database yml file.
> >
> > # config/database.yml
> > development:
> >   adapter: postgresql
> >   encoding: unicode
> >   database: db_album
> >   pool: 5
> >   username: user
> >
> >   And yes, I am using the same database for both environments. (maybe I 
> > should use another database for production), but what get me confused is 
> > that I get access to the database from any other node in the network when 
> > rails is not the tool used.
> >
> >    I shall tried with other database users and other database in this 
> > application.
> >
> >  Thanks
> ----
> and what does
> production:
>  adapter: ?
>  encoding: ?
>  database: ?
>  pool: ?
>  username: ?
> 
> look like?
> 
> Craig
> 
> Craig:
> 
> as I said, there is no difference between the two sections 
> 
> production:
>   adapter: postgresql
>   encoding: unicode
>   database: db_album
>   pool: 5
>   username: user
>   password:  
> 
>   And, the strange in it all is that it has worked before.
----
well I can only comment on what I see and what I don't see and I don't see 
anything that relates to 'how' the connection to the database server is being 
made (TCP/IP or local socket) and since the first post suggested that you were 
using 'postgres' as the 'username' - that almost requires that it be a local 
socket and not TCP/IP. Of course you can bend pg_hba.conf and give user 
'postgres' a password and I would have absolutely no way of knowing that.

I think if you want some more useful help, you're going to have to supply more 
details.

Craig

-- 
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.
To unsubscribe from this group, send email to 
rubyonrails-talk+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en.

Reply via email to