Topic: Config Production Rails App to Run Locally for Development
Hello, all. I'm an experienced developer in ASP.Net and C#, with very little Rails experience...a definite n00b. A real-world opportunity to learn some Rails has fallen in my lap and though I welcome it, I'm feeling a bit lost in the woods at the moment.
I've been asked by a new client to provide some minor changes to a production Rails app. Either the original developer has abandoned the client, or the client had a falling out with them a couple of years back. I'm not sure which is the true case, but regardless, the job falls on me to make the changes and get the app deployed on the production server.
At this point I'm not even sure what questions to ask, but here is what I have learned about the app and production deployment so far:
Rails 2.3.2 according to the environment.rb file. I've installed that on my Windows box after installing Ruby 1.8.7 and Ruby Gems 1.8.15. I believe all of this installed without issue.
I have all the production files and production DB (MySQL) downloaded from Slicehost.
When I tried to start the rails server (rails s) from within the root of the local site, I got an error about various missing dependencies related to something called ActiveSupport. (Sorry...don't have the specific errors as I am posting this from my day-job PC).
I know nothing about "Capistrano" other than that it is a tool used with Git to deploy sites, but there is a "Capify" file in the root of the site. I'm hoping that that will make my eventual deployment easier.
The app is basically a simple CMS and I have been asked to add a an additional checkbox to one of the backend pages. I have identified which view needs to be changed and the associated helper file. I know that to make those changes work I need to create a migration to add this additional column to the database...I know this is the case because this new checkbox is related to the start of a new year and I can see the migration .rb script that the previous developer created a year ago to do the exact same change last year!
So based on the above, I'm pretty sure that this is a pretty simple modification. If I could just get this app up and running locally, I'm pretty confident I can make the changes. Any advice on how to get up and running locally would be greatly appreciated.