On Nov 12, 2010, at 8:27 AM, Philip Hallstrom wrote: >> On Fri, Nov 12, 2010 at 9:51 AM, Philip Hallstrom <[email protected]> wrote: >> > I have the following constant in production.rb: >> > GSA_EPLS_DATASOURCE = FILESTORE + "/" + "datafiles/gsa_epls.xml" >> > >> > The constant FILESTORE is located in environment.rb: >> > FILESTORE = "../creditcompare_filestore/" + Rails.env >> > >> > When I try to migrate my db on heroku I get this error which points to the >> > line above in production.rb >> > >> > uninitialized constant FILESTORE >> > >> > >> > So I am gathering that there is a load sequence issue. I am trying to keep >> > FiLESTORE in highest level as it applies to all environments... I dont >> > have to but would like to. Is there a way to do what I am trying to do? >> >> I see you already solved this, but you might look into something like >> SettingsLogic.... >> >> https://github.com/binarylogic/settingslogic >> >> Hey Philip, that looks really cool - thanks for sharing. Not sure if you >> know, but my challenge is I push to heroku for staging (product owner >> review), but my production environment is elsewhere on our own Ubuntu >> server. Is there a way to create two production environments -- say >> :production_heroku and :production_live? What I am doing now is having an >> extra production.rb off in a sub folder and when I push to the real >> production environment I tell capistrano to replace the existing production >> file which corresponds to heroku... > > You want Capistrano's multistage functionality... > > http://weblog.jamisbuck.org/2007/7/23/capistrano-multistage > > Create a "staging" environment file, entry in database.yml, and anywhere else > you have development/production stuff... > > Then you can do > > cap staging deploy # to heroku > > cap production deploy # to ubuntu
I realized I read to quickly... heroku has it's own deployment setup. If you can change the environment you to deploy to on heroku then you could still do what I've said above. Otherwise, you could cheat and create :production (for heroku) and :really_really_production (for ubuntu) and then use what I've said above. Not quite as nice, but it would work. -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
