Re: Staging Environments
Hello Neil, Just keep in mind that Heroku defaults to using the master branch. I think you can override this during the heroku command see: http://jqr.github.com/2009/04/25/deploying-multiple-environments-on-heroku.html Let us know how it works out for you. --Keenan On Jul 30, 2009, at 5:15 AM, Neil wrote: Has anyone played with staging environments (in addition to a production environment) on Heroku. Essentially, what I'm looking to achieve is the ability to test deploy my code to Heroku, before trying it against the production version, essentially to just run a final check that things won't explode before trying it against production. It is just a case of adding an additional remote into my git config? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Staging Environments
Hello Neil, I wrote a post that explains how I deal with a Staging + Production environment here : http://suitmymind.com/blog/2009/06/02/deploying-multiple-environments-on-heroku-while-still-hosting-code-on-github/ Hope this helps. Best, Thomas. On Jul 30, 11:15 am, Neil neil.middle...@gmail.com wrote: Has anyone played with staging environments (in addition to a production environment) on Heroku. Essentially, what I'm looking to achieve is the ability to test deploy my code to Heroku, before trying it against the production version, essentially to just run a final check that things won't explode before trying it against production. It is just a case of adding an additional remote into my git config? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Adva CMS
I am trying to get around the symlinks problem, I think heroku is not detecting to the symlinks in the public/stylesheets Thanks all for the replies Cheers Saurabh On Jul 27, 11:34 pm, Casper Fabricius casper.fabric...@gmail.com wrote: I just replied to Saurabh's similar question on the Adva mailing list. Here's my solution to the problem: I have recently deployed an Adva CMS based application to Heroku. It is running fine now, but there are complications. Besides from not supporting submodules, the big issue on Heroku is that the application are not allowed to write files on the local disk - except to the /tmp directory of the application. This means two things: 1) Migrations won't work because Adva aren't allowed to copy it's migration files to /db/migrations 2) Caching won't work because Rails aren't allowed to write it's cache files to the public folder No. 2 is easily resolved by disabling controller caching in /config/ environments/production.rb: config.action_controller.perform_caching = false # We can't do file- based caching on Heroku No. 1 can be solved in a number of ways, the easiest being that you do migrations locally and then import your local database to Heroku. This will get you up and running, but is no use once you have production data in your database. For this reason, I have removed Adva's copying of files when migrating and added a rake task that will copy all Adva's migrations from all the Adva engines to /db/migrations - permantly. Put this code in /lib/tasks/adva.rake (will both remove Adva's copying and give you the new rake task):http://pastie.org/560590 - and run rake db:copy_adva to copy Adva's migrations. I'm not 100% happy with that solution since I now have a lot of foreign migrations laying in my main app, but it works - also on the longer scale. I can run this task everytime I upgrade Adva (which also harder because it can't be a submodule) and make sure I get all the database changes. Cheers, Casper Fabriciushttp://casperfabricius.com On 27/07/2009, at 19.54, saur...@safew wrote: Hi there, I am trying to install adva cms over Heroku. I am facing this problem, saur...@laptop:~/adva/adva$ heroku rake adva:install rake aborted! Read-only file system - /disk1/home/slugs/34680_13540ed_19fb/mnt/db/ migrate/app (See full trace by running task with --trace) (in /disk1/home/slugs/34680_13540ed_19fb/mnt) adva is based on Rails engines and all the migrations lie in the engines.is this a problem because of that ? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Adva CMS
Actually because the file system is read only id does allow copying of engines and creation of symbolic links. Cheers Saurabh On Jul 30, 10:42 pm, saur...@safew saurabh.a.bha...@gmail.com wrote: I am trying to get around the symlinks problem, I think heroku is not detecting to the symlinks in the public/stylesheets Thanks all for the replies Cheers Saurabh On Jul 27, 11:34 pm, Casper Fabricius casper.fabric...@gmail.com wrote: I just replied to Saurabh's similar question on the Adva mailing list. Here's my solution to the problem: I have recently deployed an Adva CMS based application to Heroku. It is running fine now, but there are complications. Besides from not supporting submodules, the big issue on Heroku is that the application are not allowed to write files on the local disk - except to the /tmp directory of the application. This means two things: 1) Migrations won't work because Adva aren't allowed to copy it's migration files to /db/migrations 2) Caching won't work because Rails aren't allowed to write it's cache files to the public folder No. 2 is easily resolved by disabling controller caching in /config/ environments/production.rb: config.action_controller.perform_caching = false # We can't do file- based caching on Heroku No. 1 can be solved in a number of ways, the easiest being that you do migrations locally and then import your local database to Heroku. This will get you up and running, but is no use once you have production data in your database. For this reason, I have removed Adva's copying of files when migrating and added a rake task that will copy all Adva's migrations from all the Adva engines to /db/migrations - permantly. Put this code in /lib/tasks/adva.rake (will both remove Adva's copying and give you the new rake task):http://pastie.org/560590 - and run rake db:copy_adva to copy Adva's migrations. I'm not 100% happy with that solution since I now have a lot of foreign migrations laying in my main app, but it works - also on the longer scale. I can run this task everytime I upgrade Adva (which also harder because it can't be a submodule) and make sure I get all the database changes. Cheers, Casper Fabriciushttp://casperfabricius.com On 27/07/2009, at 19.54, saur...@safew wrote: Hi there, I am trying to install adva cms over Heroku. I am facing this problem, saur...@laptop:~/adva/adva$ heroku rake adva:install rake aborted! Read-only file system - /disk1/home/slugs/34680_13540ed_19fb/mnt/db/ migrate/app (See full trace by running task with --trace) (in /disk1/home/slugs/34680_13540ed_19fb/mnt) adva is based on Rails engines and all the migrations lie in the engines.is this a problem because of that ? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Heroku DB access, or configuring to use an outside DB.
Hi Alex, In theory no, you can't access the DB from outside the application. We recommend that you encapsulate the DB from your app, offering an API to manipulate it. And yes you can configure your apps to connect to any DB server you want. On ActiveRecord you can do it with the method establish_connection, documented here: http://api.rubyonrails.org/classes/ActiveRecord/Base.html#M002364 Pedro On Mon, Jul 27, 2009 at 2:54 PM, Alexa...@heaton.me wrote: Is it possible to access the heroku apps DB from outside the application? Also, can an app be configured to use an outside DB server? From what I've seen the app just gets picked up and put into the heroku PostgreSQL DB... Thanks for any info, Alex --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: s3-paperclip uploads hanging indefinitely
Hey guys, we're still taking a look at this, but having trouble to reproduce it. Nick, do you get a failwhale consistently when you run this command? Anyone else is seeing this problem consistently? On Thu, Jul 30, 2009 at 9:29 AM, Pius Uzamerepius.uzam...@gmail.com wrote: Still failing for my app as well. On Jul 29, 8:34 pm, Nick Quaranto n...@quaran.to wrote: Still getting a failwhale here with no logs :/ On Wed, Jul 29, 2009 at 8:25 PM, Trevor Turk trevort...@gmail.com wrote: On Jul 29, 4:38 pm, Nick Quaranto n...@quaran.to wrote: I'm seeing the exact same behavior when pushing gems to Gemcutter. The log just totally disappears once the failwhale comes up. Everything seems to be working fine for me now, but I'm not sure about everyone else (or if the problem has been identified)...? - Trevor --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: s3-paperclip uploads hanging indefinitely
Paperclip uploads have been working fine for me. On Thu, Jul 30, 2009 at 11:40 PM, Nick Quaranto n...@quaran.to wrote: Pedro, I'm seeing it consistently. Is there any way to look at the crashed logs? -Nick On Thu, Jul 30, 2009 at 9:25 PM, Trevor Turk trevort...@gmail.com wrote: On Jul 30, 7:48 pm, Pedro Belo pe...@heroku.com wrote: Hey guys, we're still taking a look at this, but having trouble to reproduce it. Nick, do you get a failwhale consistently when you run this command? Anyone else is seeing this problem consistently? Thanks for working on this, Pedro. I'm not seeing the problem very much (if at all) today. When it was happening, it was very consistent, though. Sorry, I know that's not much help! Hopefully, someone else on here is having a consistent problem that you might be able to work out. Thanks, - Trevor --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: s3-paperclip uploads hanging indefinitely
On Jul 30, 11:11 pm, Nick Quaranto n...@quaran.to wrote: Alright, I think I've tracked down in my codebase where the problem is. Sorry for the red herring here, folks. Still though, it would be nice to see the logs. Please do let us know if/when you figure it out! - Trevor --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: s3-paperclip uploads hanging indefinitely
Alright, I think I've tracked down in my codebase where the problem is. Sorry for the red herring here, folks. Still though, it would be nice to see the logs. On Fri, Jul 31, 2009 at 12:02 AM, Chris Conley chris.m.con...@gmail.comwrote: Paperclip uploads have been working fine for me. On Thu, Jul 30, 2009 at 11:40 PM, Nick Quaranto n...@quaran.to wrote: Pedro, I'm seeing it consistently. Is there any way to look at the crashed logs? -Nick On Thu, Jul 30, 2009 at 9:25 PM, Trevor Turk trevort...@gmail.comwrote: On Jul 30, 7:48 pm, Pedro Belo pe...@heroku.com wrote: Hey guys, we're still taking a look at this, but having trouble to reproduce it. Nick, do you get a failwhale consistently when you run this command? Anyone else is seeing this problem consistently? Thanks for working on this, Pedro. I'm not seeing the problem very much (if at all) today. When it was happening, it was very consistent, though. Sorry, I know that's not much help! Hopefully, someone else on here is having a consistent problem that you might be able to work out. Thanks, - Trevor --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: s3-paperclip uploads hanging indefinitely
Alright, so looks like I've traced down the problem but I'm still not sure of how to resolve it. Part of my application deals with a pretty huge file, it's basically a giant list of all 23,000+ gems available on Gemcutter. Compressed, this is a little less than 2 megs (with Gem.deflate, which uses Zlib) and uncompressed, it comes down to ~14 megs if you write out the file. On my own machine this turned out to be slow, but usable...on Heroku it's causing an internal system error when deserializing it using Marshal.load. To recap, the process looks something like this when pushing a new gem: 1) Download zipped index from S3 2) Unzip 3) Deserialize (boom, internal server error) 4) Add new gem into the index 5) Serialize 6) Zip 7) Push back to s3 I'm seeing a few options here...one, to try out different serialization formats to see if that helps. Another is to stick it in Memcached, but my main problem with that is I can't lose that data...so perhaps I could back it up hourly to S3. I could even make a giant binary blob in Postgres, but I doubt that would be ideal. If you've got other suggestions on how to deal with a pretty massive file like this, I'd be glad to hear it. Thanks, -Nick On Fri, Jul 31, 2009 at 12:18 AM, Trevor Turk trevort...@gmail.com wrote: On Jul 30, 11:11 pm, Nick Quaranto n...@quaran.to wrote: Alright, I think I've tracked down in my codebase where the problem is. Sorry for the red herring here, folks. Still though, it would be nice to see the logs. Please do let us know if/when you figure it out! - Trevor --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
