Forum: Ruby on Rails Running a rails project in another folder

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Shockmeister (Guest)
on 2008-12-22 21:28
(Received via mailing list)
Hi all,

I want to transfer a rails project (still under development) from my
aptop to my pc. I copied the project folder into the ruby directory on
my pc and ran it with mongrel (ran successfully). However, when I try
to access the site through the browser, the pages won't display. What
am I doing wrong?
Maulin p. (Guest)
on 2008-12-22 23:27
I dont think you can just copy the application folder over. Try running
rails <app_name> command on your pc and then copy the app folder over
and all other files that you may have changed (routes, db.yaml...etc)

I have never done this myself, so let me know how it goes :)

> am I doing wrong?
Dejan D. (Guest)
on 2008-12-22 23:49
(Received via mailing list)
It is custom to copy the folder from one location to another and then
adjust the database.yml if required and other dependent configuration

How do you verify that your application on pc using mongrel is
What database are you  using?
What is the contents of application log file (considered the

Give us some more information so we can help you.

On Dec 22, 10:27 pm, Maulin P. <removed_email_address@domain.invalid>
Swift Y. (Guest)
on 2008-12-23 02:56
(Received via mailing list)
what do you mean by the browser just came up nothing? or is there any
hint about the errors..

showing us whatever it displayed maybe helpful

and by the way

modifying you database.yml file is recommanded just after you maved
the project directory.

so check that first.
Shockmeister (Guest)
on 2008-12-24 10:21
(Received via mailing list)
Hi guys,

Sorry for the delay in replying. Thanks for your replies. It was
indeed my database.yml that was giving the problem. Its now working

Thanks again,

This topic is locked and can not be replied to.