Hi Craig,

Thanks for your advice.

> Rails is entirely indifferent to whatever you put into the 'image_tag'
That's what I expected.  Asking about it is like taking a Flu shot: it
wards off possible ills.

> root should never be the user of any sql database ...
I agree, with the exception of my machine that is:
- protected from the Net and malware
- I am the sole user
- and it's only for development purposes

BTW, that's how the author posted the code.

On Feb 26, 7:48 pm, Craig White <craigwh...@azapple.com> wrote:
> On Fri, 2010-02-26 at 16:30 -0800, RichardOnRails wrote:
> > Hi ALL,
>
> > I'm building a Rails app using the app provided in Ruby On Rails
> > Cookbook.  The book's app works "out of the box" after appropriate
> > tweaks: adding a "log" directory, adding a root password in
> > database.yml and a couple of rake executions ... which is more than I
> > can say for many books.  (Just wanted to give it a plug.)
>
> > In public/images he's got a main_logo.png file which he references in
> > the <body> of application.html.erb in
> > ink_to image_tag('main_logo.png').
>
> > I've got a .jpg that I'd use in place of a .png because my JPEG loses
> > detail when I convert to PNG.  I expect that JPEGs and GIFs and other
> > major graphic encodings should work just as well in Rails as PNGs.  Is
> > that true?
>
> > I ask because despite the fact that I'm using a working Rails app as
> > guide,  I'm confident I'll make some mistakes I'll have to debug.  I'm
> > just trying in advance to avoid one here.
>
> ----
> Debugging and trying many things and causing errors is an essential part
> of the learning process itself.
>
> Rails is entirely indifferent to whatever you put into the 'image_tag'
> because all it really does is create the normal <img src=""> html tag
> and then it's up to the server to deliver the file and the web browser
> to parse it and display it.
>
> Also - FTR - when you say 'adding a root password in database.yml' that
> immediately makes me nervous because root should never be the user of
> any sql database - at least in my opinion.
>
> Craig
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.

-- 
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-t...@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