EJBs on Heroku -- How to?
Hello, All: I have a simple JSF project running on Apache TomEE PluME. As you might expect, I want to incorporate EJBs into my project for use in my XHTML. As you know, Heroku provides a Servlet container, aka plain Tomcat. My project is a maven project, built in Eclipse. How do I incorporate Java Beans in my project? -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Deploying J2EE app with EJBs on Heroku
Hey James, Perhaps I am too novice. I have been trying to use EJBs on Heroku with no luck. I am using PluMEE on my local host, and of course, it works. However, I've read, as you mention, that you would have to embed it somehow to get EJB functionality. How do you do this? ~Bests, - A.D On Tuesday, August 21, 2012 at 8:29:49 AM UTC-4, James Ward wrote: > > Sure! You just need a way to bring your EJB engine with you to Heroku. > I've heard that someone got embedded Glassfish working on Heroku. > That would be an option. What EJB library are you using? > > -James > > > On 08/21/2012 03:00 AM, Pankaj Bhardwaj wrote: > > Can I deploy a J2EE with EJB 2/3.1 components on Heroku. > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Heroku" group. > > > > To unsubscribe from this group, send email to > > heroku+un...@googlegroups.com > > For more options, visit this group at > > http://groups.google.com/group/heroku?hl=en_US?hl=en > -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issues getting custom binary to run on Heroku
You can try using Anvil for this: $ gem install anvil The gist below is an example for compiling bsdiff on Heroku: https://gist.github.com/ddollar/7c37dfd22528a9024a52 On Wed, Oct 9, 2013 at 8:48 PM, Robert Fletcher lobatifri...@gmail.comwrote: Hmm, okay, so I'm going to have to compile it myself I take it then... Ran into some hurdles with that, too, but I'll dig in deeper on that side of things. On Wed, Oct 9, 2013 at 5:45 PM, Daniel Farina dan...@fdr.io wrote: On Wed, Oct 9, 2013 at 5:43 PM, Robert Fletcher lobatifri...@gmail.com wrote: Yeah, that's the weird thing. When I run it on my local machine: $ ldd bin/lp_solve linux-gate.so.1 = (0xf7782000) libm.so.6 = /lib/i386-linux-gnu/libm.so.6 (0xf7733000) libdl.so.2 = /lib/i386-linux-gnu/libdl.so.2 (0xf772e000) libc.so.6 = /lib/i386-linux-gnu/libc.so.6 (0xf7584000) /lib/ld-linux.so.2 (0xf7783000) Heroku is on amd64. It does not have the supporting libraries in the i386 arch. -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Issues getting custom binary to run on Heroku
That looks like it should work from my eyeball compiler :) If you check out the comment at the bottom of the gist I pasted earlier you can see the anvil syntax for compiling from a gist. On Wed, Oct 9, 2013 at 10:34 PM, Robert Fletcher lobatifri...@gmail.comwrote: Okay, progress made. I've got it compiled locally and pushed it up. I got the following exception on Heroku: ~ $ bin/lp_solve bin/lp_solve: /lib/libc.so.6: version `GLIBC_2.14' not found (required by bin/lp_solve) I'm assuming this means I just need to compile it on Heroku instead. This is where I'm getting caught up. In order to compile, all that needs to happen is to cd into `lp_solve_5.5/lp_solve/` and execute the script `ccc`, then grab the `lp_solve` file that is generated. So I guess the script would look something like this: https://gist.github.com/mockdeep/6912134 Does that look correct? How do I go about executing that with anvil? On Wed, Oct 9, 2013 at 6:27 PM, Daniel Farina dan...@fdr.io wrote: On Oct 9, 2013 6:25 PM, Robert Fletcher lobatifri...@gmail.com wrote: The file output on Heroku was the same as local: ~ $ file bin/lp_solve bin/lp_solve: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.2.5, not stripped Great, that means 'file' can be used to spot such problems. Thanks for looking into that. -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Issues getting custom binary to run on Heroku
You'll need the link to the raw gist, which you can get by clicking the icon on your gist page. You'll probably want to drop the second ID out of the URL (the commit hash) so that the URL stays valid as you continue to make edits to the gist. On Wed, Oct 9, 2013 at 10:42 PM, Robert Fletcher lobatifri...@gmail.comwrote: Okay, running this: anvil build http://downloads.sourceforge.net/project/lpsolve/lpsolve/5.5.0.13/lp_solve_5.5.0.13_source.tar.gz-b https://gist.github.com/mockdeep/6912134 Gets me this: Launching build process... done Preparing app for compilation... done Fetching buildpack... failed Unknown buildpack type: https://gist.github.com/mockdeep/6912134 Build Error: exited 1 On Wed, Oct 9, 2013 at 7:34 PM, Robert Fletcher lobatifri...@gmail.comwrote: Okay, progress made. I've got it compiled locally and pushed it up. I got the following exception on Heroku: ~ $ bin/lp_solve bin/lp_solve: /lib/libc.so.6: version `GLIBC_2.14' not found (required by bin/lp_solve) I'm assuming this means I just need to compile it on Heroku instead. This is where I'm getting caught up. In order to compile, all that needs to happen is to cd into `lp_solve_5.5/lp_solve/` and execute the script `ccc`, then grab the `lp_solve` file that is generated. So I guess the script would look something like this: https://gist.github.com/mockdeep/6912134 Does that look correct? How do I go about executing that with anvil? On Wed, Oct 9, 2013 at 6:27 PM, Daniel Farina dan...@fdr.io wrote: On Oct 9, 2013 6:25 PM, Robert Fletcher lobatifri...@gmail.com wrote: The file output on Heroku was the same as local: ~ $ file bin/lp_solve bin/lp_solve: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.2.5, not stripped Great, that means 'file' can be used to spot such problems. Thanks for looking into that. -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Issues getting custom binary to run on Heroku
If you drop that second hash from the URL entirely it will just give you the latest one. On Wed, Oct 9, 2013 at 11:45 PM, Robert Fletcher lobatifri...@gmail.comwrote: Just realized that the gist hash changes with every change. Should be able to stumble my way through now. On Wed, Oct 9, 2013 at 8:32 PM, Robert Fletcher lobatifri...@gmail.comwrote: Okay, stuck again. It looks to me like it packages up whatever is in the starting directory, so I've updated my script to put the output there, but the archive is coming back empty. https://gist.github.com/mockdeep/6912134 On Wed, Oct 9, 2013 at 7:45 PM, David Dollar da...@heroku.com wrote: You'll need the link to the raw gist, which you can get by clicking the icon on your gist page. You'll probably want to drop the second ID out of the URL (the commit hash) so that the URL stays valid as you continue to make edits to the gist. On Wed, Oct 9, 2013 at 10:42 PM, Robert Fletcher lobatifri...@gmail.com wrote: Okay, running this: anvil build http://downloads.sourceforge.net/project/lpsolve/lpsolve/5.5.0.13/lp_solve_5.5.0.13_source.tar.gz-b https://gist.github.com/mockdeep/6912134 Gets me this: Launching build process... done Preparing app for compilation... done Fetching buildpack... failed Unknown buildpack type: https://gist.github.com/mockdeep/6912134 Build Error: exited 1 On Wed, Oct 9, 2013 at 7:34 PM, Robert Fletcher lobatifri...@gmail.com wrote: Okay, progress made. I've got it compiled locally and pushed it up. I got the following exception on Heroku: ~ $ bin/lp_solve bin/lp_solve: /lib/libc.so.6: version `GLIBC_2.14' not found (required by bin/lp_solve) I'm assuming this means I just need to compile it on Heroku instead. This is where I'm getting caught up. In order to compile, all that needs to happen is to cd into `lp_solve_5.5/lp_solve/` and execute the script `ccc`, then grab the `lp_solve` file that is generated. So I guess the script would look something like this: https://gist.github.com/mockdeep/6912134 Does that look correct? How do I go about executing that with anvil? On Wed, Oct 9, 2013 at 6:27 PM, Daniel Farina dan...@fdr.io wrote: On Oct 9, 2013 6:25 PM, Robert Fletcher lobatifri...@gmail.com wrote: The file output on Heroku was the same as local: ~ $ file bin/lp_solve bin/lp_solve: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.2.5, not stripped Great, that means 'file' can be used to spot such problems. Thanks for looking into that. -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group
Re: Deploying to github pages from Heroku
Thanks for the tips. I got into bash and ran through the steps manually. But there's still something really odd going on: ~/test $ export GIT_SSH=/app/bin/git_ssh.sh ~/test $ git push g...@github.com:misterdai/test.git master:gh-pages --force error: cannot run /app/bin/git_ssh.sh: No such file or directory fatal: unable to fork ~/test $ ls /app/bin git_ssh.sh node So it still seems like when git reads the GIT_SSH var, it can't find git_ssh.sh, even thought it's right there? Getting pretty confused. I do have a workaround of setting up another github account and using https://username:password@github etc... But preferred the idea of using a deploy key to restrict access to a single repository. Dave On Thursday, 4 April 2013 10:39:10 UTC+1, Daniel Farina wrote: On Thu, Apr 4, 2013 at 1:36 AM, David Boyer da...@yougeezer.co.ukjavascript: wrote: Didn't get chance to try it out from home but I'm sure it's probably a firewall not letting me out. If I try it on an external connection and still have issues I'll log it on the off chance ;) Unfortunately I found the issue; it has been closed with, basically, 'arrrgh'...but I'd go there and register your +1 that this sucks and it'd be nice to find some way to get around this: https://github.com/heroku/heroku/issues/407 From all the variations I've tried so far it feels like the following happens: git commands fire off fine (git init, git add, git commit) git push to github starts It spots the GIT_SSH environmental variable. Reads it correctly. Can't find the file /app/git_ssh.sh error (unable to fork) It's really weird, because that file definitely exists. It's almost seems like the git process spawns sh to run the script but it can't see the /app mount? I'm grabbing at straws if that sounds daft ;) Well, I don't think we do anything unusual there -- perhaps you should try stepping through it while running inside 'heroku run bash'? I know the 'heroku run bash' to get a shell hooked up from a Heroku container to your local TTY is old news by now, but I feel inclined to remark that it's saved me enormous grief in debugging this kind of thing: so before tearing one's hair out I'd strongly recommend somehow making 'heroku run bash' happen. Also, there is a convention of putting executable utilities into /app/bin, which in a local git repository is rendered as REPO_ROOT/bin. That shouldn't break your stuff, but I think parts of the toolchain anticipate it...for example, $PATH in an environment emitted from the Ruby build pack (not every buildpack does this or needs to): /app/bin:/app/vendor/bundle/ruby/1.9.1/bin:/usr/local/bin:/usr/bin:/bin Doing this, you can take advantage of up things in ./bin/ in your repository (translated to /app/bin on Heroku) being in $PATH from the get-go, at least for Ruby. -- fdr -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Deploying to github pages from Heroku
Didn't get chance to try it out from home but I'm sure it's probably a firewall not letting me out. If I try it on an external connection and still have issues I'll log it on the off chance ;) Just did a heroku stack and it's saying cedar. From all the variations I've tried so far it feels like the following happens: - git commands fire off fine (git init, git add, git commit) - git push to github starts - It spots the GIT_SSH environmental variable. - Reads it correctly. - Can't find the file /app/git_ssh.sh error (unable to fork) It's really weird, because that file definitely exists. It's almost seems like the git process spawns sh to run the script but it can't see the /app mount? I'm grabbing at straws if that sounds daft ;) On Wednesday, April 3, 2013 8:18:49 PM UTC+1, Daniel Farina wrote: On Wed, Apr 3, 2013 at 8:14 AM, David Boyer da...@yougeezer.co.ukjavascript: wrote: Does ssh.sh has execute permissions set correctly? Is ssh.sh sitting in a mount point with `noexec` set? (mount | grep noexec) I'll double check these when I get chance (can't seem to access bash from work), but in the meantime I tried setting GIT_SSH to just ssh. It ran it without an error, although github refused the push since it wasn't authenticated (as expected). Interesting. In my recollection, heroku run (as in heroku run bash) does not rely on HTTP to do the heavy lifting, unlike most of the toolchain. Sounds like it can't navigate a firewall. The relevant implementation is here: https://github.com/heroku/heroku/blob/master/lib/heroku/client/rendezvous.rb#L27-L45 Although I might guess this problem may have come up before, it's a new one to me...it's probably worth a filed issue on Github, although I think the odds of this changing Real Soon are not vast :( And just to double-check: are you using the Cedar stack? I read up and GIT_SSH isn't capable of taking command arguments, so most people use a .sh script. I've managed to get rid of the permissions error but it now complains about not being able to find the file (/app/git_ssh.sh) even though I test for it's existence in the app and it's definitely there (also set 0755 permissions to be sure). error: cannot run /app/git_ssh.sh: No such file or directory\nfatal: unable to fork\n Something is wrong: if executable bits didn't work in /app, then a ton of stuff would be broken. Here is a dump of the mount table from a fresh app for all involved, I think eliminating the noexec suspicion: ~ $ mount rootfs on / type rootfs (rw) /dev/loop1 on / type ext3 (ro,nosuid,nodev,noatime,nodiratime,errors=continue,data=writeback) /dev/sda2 on /app type ext3 (rw,nosuid,nodev,relatime,errors=continue,data=writeback) /dev/sda2 on /tmp type ext3 (rw,nosuid,nodev,relatime,errors=continue,data=writeback) /dev/sda2 on /var/tmp type ext3 (rw,nosuid,nodev,relatime,errors=continue,data=writeback) none on /proc type proc (rw,relatime) none on /dev type devtmpfs (rw,relatime,size=17364800k,nr_inodes=4341200,mode=755) none on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620) none on /dev/shm type tmpfs (rw,nosuid,nodev,relatime,size=5120k,nr_inodes=1024,mode=700,uid=55751,gid=55751) none on /dev/console type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620) /dev/sda2 on /etc/passwd type ext3 (rw,nosuid,nodev,relatime,errors=continue,data=writeback) /dev/sda2 on /etc/hostname type ext3 (rw,nosuid,nodev,relatime,errors=continue,data=writeback) /dev/sda2 on /etc/hosts type ext3 (rw,nosuid,nodev,relatime,errors=continue,data=writeback) /dev/sda2 on /etc/profile type ext3 (rw,nosuid,nodev,relatime,errors=continue,data=writeback) /dev/sda2 on /etc/bash.bashrc type ext3 (rw,nosuid,nodev,relatime,errors=continue,data=writeback) /dev/sda1 on /etc/resolv.conf type ext3 (rw,relatime,errors=continue,data=writeback) -- fdr -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Deploying to github pages from Heroku
Looks like the ephemeral file system won't be an issue. I've read up and it appears that it'll only lose any created files when the dyno is stopped or restarted. That works fine for me since if the process is stopped / restarted, I wouldn't want those files anyway. Plus each batch would be independent, not requiring any from a previous batch of files. Just need to work out the SSH github deploy key needs to be configured for heroku to have repository access for the push. Possibly thishttp://stackoverflow.com/questions/4565700/specify-private-ssh-key-to-use-when-executing-shell-command-with-or-without-ruby ? Dave On Tuesday, 2 April 2013 22:55:00 UTC+1, David Boyer wrote: Hi Mike, Sounds about right. It's a daily job that creates the files, doesn't take that long but there can be quite a few of them. I'm not worried about them after the push to github but wouldn't want them disappearing before it finishes. I've part of the code already running but only push two tiny test files. Plus I haven't figure out how the deploy key works. Dave On 2 Apr 2013 20:26, m...@bolser.co.uk mike%bolser.co...@gtempaccount.com wrote: Hi David It sounds like you're trying to do this: 1. Create files on a running dyno (presumably the output of a process). 2. Set github as a git remote on a running dyno. 3. Add and commit the newly created files to the dyno's local git repo. 4. Push the dyno's local git repo to github. Is that correct? There are a lot of risks with this approach due Heroku's ephemeral file system. Mike On Tuesday, April 2, 2013 4:26:46 PM UTC+1, David Boyer wrote: Hi, Hopefully this won't seem like an odd question but has anyone got any experience when it comes to pushing stuff back to github, from an actual Heroku app. I have some nodejs code which runs on Heroku, that'll create a load of .json files. From there I want to git push them to a github repository (gh-pages branch). I've got the nodejs code and git commands sorted but haven't worked out how to get the deploy key working. If anyone has done something like this before, I'd be grateful to hear how it was put together. Cheers, Dave --- David Boyer --- http://about.me/david.boyer -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to a topic in the Google Groups Heroku Community group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/heroku/J8gtGO5jPgo/unsubscribe?hl=en. To unsubscribe from this group and all its topics, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Deploying to github pages from Heroku
Hi Daniel, Thanks for the extra information on the file system, good to know I've got that right :) Stuffing the key into a config var does make sense, thanks for the suggestion. I seem to still be missing a piece of the puzzle though. I've the keys needed set as config vars, plus GIT_SSH set as a ssh.sh script which contains lines to materialise the keys as files and then make use of it got the push. But I'm running into the error: fatal: cannot exec './ssh.sh': Permission denied\nfatal: unable to fork\n I noticed that a wallmart project called mock-serverhttps://github.com/walmartlabs/mock-serverappears to have code that supports heroku and funcationality for git keys. I've tried to follow what they have with the keys as config vars and the .sh script. Dave On Wednesday, 3 April 2013 09:53:33 UTC+1, Daniel Farina wrote: Hello, On Wed, Apr 3, 2013 at 1:11 AM, David Boyer da...@yougeezer.co.ukjavascript: wrote: Looks like the ephemeral file system won't be an issue. I've read up and it appears that it'll only lose any created files when the dyno is stopped or restarted. That works fine for me since if the process is stopped / restarted, I wouldn't want those files anyway. Plus each batch would be independent, not requiring any from a previous batch of files. Your reading is correct. Many, many applications -- including quite a few Heroku components -- rely on manipulating the file system within the running container with the understanding that it will go away after the container is destroyed. You can have a shot at knowing when this is happening by treating SIGTERM in a program. The grace period is some handful of seconds. Just need to work out the SSH github deploy key needs to be configured for heroku to have repository access for the push. Possibly this? I'd suggest (although it may seem bizarre) stuffing the key into a config var if you do this, and then materializing it on the file system to aid 'git push'. -- fdr -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Deploying to github pages from Heroku
1. Does ssh.sh has execute permissions set correctly? 2. Is ssh.sh sitting in a mount point with `noexec` set? (mount | grep noexec) I'll double check these when I get chance (can't seem to access bash from work), but in the meantime I tried setting GIT_SSH to just ssh. It ran it without an error, although github refused the push since it wasn't authenticated (as expected). I read up and GIT_SSH isn't capable of taking command arguments, so most people use a .sh script. I've managed to get rid of the permissions error but it now complains about not being able to find the file (/app/git_ssh.sh) even though I test for it's existence in the app and it's definitely there (also set 0755 permissions to be sure). error: cannot run /app/git_ssh.sh: No such file or directory\nfatal: unable to fork\n Very confused at the moment :P Dave On Wednesday, April 3, 2013 12:36:53 PM UTC+1, mi...@bolser.co.uk wrote: Glad you're making progress and the file system isn't going to cause issues for you. I don't know the solution but am pretty sure that error is a UNIX permission error, so two things I'd check: 1. Does ssh.sh has execute permissions set correctly? 2. Is ssh.sh sitting in a mount point with `noexec` set? (mount | grep noexec) Does that help? On Wednesday, April 3, 2013 12:04:48 PM UTC+1, David Boyer wrote: Hi Daniel, Thanks for the extra information on the file system, good to know I've got that right :) Stuffing the key into a config var does make sense, thanks for the suggestion. I seem to still be missing a piece of the puzzle though. I've the keys needed set as config vars, plus GIT_SSH set as a ssh.sh script which contains lines to materialise the keys as files and then make use of it got the push. But I'm running into the error: fatal: cannot exec './ssh.sh': Permission denied\nfatal: unable to fork\n I noticed that a wallmart project called mock-serverhttps://github.com/walmartlabs/mock-serverappears to have code that supports heroku and funcationality for git keys. I've tried to follow what they have with the keys as config vars and the .sh script. Dave On Wednesday, 3 April 2013 09:53:33 UTC+1, Daniel Farina wrote: Hello, On Wed, Apr 3, 2013 at 1:11 AM, David Boyer da...@yougeezer.co.uk wrote: Looks like the ephemeral file system won't be an issue. I've read up and it appears that it'll only lose any created files when the dyno is stopped or restarted. That works fine for me since if the process is stopped / restarted, I wouldn't want those files anyway. Plus each batch would be independent, not requiring any from a previous batch of files. Your reading is correct. Many, many applications -- including quite a few Heroku components -- rely on manipulating the file system within the running container with the understanding that it will go away after the container is destroyed. You can have a shot at knowing when this is happening by treating SIGTERM in a program. The grace period is some handful of seconds. Just need to work out the SSH github deploy key needs to be configured for heroku to have repository access for the push. Possibly this? I'd suggest (although it may seem bizarre) stuffing the key into a config var if you do this, and then materializing it on the file system to aid 'git push'. -- fdr -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Deploying to github pages from Heroku
Hi, Hopefully this won't seem like an odd question but has anyone got any experience when it comes to pushing stuff back to github, from an actual Heroku app. I have some nodejs code which runs on Heroku, that'll create a load of .json files. From there I want to git push them to a github repository (gh-pages branch). I've got the nodejs code and git commands sorted but haven't worked out how to get the deploy key working. If anyone has done something like this before, I'd be grateful to hear how it was put together. Cheers, Dave --- David Boyer --- http://about.me/david.boyer -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Deploying to github pages from Heroku
Hi Mike, Sounds about right. It's a daily job that creates the files, doesn't take that long but there can be quite a few of them. I'm not worried about them after the push to github but wouldn't want them disappearing before it finishes. I've part of the code already running but only push two tiny test files. Plus I haven't figure out how the deploy key works. Dave On 2 Apr 2013 20:26, m...@bolser.co.uk mike%bolser.co...@gtempaccount.com wrote: Hi David It sounds like you're trying to do this: 1. Create files on a running dyno (presumably the output of a process). 2. Set github as a git remote on a running dyno. 3. Add and commit the newly created files to the dyno's local git repo. 4. Push the dyno's local git repo to github. Is that correct? There are a lot of risks with this approach due Heroku's ephemeral file system. Mike On Tuesday, April 2, 2013 4:26:46 PM UTC+1, David Boyer wrote: Hi, Hopefully this won't seem like an odd question but has anyone got any experience when it comes to pushing stuff back to github, from an actual Heroku app. I have some nodejs code which runs on Heroku, that'll create a load of .json files. From there I want to git push them to a github repository (gh-pages branch). I've got the nodejs code and git commands sorted but haven't worked out how to get the deploy key working. If anyone has done something like this before, I'd be grateful to hear how it was put together. Cheers, Dave --- David Boyer --- http://about.me/david.boyer -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to a topic in the Google Groups Heroku Community group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/heroku/J8gtGO5jPgo/unsubscribe?hl=en. To unsubscribe from this group and all its topics, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: See contents of slug?
You can use `heroku run bash` to explore around: $ heroku run bash ~ du -sh * On Wed, Feb 20, 2013 at 7:36 AM, Phil Gyford gyf...@gmail.com wrote: I have a Django project on Heroku, and its slug size has ballooned to 110MB. I've added a couple of things to my .slugignore file, which took it down from 116MB, but I thought it would be reduced by more. I can't work out why the slug's so big - is there any way to list what's in it, so I can see if I've missed anything, or if my .slugignore file isn't having the desired effect? Phil -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Heroku and Proximo
Would you mind filing a support ticket so I can dig into this with you?
On Wednesday, January 30, 2013, Xenio Ye wrote:
I need for the remote mysql db that I used to use fine in Heroku to
connect to my newly updated server that now only allows specific ip
addresses.
I setup the Proximo add-on as per the instructions and when I try to push
it to Heroku the push works but the app crashes upon entry. I get the
Heroku application crashed error page and not the 500 server error.
I noticed that in my app's settings the dyno was configured as such: *web
* bin/proximo thin -p $PORT -e $RACK_ENV -R $HEROKU_RACK start. The only
difference is that I stuck in the bin/proximo at the start as per the
instructions. Besides that, the dyno was configured with the other values.
Here is a piece from the log (I removed my ip and app's hostname for
security):
2013-01-31T01:42:04+00:00 heroku[slugc]: Slug compilation finished
2013-01-31T01:42:06+00:00 heroku[web.1]: Stopping all processes with
SIGTERM
2013-01-31T01:42:07+00:00 app[web.1]: Stopping ...
2013-01-31T01:42:09+00:00 heroku[web.1]: Process exited with status 0
2013-01-31T01:42:11+00:00 heroku[web.1]: Starting process with command
`bin/proximo thin -p 8594 -e production -R /home/heroku_rack/heroku.rustart`
2013-01-31T01:42:12+00:00 app[web.1]: Proxying traffic bound for 0.0.0.0/0via
Proximo host 23.xx.xx.xxx:1080
2013-01-31T01:42:12+00:00 app[web.1]: rm: cannot remove
`/app/vendor/dante/socks.conf': Permission denied
2013-01-31T01:42:12+00:00 app[web.1]: bin/proximo: line 35:
/app/vendor/dante/socks.conf: Permission denied
2013-01-31T01:42:12+00:00 app[web.1]: chmod: changing permissions of
`/app/vendor/dante/bin/socksify': Operation not permitted
2013-01-31T01:42:13+00:00 heroku[web.1]: Process exited with status 1
2013-01-31T01:42:13+00:00 heroku[web.1]: State changed from starting to
crashed
2013-01-31T01:42:13+00:00 heroku[web.1]: State changed from crashed to
starting
2013-01-31T01:42:18+00:00 heroku[web.1]: Starting process with command
`bin/proximo thin -p 54095 -e production -R /home/heroku_rack/heroku.rustart`
2013-01-31T01:42:18+00:00 app[web.1]: Proxying traffic bound for 0.0.0.0/0via
Proximo host 23.xx.xx.xxx:1080
2013-01-31T01:42:18+00:00 app[web.1]: rm: cannot remove
`/app/vendor/dante/socks.conf': Permission denied
2013-01-31T01:42:18+00:00 app[web.1]: bin/proximo: line 35:
/app/vendor/dante/socks.conf: Permission denied
2013-01-31T01:42:18+00:00 app[web.1]: chmod: changing permissions of
`/app/vendor/dante/bin/socksify': Operation not permitted
2013-01-31T01:42:20+00:00 heroku[web.1]: Process exited with status 1
2013-01-31T01:42:20+00:00 heroku[web.1]: State changed from starting to
crashed
2013-01-31T01:42:21+00:00 heroku[router]: at=error code=H10 desc=App
crashed method=GET path=/ host=my_ap.heroku.com fwd=71.230.121.127 dyno=
queue= wait= connect= service= status=503 bytes=
2013-01-31T01:42:21+00:00 heroku[nginx]: my_ip - - [31/Jan/2013:01:42:21
+] GET / HTTP/1.1 503 601 - Mozilla/5.0 (Windows NT 6.1; WOW64;
rv:18.0) Gecko/20100101 Firefox/18.0 my_app.heroku.com
--
--
You received this message because you are subscribed to the Google
Groups Heroku group.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com javascript:_e({}, 'cvml',
'heroku%2bunsubscr...@googlegroups.com');
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups
Heroku Community group.
To unsubscribe from this group and stop receiving emails from it, send an
email to heroku+unsubscr...@googlegroups.com javascript:_e({}, 'cvml',
'heroku%2bunsubscr...@googlegroups.com');.
For more options, visit https://groups.google.com/groups/opt_out.
--
--
You received this message because you are subscribed to the Google
Groups Heroku group.
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_US?hl=en
---
You received this message because you are subscribed to the Google Groups
Heroku Community group.
To unsubscribe from this group and stop receiving emails from it, send an email
to heroku+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Automated Toolbelt installation on Windows
If you drop a ~/.netrc in place with a username and API key you won't need to run `heroku login`. Just log in manually and grab the api.heroku.comchunk from your ~/.netrc. On Wed, Jan 16, 2013 at 6:15 PM, Matthew Ueckerman duec...@gmail.comwrote: Many thanks for your help David, those options appear to work. As a point of potential interest a window still appears during the Git install with all controls disabled. Any chance you could offer advice on automating heroku login via the toolbelt? Given the command does not accept username and password as command line arguments, I am exploring sending keys to the process via PowerShell which feels a little dirty... Kind Regards, Matthew On Tuesday, January 15, 2013 9:53:58 PM UTC+11, David Dollar wrote: The Toolbelt uses Inno Setup, which I believe has some flags for skipping things. You might try /silent or /verysilent like the Toolbelt itself does on the Ruby installer. https://github.com/heroku/**toolbelt/blob/master/dist/** resources/exe/heroku.iss#L49https://github.com/heroku/toolbelt/blob/master/dist/resources/exe/heroku.iss#L49 On Tue, Jan 15, 2013 at 5:50 AM, Matthew Ueckerman due...@gmail.comwrote: I'm hoping to script installation of the Toolbelt on windows boxes - is anyone able to offer advice? I have attempted to identify if the windows installer accepts a silent install arguments without success. Cheers, Matthew -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+un...@**googlegroups.com For more options, visit this group at http://groups.google.com/**group/heroku?hl=en_US?hl=enhttp://groups.google.com/group/heroku?hl=en_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en
Re: Automated Toolbelt installation on Windows
The Toolbelt uses Inno Setup, which I believe has some flags for skipping things. You might try /silent or /verysilent like the Toolbelt itself does on the Ruby installer. https://github.com/heroku/toolbelt/blob/master/dist/resources/exe/heroku.iss#L49 On Tue, Jan 15, 2013 at 5:50 AM, Matthew Ueckerman duec...@gmail.comwrote: I'm hoping to script installation of the Toolbelt on windows boxes - is anyone able to offer advice? I have attempted to identify if the windows installer accepts a silent install arguments without success. Cheers, Matthew -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en
Re: Heroku Labs: pipelines?
https://devcenter.heroku.com/articles/using-pipelines-to-deploy-between-applications You can find the documentation pages for Labs features using `heroku labs:info` Cheers, David On Mon, Dec 17, 2012 at 9:58 AM, Michel Pigassou dag...@gmail.com wrote: Hi. heroku labs:list gives pipelines Pipelines adds experimental support for deploying changes between applications with a shared code base. I can't find any documentation on this. There is no page on the labs help website. Does anybody have an idea? -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en
Re: Heroku potentially overcharged for scheduler on Oct. 30
I do see an increase from 0.001 to 0.563 dyno hours for October 30th compared to previous days in the month on the app that use scheduler here as well. / David On Thu, Nov 8, 2012 at 8:08 PM, Josh Cronemeyer joshuacroneme...@gmail.comwrote: My monthly billing statement is what tipped me off to the problem, but unfortunately my logs don't go back to Oct. 30. I have verified that in the past week my scheduled tasks are running in less than a second, at 10 minute intervals. The fact that 3 separate codebases across 2 different user accounts have the same spike on the same day is what made me think this wasn't something I was doing wrong. I hadn't thought to set a max execution time for my scheduled processes though, and i'm going to do that going forward. Great suggestion. On Thursday, November 8, 2012 10:53:01 AM UTC-8, Neil Middleton wrote: Have you ascertained that your scheduled tasks aren't taking longer than normal for some reason? Do you have maximum execution times set in your code to stop them running indefinitely? Neil On Thursday, November 8, 2012, Josh Cronemeyer wrote: I've got access to two separate heroku accounts (mine and my employer). And several different apps across both accounts that use the basic scheduler add on. I've noticed on my Oct. bill that there is a huge spike in usage for all these apps and accounts on Oct. 30. In all of these cases, the amount of processing done by the scheduler is not a function of traffic so any spike is unexpected. Is anyone else seeing a similar thing on their bill? I noticed that apps that just run a nightly scheduler the net effect is relatively small, but if you have scheduler tasks that run every 10 minutes the cost for that one anomalous day is pretty big. My app that schedules every 10 minutes went from an average 0.04 dynos to almost 6 dynos on Oct. 30. I've filed a support ticket on heroku, but was interested to see if other folks were seeing the same issue. -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscribe@**googlegroups.com For more options, visit this group at http://groups.google.com/**group/heroku?hl=en_US?hl=enhttp://groups.google.com/group/heroku?hl=en_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- David Hall, M. Sc., da...@dpg.se +46 (0)708-39 62 91 http://groups.google.com/group/heroku?hl=en_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en
Re: How do you manage your production secrets (API key's etc.) without using source control?
Check out https://github.com/ddollar/heroku-config I store my development environment in .env and my production environment in the Herou app. heroku-config can be used to push/pull while not overwriting existing values so it's easy to have variables with different values in development. On Mon, Oct 29, 2012 at 1:54 PM, Alex Heaton a...@heaton.me wrote: Like the title says, what approaches do you use for keeping private things out of Git? I'm currently considering Foreman and development/production.env files. I can check the former into git, keep the latter private. I'd rather not simply update the heroku config vars manually, I need to keep the secrets all in one place. -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en
Re: REXML::UndefinedNamespaceException when downloading from Amazon S3
Danorak,
Have you solved this issue? I'm running in this exact error myself on a
Amazon EC2 instance... And I was wondering if you ever happened to solve
this issue...
Op zaterdag 24 maart 2012 03:43:15 UTC+1 schreef Danorak het volgende:
I am downloading a file from Amazon S3 into the tmp directory of my
heroku dyno. I am using aws-s3 and downloading using the following
code:
def s3_get_file(filename, bucket_name)
logger.debug S3 - Streaming #{filename} from bucket
#{bucket_name} to temp
temp = Tempfile.new(s3)
File.open(temp.path, 'wb') do |file|
AWS::S3::S3Object.stream(filename, bucket_name) { |segment|
file segment
}
end
temp.path
end
This works fine on my local machine but when running on heroku I get
the following exception.
2012-03-24T02:18:12+00:00 app[web.1]:
REXML::UndefinedNamespaceException (Undefined prefix Net: found):
2012-03-24T02:18:12+00:00 app[web.1]: app/controllers/
application_controller.rb:73:in `block in s3_get_file'
2012-03-24T02:18:12+00:00 app[web.1]: app/controllers/
application_controller.rb:72:in `open'
2012-03-24T02:18:12+00:00 app[web.1]: app/controllers/
application_controller.rb:72:in `s3_get_file'
Line 73 is the S3Object.stream call.
Any ideas what is going on here.
Thanks
--
You received this message because you are subscribed to the Google
Groups Heroku group.
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_US?hl=en
Re: node db-migrate?
The Node.js buildpack puts the bin directory of your node_modules into the path. If you put db-migrate into your package.json you should be able to run it with: $ heroku run db-migrate ... On Wed, May 23, 2012 at 8:59 AM, Jeff Cole cole.j...@gmail.com wrote: Has anyone tried running node db-migrate on Heroku? You can run node in your environment with heroku run node, but db-migrate is typically run from command line using npm install -g. https://github.com/nearinfinity/node-db-migrate -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en
Re: git remote references problem
Adding a remote reference to a local working copy of a repository only impacts that clone. Subsequent clones of that repository will not have any knowledge of those actions performed. You will need to add the heroku remote again. On Thu, May 17, 2012 at 12:19 PM, psychok7 nun...@gmail.com wrote: So i have this project hosted on bitbucket and i added a git remote reference saying that origin is bitbucket after i added a heroku remote reference and everything is good. when i pushed my changes into bitbucket and latter cloned it the heroku reference was not there, only bitbucket. why is that? how do i fix this? thanks -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en
Re: Imminent Death of the Heroku Google Group
For the record, this is the way I keep abreast of all the heroku things. Doing away with it is sheer madness. The sort of bad decisionss I saw coming the sad day Salesforce came into the picture. I warned them... This is going to change you no matter what they say. And it has. David Sent from my iPad On Apr 25, 2012, at 12:17 PM, Neil Middleton neil.middle...@gmail.com wrote: In order to play devils advocate here (I'm not saying if I'm on one side of the fence or the other): 1) The group isn't a great archive for problems as the specific problems tend to be buried in email threads. 2) For a lot of the problems on here, support.heroku.com is probably the best place to go. 3) The StackOverflow tag on SO is remarkably active: http://stackoverflow.com/questions/tagged/heroku 3) Google have already done this with some success: https://groups.google.com/forum/?fromgroups#!topic/google-appengine/Z6XN_64cA7w Neil On Wednesday, 25 April 2012 at 18:12, Alex Chaffee wrote: fIn the latest Heroku Newsletter[1], it says this group will be killed at the end of April, and suggests instead to go to support.heroku.com (which is private) or stackoverflow.com. While SO is awesome, is it really an adequate replacement for this group? I've found that SO is a great complement to mailing lists but doesn't allow for the same kind of deep discussion and community building. Worse, it requires active attention rather than arriving in one's inbox, so the people who are most likely to have an answer to a question are the least likely to hear it -- since they're not having any problems. Why uproot a productive community (this mailing list) and hope that it migrates to a new place with a radically different interaction model? [1] http://lists.heroku.com/t/ViewEmail/r/6DFC781E555FD71E/CEC5941F8B0A6F4BC5EC08CADFFC107B -- Alex Chaffee - a...@stinky.com http://alexchaffee.com http://twitter.com/alexch -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en
Re: Imminent Death of the Heroku Google Group
Is there any way to just preserve the current google group and it's members, but transfer ownership and official status? On Wed, Apr 25, 2012 at 14:01, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote: I'm happy to create our own google group for discussion/QA if I can get 4 others to agree this is warranted (me being one, I guess Justin you are a second?) On Wed, Apr 25, 2012 at 12:39 PM, Justin Houk jsh...@gmail.com wrote: I agree with Jeff. FWIW, I find the SO community to be micromanaging, pedantic, and downright annoying to try to interact with. Which, I guess, is why I'm here and not there. On the other hand, I guess it shows how little Heroku takes this list seriously that we hear about this announcement from the newsletter and not here? The community does lose some value without a certain level of interest and support from Heroku proper. --Justin On Wed, Apr 25, 2012 at 1:33 PM, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote: I agree. Stack Overflow is completely different from a mailing list. Here discussion is encouraged. There, it is penalized and can be edited or deleted. I suppose we can create our own google group? jeff On Wed, Apr 25, 2012 at 12:28 PM, David Whatley nsxda...@gmail.com wrote: For the record, this is the way I keep abreast of all the heroku things. Doing away with it is sheer madness. The sort of bad decisionss I saw coming the sad day Salesforce came into the picture. I warned them... This is going to change you no matter what they say. And it has. David Sent from my iPad On Apr 25, 2012, at 12:17 PM, Neil Middleton neil.middle...@gmail.com wrote: In order to play devils advocate here (I'm not saying if I'm on one side of the fence or the other): 1) The group isn't a great archive for problems as the specific problems tend to be buried in email threads. 2) For a lot of the problems on here, support.heroku.com is probably the best place to go. 3) The StackOverflow tag on SO is remarkably active: http://stackoverflow.com/questions/tagged/heroku 3) Google have already done this with some success: https://groups.google.com/forum/?fromgroups#!topic/google-appengine/Z6XN_64cA7w Neil On Wednesday, 25 April 2012 at 18:12, Alex Chaffee wrote: fIn the latest Heroku Newsletter[1], it says this group will be killed at the end of April, and suggests instead to go to support.heroku.com (which is private) or stackoverflow.com. While SO is awesome, is it really an adequate replacement for this group? I've found that SO is a great complement to mailing lists but doesn't allow for the same kind of deep discussion and community building. Worse, it requires active attention rather than arriving in one's inbox, so the people who are most likely to have an answer to a question are the least likely to hear it -- since they're not having any problems. Why uproot a productive community (this mailing list) and hope that it migrates to a new place with a radically different interaction model? [1] http://lists.heroku.com/t/ViewEmail/r/6DFC781E555FD71E/CEC5941F8B0A6F4BC5EC08CADFFC107B -- Alex Chaffee - a...@stinky.com http://alexchaffee.com http://twitter.com/alexch -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- Justin Houk Co-Founder, 10x10 Room http://www.linkedin.com/profile/view?id=6055184 http://10x10room.com http://playconclave.com -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl
Re: git tagging heroku releases
Well that's embarrassing. Looks like when I found the need for this, I had several issues in my repo/app running in concert. This made me think that when the hashes listed in `heroku releases` differed from both `git log heroku/master` and `git log master` that I was perhaps seeing an alternate hash generated by the slug compilation. Don't mind me I guess, at least I only spent a day or so on this script, although I think that perhaps then converting the idea into a heroku cli plugin that just took the versions in releases and created the tags as scraped could still have value? Thoughts? On Mon, Apr 23, 2012 at 09:10, Neil Middleton neil.middle...@gmail.com wrote: You've lost me a little here. `heroku releases` gives you all the deployed git versions and other changes. For instance: Rel Change By When -- -- -- v214 Deploy 5f3f619 neil.middle...@gmail.com 2012-04-18 17:28:41 +0100 v213 Deploy b71ce95 neil.middle...@gmail.com 2012-04-12 15:04:45 +0100 v212 Deploy d27f151 neil.middle...@gmail.com 2012-04-12 13:20:53 +0100 v211 Deploy 6b81eef neil.middle...@gmail.com 2012-04-12 12:59:28 +0100 v210 Config add FACEBOOK_APP_SECR.. neil.middle...@gmail.com 2012-04-12 12:56:11 +0100 v209 Deploy 2f54f24 neil.middle...@gmail.com 2012-04-12 11:43:28 +0100 v208 Deploy 19b486d neil.middle...@gmail.com 2012-04-12 11:36:34 +0100 v207 Deploy efdd6ef neil.middle...@gmail.com 2012-04-12 11:22:40 +0100 Each of those deploy hashes under 'Change' match commits in my Git repo on Github (and everywhere else). By rolling back to say v208 I know I'm going to end up with 19b486d, or am I missing something obvious here? N Neil On Monday, 23 April 2012 at 02:08, david ignacio wrote: Hey- So one thing that has got me about heroku is that there isn't necessarily a good link between the git repo and heroku releases. By this I mean that it isn't entirely obvious what is deployed and running at the moment. There are two current tools we have: * the heroku remote in the git repo * heroku releases This gives me the current release and what is working right now, but nothing more. If I deploy something broken, there isn't a clear way to find what I'd be rolling back to. The hashes displayed in heroku releases are of the compiled slugs. I have gone through a few back and forths as to what would be a good way to fill this gap. I realized that you'd really need two different scripts since releases are created in multiple places, one in the heroku cli and one in git. The config/addon changes trigger a new release to be created, but I think that those changes are well documented in heroku releases. It was the git-push triggered releases that I wanted to track. This led me to write: https://github.com/deignacio/gthr What I'm wondering from you guys is: * is there any other way in heroku that I can get the information I'm scraping so that I'm not just scraping stderr of git push? * am I thinking about this problem in the right way that this solution seems okay? * are there any other precedents that I didn't find in my sanity check google search? * assuming that the previous questions are positive, can anyone think of any other things they'd want? Thanks for your input Dave -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en -- You received this message because you are subscribed to the Google Groups Heroku group. 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_US?hl=en
worker.js example
okay a total noob here. I have a webserver running on nodejs. It itnt finished yet but at the moment I would like to add a worker process to update the database, send out http requests etc. Is there documentation/example available how to do this in nodejs/javascript? I cant find any examples please help -- 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: Can't get Building a Database-Backed Clojure Web Application to work
I was able to solve the problem.
I noticed that with-connection doesn't take a
stringhttp://clojure.github.com/java.jdbc/#clojure.java.jdbc/with-connection.
Following the Clojure Programming/Examples/JDBC
Exampleshttp://en.wikibooks.org/wiki/Clojure_Programming/Examples/JDBC_Examples#PostgreSQL,
I replaced:
(sql/with-connection (System/getenv DATABASE_URL)
(sql/create-table :testing [:data :text]))
with:
(sql/with-connection {:classname org.postgresql.Driver
:subprotocol postgresql
:subname //localhost:5432/shouter}
(sql/create-table :testing [:data :text]))
and now it works.
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To view this discussion on the web visit
https://groups.google.com/d/msg/heroku/-/b5QrL6taS6oJ.
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.
Can't get Building a Database-Backed Clojure Web Application to work
Hi, I'm new to Heroku and I'm trying to follow the directions here: https://devcenter.heroku.com/articles/clojure-web-application I'm stuck at this point: user= (sql/with-connection (System/getenv DATABASE_URL) (sql/create-table :testing [:data :text])) I get the following error message: org.postgresql.util.PSQLException: Something unusual has occured to cause the driver to fail. Please report this exception. (NO_SOURCE_FILE:0) I found someone else complaining about the same problem here: http://stackoverflow.com/questions/10089969/leiningen-clojure-is-acting-weird-when-i-try-to-connect-to-postgresql-database Based on that page, I tried the following: export DATABASE_URL=jdbc:postgresql:shouter Now I get a different error message: java.lang.NullPointerException (NO_SOURCE_FILE:0) I've tried this on Lion, Snow Leopard, and Ubuntu, all with the same result. Can someone unstick me? Thanks, David -- You received this message because you are subscribed to the Google Groups Heroku group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/HKgTGPOk9zEJ. 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: Gem Manifest deprecation
The .gems solution was non-deterministic in the normal use case. If someone specified sinatra in their .gems file, they would often end up with a completely different version in production than they were using in development. Sure you could specify an exact version of every gem in your .gems file, but few people did and it's a huge pain to maintain. Bundler splits dependency declaration into what the developer cares about (Gemfile) and an exact specification of each version that should be installed (Gemfile.lock). This maintains dev/prod parity without the maintenance overhead of curating a specific list of gem versions yourself. It also has the advantage of not being specific to Heroku. Cheers, David On Fri, Apr 6, 2012 at 3:06 PM, Michel Martens sove...@gmail.com wrote: Hey Keenan, thanks for replying :-) On Fri, Apr 6, 2012 at 2:48 PM, Keenan Brock kee...@thebrocks.net wrote: Hello Michel, I think this is a great example of heroku being ahead of their time. When .gems was introduced, there wasn't a way to specify gem dependencies in a ruby project. Back then, dependencies were a mess - heroku even had to run their own custom fork of rails. There were other means to define dependencies (for instance, Bundler was initially inspired by this library: https://github.com/djanowski/dependencies). I think Heroku's solution was very elegant, and continues to be. Now, the Gemfile is a common and standard way of specifying dependencies. There is a whole community adding features and documenting implications and nuances. It is true that there wasn't a standard before Bundler. What I think, and I guess most people will disagree with me, is that even though Bundler was imposed upon every Rails developer, it doesn't mean it is the standard for the rest of the Ruby community. Sure, I could go along with the masses and adopt Bundler, but it feels wrong because it is way out of my workflow. Bundler is a very big dependency, I don't like the idea of it being imposed on me. Just for reference, this is the tool we use for managing dependencies at the company I work for: https://github.com/twpil/dep It makes sense for heroku to drop their proprietary tool and go with the common one, no? That way they can dedicate their resources on other great stuff to give to us. It may makes sense for Heroku, I really don't know if they will lose clients by dropping support for the .gems manifest. I don't have the power to avoid that from happening, sadly. If it were up to me, I would stick to the minimalism of the .gems manifest and also support Gemfile, given that most of the applications deployed to Heroku are built with Rails. Thanks! -- 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. -- 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.
Heroku Scheduler - Process doesn't complete (Cedar)
Hi,
I'm running a node process on Cedar as a scheduled task. It runs fine,
except the process never changes to complete. If I run it every 10 mins,
then pretty quickly I have several run.X processes that are continuing to
run even though there is nothing to process, and this is not good for my
bill.
My code is async and does execute a callback and so far the only way I've
found to get the process to finish is to add { throw new Error('done'); }
when my last callback completes.
Perhaps I am missing something extremely obvious?
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To view this discussion on the web visit
https://groups.google.com/d/msg/heroku/-/CfdnMQHR0SsJ.
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: How to save user responses on the server
Have you thought about persisting your responses to a database? All apps have a shared database, and there are many addons that provide cloud based sql/nosql databases. There are also many help docs about setting these services up. On Fri, Mar 23, 2012 at 14:22, Anthony Fontanilla epicmomentoftr...@gmail.com wrote: I want to make a Facebook app that's like a questionnaire. After the user answers the questions, it will display statistics about how everyone who took the questionnaire answered. It will show what % of people answered yes and what % of people answered no. In order to do this, I need to save the user's answers somewhere. I heard that I can't save it to the Heroku server? How do I save user's responses so that they can be retrieved later to do these calculations? -- 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. -- 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: I need the dumbed down version of how to do this
There's a bit of a learning curve here, unfortunately. You'll have to dive into git: http://help.github.com/ Also, check out my friend Jared's company http://www.trybloc.com/ -- they're trying to produce training for this stuff, maybe you'll find that helpful. D On Mon, Mar 12, 2012 at 10:02 AM, Jodi Cocagne jodigle...@gmail.com wrote: Hello, I have created an APP and have made it to the Getting started with my APP section. I can not figure out this 1) Fetch Your App’s Sourcecode We’ll start by grabbing a copy of your app’s sourcecode using Git. You’ll need to know the name of your app for this: Heroku gave it a randomly-generated haiku name to start with, so look in the URL to find your app name. For example, if your URL is https://furious-robot-218.herokuapp.com, then your app name is furious-robot-218. Paste this into a git clone command. How do I FETCH my App's source code? I just want to figure out how to use this whole graph api thing. There is not anything on this yet for dummies. I am not a web developer. Any type of information that anyone can put into layman's terms regarding this application and a simple how to would be awesome. To bad it was so easy to do up until it came to editing this. Thanks for any help Jodi -- 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. -- 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: node version bump
OK, followed the directions. Relevant package.json section:
, engines: {
node: 0.6.x
, npm: =1.0.0
}
When I git push to heroku (via Jenkins), I get
Pushing HEAD to branch master at repo staging
ERROR: Failed to push branch master to staging: Error performing
command: git push g...@heroku.com:wishery-services-staging.git
HEAD:master
Command git push g...@heroku.com:wishery-services-staging.git
HEAD:master returned status code 1:
- Heroku receiving push
- Node.js app detected
- Resolving engine versions
Using Node.js version: 0.6.10
! Heroku push rejected, failed to compile Node.js app
I noticed the lines above didn't include anything about npm, so I changed
my npm dependency to an explicit version, rather than a conditional:
, engines: {
node: 0.6.x
, npm: 1.1.1
}
Success.
Heroku, please update your docs or tell me what I did wrong -- I think I
followed the labs docs on the feature verbatim?
DA
On Mon, Feb 20, 2012 at 6:17 PM, David Dollar da...@heroku.com wrote:
Labs itself is fairly new and hasn't yet been widely publicized.
As far as release timeline, we're in the process of an incremental
rollout. The nodejs-versions feature is on by default for all new apps and
you can flag any existing apps by hand. We'll be rolling out the feature to
existing apps slowly over the next few weeks.
Cheers,
David
On Mon, Feb 20, 2012 at 9:13 PM, David Albrecht da...@wishery.com wrote:
That's fantastic. Is there any schedule to get this on a
production/release track? I've been using Heroku over 1.5 years and had
never even heard of Labs prior to today.
DA
On Mon, Feb 20, 2012 at 6:08 PM, David Dollar da...@heroku.com wrote:
Hi David,
Last week we added the ability to select your Node.js version to Heroku
Labs, our breeding ground for experimental new features. Check it out at:
http://devcenter.heroku.com/articles/labs-nodejs-versions
On Mon, Feb 20, 2012 at 8:56 PM, David Albrecht da...@wishery.comwrote:
Is there any plan to upgrade the version of node offered on Cedar past
0.4.7? Node's commit log shows this version became stable on April 22nd
2011, which is fast approaching a year ago.
Thanks,
DA
--
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.
--
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.
--
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.
--
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.
--
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.
node version bump
Is there any plan to upgrade the version of node offered on Cedar past 0.4.7? Node's commit log shows this version became stable on April 22nd 2011, which is fast approaching a year ago. Thanks, DA -- 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: node version bump
That's fantastic. Is there any schedule to get this on a production/release track? I've been using Heroku over 1.5 years and had never even heard of Labs prior to today. DA On Mon, Feb 20, 2012 at 6:08 PM, David Dollar da...@heroku.com wrote: Hi David, Last week we added the ability to select your Node.js version to Heroku Labs, our breeding ground for experimental new features. Check it out at: http://devcenter.heroku.com/articles/labs-nodejs-versions On Mon, Feb 20, 2012 at 8:56 PM, David Albrecht da...@wishery.com wrote: Is there any plan to upgrade the version of node offered on Cedar past 0.4.7? Node's commit log shows this version became stable on April 22nd 2011, which is fast approaching a year ago. Thanks, DA -- 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. -- 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. -- 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: node version bump
Labs itself is fairly new and hasn't yet been widely publicized. As far as release timeline, we're in the process of an incremental rollout. The nodejs-versions feature is on by default for all new apps and you can flag any existing apps by hand. We'll be rolling out the feature to existing apps slowly over the next few weeks. Cheers, David On Mon, Feb 20, 2012 at 9:13 PM, David Albrecht da...@wishery.com wrote: That's fantastic. Is there any schedule to get this on a production/release track? I've been using Heroku over 1.5 years and had never even heard of Labs prior to today. DA On Mon, Feb 20, 2012 at 6:08 PM, David Dollar da...@heroku.com wrote: Hi David, Last week we added the ability to select your Node.js version to Heroku Labs, our breeding ground for experimental new features. Check it out at: http://devcenter.heroku.com/articles/labs-nodejs-versions On Mon, Feb 20, 2012 at 8:56 PM, David Albrecht da...@wishery.comwrote: Is there any plan to upgrade the version of node offered on Cedar past 0.4.7? Node's commit log shows this version became stable on April 22nd 2011, which is fast approaching a year ago. Thanks, DA -- 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. -- 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. -- 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. -- 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: rails 3.2 on cedar only?!
Currently, yes, Rails 3.2 only runs on Cedar. We are looking into the bamboo problems and hope to have a fix soon. On Wednesday, January 25, 2012 at 10:34 AM, vierundsech...@googlemail.com wrote: I just tried to run rails 3.2 and ran into all sorts of weird errors (mostly gem-problems). I'm currently running on bamboo-mri-1.9.2 - does 3.2 only run on cedar?! -- 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 (mailto:heroku@googlegroups.com). To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com (mailto:heroku+unsubscr...@googlegroups.com). For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- 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.
Heroku Labs git_submodules private repos
I got this to work: http://devcenter.heroku.com/articles/labs-git-submodules But there is an issue in that my submodule is private. The particular submodule I'd like to include contains global variables and authentication parameters that I want to share across several different apps that together form our service. There's no way I can make this public. So how can I allow heroku to access my private repo, or rather provide my credentials during dependency installation to allow this to work? -- You received this message because you are subscribed to the Google Groups Heroku group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/nIWbZvcPWIMJ. 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: rack-time not cutting off long postgres queries
Ah, we ran into this very issue :)
rack_timeout uses SystemTimer, and it turns out that the database call
isn't interrupted or aborted by the trapped signal. That's why the
timeout doesn't fire until the call returns:
Benchmark.realtime { SystemTimer.timeout_after(5) {
AR::Base.connection.select_value(SELECT pg_sleep(10)) } rescue nil }
= 10.0038049221039
We uncovered the statement_timeout setting in Postgres, which will
kill queries that exceed the setting. Doco here:
http://www.postgresql.org/docs/9.1/static/runtime-config-client.html#GUC-STATEMENT-TIMEOUT
AR::Base.connection.execute(SET statement_timeout TO '4s')
= 4s
Benchmark.realtime { SystemTimer.timeout_after(5) {
AR::Base.connection.select_value(SELECT pg_sleep(10)) } rescue nil }
= 4.00161099433899
With that in hand, we set statement_timeout to one second less than
the request timeout, and handled the exception that's raised by the
timed out query (an AR::StatementInvalid in ActiveRecord's case) in a
piece of middleware.
A few gotchas:
1. We set the statement_timeout in a Rails initializer
(config/initializers/something.rb), but we had to add some additional
chrome because we did not want the timeout enabled for background
jobs, rake tasks, or the development/test environments. Web requests
only.
2. AR::StatementInvalid isn't particular to timed-out queries, so we
had to do some substring matching on the exception's message in order
to filter it properly in middleware. Specifically, we were looking for
canceling statement due to statement timeout (when the
statement_timeout is exceeded and Pg kills it) and Timeout::Error
(when SystemTimer's SIGALRM is trapped during the database call).
3. If you're using Rails and the query times out in a view, then ugh,
the exception is swallowed into a generic ActionView::Template::Error.
The message, however, remains original.
Best of luck!
Dave
On Wed, Jan 4, 2012 at 9:02 PM, Peter van Hardenberg p...@heroku.com wrote:
Hi Sorens,
sorry I didn't get back to you earlier. PostgreSQL only checks for
connection interruption between statements -- this is an unfortunate design
decision and perhaps something that could be better emphasized with the
project as a serious production problem. (In fact, I may go start a thread
on this issue right now!)
When this occurs, you could use pg_cancel_backend(query pid) IF you were a
superuser. Unfortunately, in order to provide a stable service we can't give
that out. Because of that, we've worked with the project to upstream a fix,
which should arrive with 9.2, and we're currently looking at backporting
that patch to all new databases as soon as it stabilizes.
Other than that, I'm afraid there's not much you can do currently except try
not to issue single statements which cause big problems. Really sorry I
don't have better news to bring you. It's an issue we're obviously tracking
closely and working on a solution for but there isn't one available yet.
Best,
Peter
Heroku Postgres
On Fri, Dec 16, 2011 at 10:12 AM, sorens skor...@gmail.com wrote:
Our web app is running on heroku with a dedicated postgres DB. We have
a long query that we're fixing(separate issue), but we noticed that
the rack-timeout did not cut the request off at 15 seconds as
expected. I posted a question about it on StackOverflow.
http://stackoverflow.com/questions/8512540/a-slow-postgres-query-on-heroku-is-not-being-interrupted-by-rack-timeout
Does anyone have insight into how I can make rack-timeout cut off this
request? While we're tracking down the query issue, having the query
take out the service is causing problems.
Thanks,
Steve
--
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.
--
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.
--
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: fatal: Not a git repository (or any of the parent directories): .git
A similar error, but different root cause, I think...I'm on Heroku
Cedar with node.js, and NPM is failing to install my git dependencies:
- Heroku receiving push
- Node.js app detected
- Fetching Node.js binaries
- Vendoring node 0.4.7
- Installing dependencies with npm 1.0.94
npm ERR! git checkout oauth-prerfc fatal: Not a git repository:
'.'
npm ERR! Error: `git checkout oauth-prerfc` failed with 128
npm ERR! at ChildProcess.anonymous (/tmp/node-npm-A6yb/
lib/utils/exec.js:49:20)
npm ERR! at ChildProcess.emit (events.js:67:17)
npm ERR! at ChildProcess.onexit (child_process.js:192:12)
npm ERR! Report this *entire* log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR! n...@googlegroups.com
For comparison, when running npm locally, I get:
npm verb mkdir done: /tmp/npm-1322678417970 755
npm verb git clone git://github.com/eldavido/connect-auth.git
Initialized empty Git repository in /tmp/
npm-1322678417970/1322678417970-0.53214391018264/.git/
npm verb git checkout oauth-prerfc Branch oauth-prerfc set up to track
remote branch oauth-prerfc from origin.
npm verb git checkout oauth-prerfc
npm verb git checkout oauth-prerfc Switched to a new branch 'oauth-
prerfc'
npm verb caching /tmp/npm-1322678417970/1322678417970-0.53214391018264/
package.json
npm verb loadDefaults connect-auth@0.4.1
Is it possible for NPM to create a new directory in /tmp on the cedar
stack? If not, this would cause this to fail, but I'm not sure that's
the root cause.
Thanks,
DA
On Nov 30, 4:00 am, DAZ daz4...@gmail.com wrote:
Cheers Adam,
It was this line:
sha1, date = `git log HEAD~1..HEAD --pretty=format:%h^
%ci`.strip.split('^')
I've been using that it to create etag and last modified headers for
caching. Konstantin Haase recommends it and uses it in his apps
(https://github.com/rkh/rkh.im/blob/master/blog.rb).
I'll have to have another look at how to generate these instead.
cheers,
DAZ
On Nov 30, 6:36 am, Adam Wiggins a...@heroku.com wrote:
Slugs don't have git repositories in them. Something in your app is trying
to do a Git operation when it boots -- you should figure out what it is and
remove it.
You can duplicate it locally by moving your .git directory to .git-bak, and
then try running your app.
Adam
--
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: cedar stack: git requirements failing?
Downloading/unpacking idios-dev from git+https://github.com/
eldarion/idios.git@c6f670fe2778d7739efde0f69d18dbdbbb04db2c (from -r
requirements.txt (line 21))
Cloninghttps://github.com/eldarion/idios.git(to
c6f670fe2778d7739efde0f69d18dbdbbb04db2c) to ./build/idios-dev
Command /usr/bin/git tag -l had error code 128
Complete output from command /usr/bin/git rev-parse fatal:
Not a git repository: '.':
fatal: Not a git repository: '.'
Did you ever resolve this? I think I'm getting something similar when
using NPM (on node.js, Cedar) and it's because NPM can't create a git
repo in a subdirectory of /tmp -- it works locally, but fails on
Heroku.
My package.json:
{
name: wishery-services
, version: 0.0.1
, private: true
, dependencies: {
express: 2.2.0
, mongodb: 0.9.6-20
, ejs: 0.4.3
, pg: 0.6.3
, rbytes: 0.0.2
, connect-auth: git://github.com/eldavido/connect-auth.git#oauth-
prerfc
}
}
Error:
- Heroku receiving push
- Node.js app detected
- Fetching Node.js binaries
- Vendoring node 0.4.7
- Installing dependencies with npm 1.0.94
npm ERR! git checkout oauth-prerfc fatal: Not a git repository:
'.'
npm ERR! Error: `git checkout oauth-prerfc` failed with 128
npm ERR! at ChildProcess.anonymous (/tmp/node-npm-A6yb/
lib/utils/exec.js:49:20)
npm ERR! at ChildProcess.emit (events.js:67:17)
npm ERR! at ChildProcess.onexit (child_process.js:192:12)
npm ERR! Report this *entire* log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR! n...@googlegroups.com
For context, when I do npm install --verbose locally, I get:
npm verb git clone git://github.com/eldavido/connect-auth.git
Initialized empty Git repository in /tmp/
npm-1322678417970/1322678417970-0.53214391018264/.git/
npm verb git checkout oauth-prerfc Branch oauth-prerfc set up to track
remote branch oauth-prerfc from origin.
npm verb git checkout oauth-prerfc
npm verb git checkout oauth-prerfc Switched to a new branch 'oauth-
prerfc'
npm verb caching /tmp/npm-1322678417970/1322678417970-0.53214391018264/
package.json
npm verb loadDefaults connect-auth@0.4.1
--
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: basic question about dyno RAM
Out of curiosity, why do you care about the amount of RAM available on a dyno? I generally run either delayed job workers or web processes on Heroku's dyno grid; I don't have any general-purpose compute loads that require gigabytes of RAM yet, but if I did, I'd probably look for either a hosting provider that specialized in running the type of process that needs so much memory (e.g. a database), or start thinking about buying compute power lower down the stack (EC2/colo). Maybe your needs are different than mine, though? On Fri, Nov 25, 2011 at 11:16 AM, anentropic bluesk...@gmail.com wrote: I have some (Django) sites on an 80MB WebFaction hosting account. I see that a single dyno on Heroku gets 512MB... for free! (albeit I'll pay for db and S3 storage etc...) The WebFaction pricing pages says: This is the actual memory available to your long-running processes (for instance, your Rails or Django processes). Unlike in a VPS, the memory used by the operating system, the main web server and the database servers doesn't count towards your memory usage In the WF process list I see Apache httpd workers for my Django/wsgi app. Is this broadly comparable to Heroku... i.e. the whole 512MB is available to user processes? -- 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. -- 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: Multiple Apps, Multiple Clients. One Account?
It's per-app, we have four apps, three of which use only a single dyno and we don't get charged for the three that only use one dyno. OTOH, Heroku will idle your single-dyno (free) app if it doesn't get any traffic for a while, which can be irritating as there's a noticeably delay when the dyno grid unidles it. On Fri, Nov 25, 2011 at 12:55 PM, anentropic bluesk...@gmail.com wrote: just to tack my own question on the end here... if I have several apps under one account, does each app benefit from the '1 free dyno per month' (750 hrs) pricing, or just the account overall? I found a place in the FAQs where it says Each application receives 750 free dyno hours per month but would like to confirm that it really is per app. thanks! On Nov 21, 6:32 am, Mike Abner mike.ab...@gmail.com wrote: You'd have one account with N apps on the account. Each app is a set of resources (dynos, workers, dbs, add-ons). So you'd be able to scale them independently from each other. You set the number of dynos and workers you need for each app. Heroku does not manage your dyno needs for you. You can use the heroku gem to manage the scaling yourself or you can use a 3rd party service like heroscale to do it for you. So if it were me I'd have the following: Account Mike App A App B App C App D Then you would monitor those and scale them individually. If your traffic is spread throughout the day than 2-3 dynos should be all you need for clients A and B. client C you'll have to experiment with as well as D. I think your costs are going to come from the DB. If you need a dedicated DB for each app then that's $1000 a month but performance will be nice. If you could combine your databases then you can save some money there. Mike On Nov 18, 2011, at 10:26 AM, Joe K joe.kue...@gmail.com wrote: I searched and found similar questions to mine, so I can probably infer the answer, but I want to make sure before I leap. Let's pretend I have 4 clients with pretty elaborate Rails or Django apps. They are currently on a traditional shared server that we host, along with about 150 small sites, and the performance of these 4 clients sites is unacceptable. So, for the sake of performance and our sanity we are considering moving these 4 apps to Heroku (another option we are considering is spinning up our own EC2 instances). Now let's pretend I want, oh, 3 web dynos for each app. And each app will have it's own database. Would I have a single account, where I set up 12 dynos, and a single dedicated database that is shared among all apps? Or would I set up 4 accounts, each with its 3 dynos and a database? From what I have read, I believe it would be the case that I would set up a single account with however many dynos I think I would need and it would be shared among as many apps as I wish to deploy, and the first dyno for each app would be free (not just the first dyno for the account). Is this correct? Let's get a little less abstract for a moment... Client A - Small-ish database (about 40 tables, none of them with more than 100 or so records), a fair amount of static content, and perhaps 1000 hits a day. Client B - Almost identical to Client A Client C - Medium-sized database (about 20 tables with about 1500 records each, fairly high traffic), lots of static content (thousands of images) Client D - Very dynamic, mostly user-generated content, lots of static content (uploaded images, PDFs, etc.) Given this type of configuration, I believe I read that I can basically give Heroku a dyno budget, it it will use what it needs to for each client, as it needs to, though I can also tell it how I would prefer those dynos is distributed. Is that correct? Finally, it is my understanding that if dynos aren't being used, they are killed off, so we won't get charged for 12 dynos just because we had a 12 dyno budget. Heroku will use what is needed when needed, so costs could be less than budgeted. Correct? Sorry for all of the questions. The boss-man is asking me to make a pretty important decision here, so I want to make sure I have the facts straight. Thanks in advance for your help. Joe K. -- 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 athttp:// groups.google.com/group/heroku?hl=en. -- 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
Setting collation on Postgres databases
I am trying to find a way to get the Postgres database to understand our Swedish umlauts correctly. I have found two [1] unanswered questions on the topic of collation from other Scandinavians last year but no solution. Is there a way to set collation on database level on Postgres under Heroku? The specific problem I have is that ILIKE handles characters such as ä and Ä as two different characters. 1. Heroku DB and sorting, http://groups.google.com/group/heroku/browse_frm/thread/fd206f57f41fb36d/414f415f3947c442 postgresql and sort order collation, http://groups.google.com/group/heroku/browse_thread/thread/2a270c4443e92b40/b7ca452a2a0fc583 -- 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: New Relic causing crash on deploy
Would you mind filing a ticket about this at http://support.heroku.com so we can get to the bottom of it? Thanks, David -- You received this message because you are subscribed to the Google Groups Heroku group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/FrTT7HwO0XwJ. 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.
Worker won't run Delayed::Jobs on Sinatra app
I'm trying to get delayed jobs to work on a Sinatra app. I have been looking at https://github.com/bmizerany/sinatra-dj but I am currently using delayed-job in gem form and not in a vendor directory. Issuing 'heroku rake jobs:work' works as expected. However, when using the heroku worker I can't really get it to work. 2011-09-07T18:19:22+00:00 heroku[worker.1]: Starting process with command `rake jobs:work` 2011-09-07T18:19:22+00:00 heroku[worker.1]: State changed from starting to up 2011-09-07T18:19:23+00:00 app[worker.1]: D, [2011-09-07T11:19:23.240558 #1] DEBUG -- : NoMethodError: undefined method `values' for #PGresult:0x7fbafe16e480: SHOW client_min_messages 2011-09-07T18:19:23+00:00 app[worker.1]: D, [2011-09-07T11:19:23.242964 #1] DEBUG -- : PGError: ERROR: invalid value for parameter client_min_messages: 2011-09-07T18:19:23+00:00 app[worker.1]: : SET client_min_messages TO '' 2011-09-07T18:19:23+00:00 app[worker.1]: D, [2011-09-07T11:19:23.305451 #1] DEBUG -- : NoMethodError: undefined method `values' for #PGresult:0x7fbafe16b2d0: SHOW client_min_messages 2011-09-07T18:19:23+00:00 app[worker.1]: D, [2011-09-07T11:19:23.307045 #1] DEBUG -- : PGError: ERROR: invalid value for parameter client_min_messages: 2011-09-07T18:19:23+00:00 app[worker.1]: : SET client_min_messages TO '' 2011-09-07T18:19:23+00:00 app[worker.1]: rake aborted! 2011-09-07T18:19:23+00:00 app[worker.1]: PGError: ERROR: invalid value for parameter client_min_messages: 2011-09-07T18:19:23+00:00 app[worker.1]: : SET client_min_messages TO '' 2011-09-07T18:19:23+00:00 app[worker.1]: 2011-09-07T18:19:23+00:00 app[worker.1]: Tasks: TOP = jobs:work 2011-09-07T18:19:23+00:00 app[worker.1]: (See full trace by running task with --trace) 2011-09-07T18:19:23+00:00 heroku[worker.1]: Process exited 2011-09-07T18:19:23+00:00 heroku[worker.1]: State changed from up to crashed 2011-09-07T18:19:23+00:00 heroku[worker.1]: State changed from crashed to created 2011-09-07T18:19:24+00:00 heroku[worker.1]: State changed from created to starting 2011-09-07T18:19:25+00:00 heroku[worker.1]: Starting process with command `rake jobs:work` 2011-09-07T18:19:26+00:00 heroku[worker.1]: State changed from starting to up 2011-09-07T18:19:26+00:00 app[worker.1]: D, [2011-09-07T11:19:26.622604 #1] DEBUG -- : PGError: ERROR: invalid value for parameter client_min_messages: 2011-09-07T18:19:26+00:00 app[worker.1]: : SET client_min_messages TO '' 2011-09-07T18:19:26+00:00 app[worker.1]: D, [2011-09-07T11:19:26.749509 #1] DEBUG -- : NoMethodError: undefined method `values' for #PGresult:0x7f452098e268: SHOW client_min_messages 2011-09-07T18:19:26+00:00 app[worker.1]: D, [2011-09-07T11:19:26.752097 #1] DEBUG -- : PGError: ERROR: invalid value for parameter client_min_messages: 2011-09-07T18:19:26+00:00 app[worker.1]: : SET client_min_messages TO '' 2011-09-07T18:19:26+00:00 app[worker.1]: rake aborted! 2011-09-07T18:19:26+00:00 app[worker.1]: PGError: ERROR: invalid value for parameter client_min_messages: 2011-09-07T18:19:26+00:00 app[worker.1]: : SET client_min_messages TO '' 2011-09-07T18:19:26+00:00 app[worker.1]: 2011-09-07T18:19:26+00:00 app[worker.1]: Tasks: TOP = jobs:work 2011-09-07T18:19:26+00:00 app[worker.1]: (See full trace by running task with --trace) 2011-09-07T18:19:26+00:00 heroku[worker.1]: Process exited 2011-09-07T18:19:27+00:00 heroku[worker.1]: State changed from up to crashed I have gem activerecord gem delayed_job gem sinatra-activerecord gem pg in my Gemfile and require 'sinatra/activerecord/rake' require 'active_record' require 'delayed_job' in the Rakefile. I most likely have some strange setting in my code. If someone spots any obvious mistake please tell. Thanks in advance, David -- David Hall, M. Sc., da...@dpg.se -- 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: SQL console plugin stopped working - anyone know why?
Give it another shot, I just fixed an issue on the server. On Jul 26, 2011, at 5:01 PM, S Wrobel wrote: The extremely useful Heroku SQL plugin just stopped working about a week ago. There seem to be a lot of people with the same issue: when you run heroku sql it says ! Internal server error and quits. See the github issue page here: http://github.com/ddollar/heroku-sql-console/issues/8 -- You received this message because you are subscribed to the Google Groups Heroku group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/X6WuNszB2p8J. 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. -- 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: Cedar does not recognize RACK_ENV?
Do you see the same behavior if you run RACK_ENV=staging rails console locally? On Jul 14, 2011, at 5:04 AM, arunthampi wrote: Hey guys - Tried running one of my apps on Cedar with RACK_ENV set to 'staging' but when I run `heroku run rails console` it says Loading production environment. Also Rails.env returns production. Anyone else seeing this? Is this a known bug? Thanks! Arun P.S. I checked and ENV['RACK_ENV'] is set to 'staging' but Rails.env returns 'production' -- 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. -- 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: GROUP BY fails on Heroku
What is the PostgreSQL equivalent of Chap's code? Mine is very similar, and i cannot get it to work on PostgreSQL. Thanks in advance -- You received this message because you are subscribed to the Google Groups Heroku group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/reCG0_3kW-IJ. 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: Procfile declares types - (none)
Make sure that your file is called Procfile, with a capital P On Saturday, June 18, 2011 at 7:28 PM, Jason Kuhrt wrote: I have a problem deploying a very simple node.js app to `--stack cedar` when I `git push heroku master` I get the following: - Heroku receiving push - Node.js app detected - Vendoring node 0.4.7 - Installing dependencies with npm 1.0.8 Dependencies installed - Discovering process types Procfile declares types - (none) - Compiled slug size is 3.4MB - Launching... done, v7 http://thievishfilms.herokuapp.com deployed to Heroku My problem is this part of the above: `Procfile declares types - (none)` The content of my procfile is: `web: node server.js` Why won't my procfile declare a process type of web? I followed the instructions at http://devcenter.heroku.com/articles/node-js perfectly. I am confused and any help would be extremely appreciated, thank you. Jason -- 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 (mailto:heroku@googlegroups.com). To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com (mailto:heroku+unsubscr...@googlegroups.com). For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- 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: Unable to verify SSL certificate for api.heroku.com
This will happen if your openssl libraries are not functioning correctly. You can set HEROKU_SSL_VERIFY=disable in your environment to prevent the verification checks. Cheers, David On Monday, June 20, 2011 at 4:51 PM, iamtheschmitzer wrote: I updated my heroku gem and I get the warning: Unable to verify SSL certificate for api.heroku.com (http://api.heroku.com) with every command. Can't find anything in the docs. Anybody know how to fix? -- You received this message because you are subscribed to the Google Groups Heroku group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/J9ZSbwaPBqUJ. To post to this group, send email to heroku@googlegroups.com (mailto:heroku@googlegroups.com). To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com (mailto:heroku+unsubscr...@googlegroups.com). For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- 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.
New Relic in a Rack app
I have read and followed the steps outlined for Rack apps in http://devcenter.heroku.com/articles/newrelic#using_new_relic_from_a_rack_appand still get the message Not a Rails app, can't install New Relic plugin. after deploy to Heroku. I added the configure :production do require 'newrelic_rpm'end part to config.ru === imgpxy Web URL:http://imgpxy.heroku.com/ Git Repo: g...@heroku.com:imgpxy.git Dynos: 5 Workers:0 Repo size: 2M Slug size: 724k Stack: bamboo-mri-1.9.2 Dyno usage: Web - 437.03 dyno-hours Data size: (empty) Addons: Basic Logging, Memcache 5MBs, New Relic Standard, Shared Database 5MB -- David Hall, M. Sc., da...@dpg.se +46 (0)708-39 62 91 -- 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: Suddenly can't deploy Rails 3/Ruby 1.92 from Windows -- crash is about rack 1.3.0 vs rack 1.2.3
This happens because rack 1.3.0 still exists in your app's bundler cache and the stacks prior to cedar do not bundle exec when running your app. You could work around this by deleting and recreating the app. You could also give the cedar stack a try which does not have this issue. Cheers, David On Tuesday, June 7, 2011 at 6:02 PM, Erich wrote: My app was working fine on the 1.9.2 branch, and it still runs fine locally. But now when I try to deploy to Heroku it crashes with this error in the log. You have already activated rack 1.3.0, but your Gemfile requires rack 1.2.3. Consider using bundle exec. (Gem::LoadError) I briefly had rails 3.1 installed but it's not on my system anymore. gem list and bundle list show no sign of rack 1.3.0. But sure enough I do see this in response to an initial push: remote: - Installing gem rack from http://rubygems.org remote: Successfully installed rack-1.3.0 remote: 1 gem installed As well as a lot of other things that aren't in my gemfile. I thought maybe it was grabbing everything from my local gem list, but deleting them out doesn't get rid of them. So where besides gemfile, gemfile.lock (ignored because I'm on windows, but I've still been checking it) and local gems would a push to heroku be finding gems to install? I know it's on my end, and something about the particular project, because a similar project on the same dev box is still able to deploy successfully. Thanks in advance for any leads. ec -- 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 (mailto:heroku@googlegroups.com). To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com (mailto:heroku+unsubscr...@googlegroups.com). For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- 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: MongoHQ and node.js
This should be working for you now, please give it another shot. Cheers, David On Wednesday, June 1, 2011 at 7:29 AM, David Hall wrote: I'm trying to deploy a node.js app on the cedar stack that uses MongoHQ. I am not sure how what to include in package.json to get the mongo module installed. If include mongodb: 0.9.1 under dependencies I get mongodb@0.9.1 (mailto:mongodb@0.9.1) install /tmp/build_1q8sajeyt0jdx/node_modules/mongodb ./install.sh (http://install.sh) ./install.sh (http://install.sh): line 2: [: too many arguments Not building native library for cygwin make -C ./external-libs/bson make[1]: Entering directory `/tmp/build_1q8sajeyt0jdx/node_modules/mongodb/external-libs/bson' rm -rf build .lock-wscript bson.node node-waf configure build make[1]: node-waf: Command not found make[1]: *** [all] Error 127 make[1]: Leaving directory `/tmp/build_1q8sajeyt0jdx/node_modules/mongodb/external-libs/bson' make: *** [build_native] Error 2 npm ERR! error installing mongodb@0.9.1 (mailto:mongodb@0.9.1) Error: mongodb@0.9.1 (mailto:mongodb@0.9.1) install: `./install.sh (http://install.sh)` npm ERR! error installing mongodb@0.9.1 (mailto:mongodb@0.9.1) `sh -c ./install.sh (http://install.sh)` failed with 2 npm ERR! error installing mongodb@0.9.1 (mailto:mongodb@0.9.1) at ChildProcess.anonymous (/mnt/slug-compiler/language_packs/node/vendor/npm/npm-1.0.6/lib/utils/exec.js:49:20) npm ERR! error installing mongodb@0.9.1 (mailto:mongodb@0.9.1) at ChildProcess.emit (events.js:67:17) npm ERR! error installing mongodb@0.9.1 (mailto:mongodb@0.9.1) at ChildProcess.onexit (child_process.js:192:12) npm ERR! mongodb@0.9.1 (mailto:mongodb@0.9.1) install: `./install.sh (http://install.sh)` npm ERR! `sh -c ./install.sh (http://install.sh)` failed with 2 npm ERR! npm ERR! Failed at the mongodb@0.9.1 (mailto:mongodb@0.9.1) install script. npm ERR! This is most likely a problem with the mongodb package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! ./install.sh (http://install.sh) npm ERR! You can get their info via: npm ERR! npm owner ls mongodb npm ERR! There is likely additional logging output above. npm ERR! npm ERR! System Linux 2.6.18-xenU-ec2-v1.2 npm ERR! command /mnt/slug-compiler/language_packs/node/vendor/node/node-0.4.7 /mnt/slug-compiler/language_packs/node/vendor/npm/npm-1.0.6/cli.js install npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /tmp/build_1q8sajeyt0jdx/npm-debug.log npm not ok ! Failed to install dependencies with npm ! Heroku push rejected, failed to compile Node.js app / David -- David Hall, M. Sc., TV4 Sweden -- 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 (mailto:heroku@googlegroups.com). To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com (mailto:heroku+unsubscr...@googlegroups.com). For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- 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.
MongoHQ and node.js
I'm trying to deploy a node.js app on the cedar stack that uses MongoHQ. I am not sure how what to include in package.json to get the mongo module installed. If include mongodb: 0.9.1 under dependencies I get mongodb@0.9.1 install /tmp/build_1q8sajeyt0jdx/node_modules/mongodb ./install.sh ./install.sh: line 2: [: too many arguments Not building native library for cygwin make -C ./external-libs/bson make[1]: Entering directory `/tmp/build_1q8sajeyt0jdx/node_modules/mongodb/external-libs/bson' rm -rf build .lock-wscript bson.node node-waf configure build make[1]: node-waf: Command not found make[1]: *** [all] Error 127 make[1]: Leaving directory `/tmp/build_1q8sajeyt0jdx/node_modules/mongodb/external-libs/bson' make: *** [build_native] Error 2 npm ERR! error installing mongodb@0.9.1 Error: mongodb@0.9.1 install: `./install.sh` npm ERR! error installing mongodb@0.9.1 `sh -c ./install.sh` failed with 2 npm ERR! error installing mongodb@0.9.1 at ChildProcess.anonymous (/mnt/slug-compiler/language_packs/node/vendor/npm/npm-1.0.6/lib/utils/exec.js:49:20) npm ERR! error installing mongodb@0.9.1 at ChildProcess.emit (events.js:67:17) npm ERR! error installing mongodb@0.9.1 at ChildProcess.onexit (child_process.js:192:12) npm ERR! mongodb@0.9.1 install: `./install.sh` npm ERR! `sh -c ./install.sh` failed with 2 npm ERR! npm ERR! Failed at the mongodb@0.9.1 install script. npm ERR! This is most likely a problem with the mongodb package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! ./install.sh npm ERR! You can get their info via: npm ERR! npm owner ls mongodb npm ERR! There is likely additional logging output above. npm ERR! npm ERR! System Linux 2.6.18-xenU-ec2-v1.2 npm ERR! command /mnt/slug-compiler/language_packs/node/vendor/node/node-0.4.7 /mnt/slug-compiler/language_packs/node/vendor/npm/npm-1.0.6/cli.js install npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /tmp/build_1q8sajeyt0jdx/npm-debug.log npm not ok ! Failed to install dependencies with npm ! Heroku push rejected, failed to compile Node.js app / David -- David Hall, M. Sc., TV4 Sweden -- 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: Setting default app name?
This happens if you have more than one git remote as a heroku app to avoid running commands on the wrong app. You can set the default remote by running git config heroku.remote heroku Cheers, David On Thursday, May 26, 2011 at 12:49 PM, Pulley wrote: I just updated my heroku gem from 1.17.5 to 2.1.4. Suddenly, the gem does not recognize my default app. I have a git remote called 'heroku', but when I try, for example, heroku console, I get 'No app specified'. Obviously, it works when I add '--app myapp', but I'd rather not specify the app everytime. The gem recognized my default app before the upgrade, anyone else having this issue? I searched the docs, this forum, and google, could not find anything on setting the default app name for heroku. Thanks! -- 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 (mailto:heroku@googlegroups.com). To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com (mailto:heroku+unsubscr...@googlegroups.com). For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- 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: Rake aborted!
Looks like there's an issue with the latest rake released yesterday and Rails 3. http://stackoverflow.com/questions/5287121/undefined-method-task-using-rake-0-9-0-beta-4 Another solution would be to pin rake to 0.8.7 in your Gemfile. On Saturday, May 21, 2011 at 10:39 AM, Nikue wrote: I haven't changed anything except add a few migrations. I removed those but it didn't solve the problem, obviously. Is it possible heroku automatically upgraded rake this week? Not sure what version I was using before. Could I just specify an older one in my gemfile? Only rails and custom ones are in there now. Thanks, Nikue On May 21, 10:30 am, Nikue nik...@gmail.com wrote: Hey guys, heroku rake getting aborted with this trace: $ heroku rake db:migrate --trace rake aborted! undefined method `task' for #Freelance::Application:0x7fca8218f160 /app/.bundle/gems/ruby/1.8/gems/railties-3.0.7/lib/rails/ application.rb:215:in ` initialize_tasks' /app/.bundle/gems/ruby/1.8/gems/railties-3.0.7/lib/rails/ application.rb:139:in ` load_tasks' /app/.bundle/gems/ruby/1.8/gems/railties-3.0.7/lib/rails/ application.rb:77:in `s end' /app/.bundle/gems/ruby/1.8/gems/railties-3.0.7/lib/rails/ application.rb:77:in `m ethod_missing' /app/Rakefile:7 /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/rake_module.rb: 25:in `load' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/rake_module.rb: 25:in `load_r akefile' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 495:in `raw_l oad_rakefile' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 78:in `load_r akefile' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 129:in `stand ard_exception_handling' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 77:in `load_r akefile' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 61:in `run' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 129:in `stand ard_exception_handling' any ideas? -- 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. -- 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: Rake aborted!
Also related: https://github.com/rails/rails/issues/1171 On Saturday, May 21, 2011 at 10:42 AM, David Dollar wrote: Looks like there's an issue with the latest rake released yesterday and Rails 3. http://stackoverflow.com/questions/5287121/undefined-method-task-using-rake-0-9-0-beta-4 Another solution would be to pin rake to 0.8.7 in your Gemfile. On Saturday, May 21, 2011 at 10:39 AM, Nikue wrote: I haven't changed anything except add a few migrations. I removed those but it didn't solve the problem, obviously. Is it possible heroku automatically upgraded rake this week? Not sure what version I was using before. Could I just specify an older one in my gemfile? Only rails and custom ones are in there now. Thanks, Nikue On May 21, 10:30 am, Nikue nik...@gmail.com wrote: Hey guys, heroku rake getting aborted with this trace: $ heroku rake db:migrate --trace rake aborted! undefined method `task' for #Freelance::Application:0x7fca8218f160 /app/.bundle/gems/ruby/1.8/gems/railties-3.0.7/lib/rails/ application.rb:215:in ` initialize_tasks' /app/.bundle/gems/ruby/1.8/gems/railties-3.0.7/lib/rails/ application.rb:139:in ` load_tasks' /app/.bundle/gems/ruby/1.8/gems/railties-3.0.7/lib/rails/ application.rb:77:in `s end' /app/.bundle/gems/ruby/1.8/gems/railties-3.0.7/lib/rails/ application.rb:77:in `m ethod_missing' /app/Rakefile:7 /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/rake_module.rb: 25:in `load' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/rake_module.rb: 25:in `load_r akefile' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 495:in `raw_l oad_rakefile' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 78:in `load_r akefile' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 129:in `stand ard_exception_handling' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 77:in `load_r akefile' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 61:in `run' /app/.bundle/gems/ruby/1.8/gems/rake-0.9.0/lib/rake/application.rb: 129:in `stand ard_exception_handling' any ideas? -- 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. -- 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: Rails 3.1 asset pipeline causing 503?
Interesting. Well, it looks like the jump to RC1 with an updated Sprockets has fixed it: - sprockets (~ 2.0.0.beta.2) + sprockets (~ 2.0.0.beta.5) Living on the edge! On May 20, 11:56 am, Chris Hanks christopher.m.ha...@gmail.com wrote: I get this same error frequently on my development machine (Ruby 1.9.2p180 on Ubuntu Natty), so it's not Heroku-specific. On May 20, 8:01 am, David datab...@gmail.com wrote: Klaus Harti posted this message originally on May 11th and I have it in my digest list - I just can't seem to find it on Google Groups. Anyhow, I'm seeing a similar problem but with this on serving the resulting CSS: !! Unexpected error while processing request: deadlock; recursive locking Log: 2011-05-20T08:31:13+00:00 heroku[web.1]: Starting process with command: `thin -p 49201 -e production -R /home/heroku_rack/heroku.ru start` 2011-05-20T08:31:17+00:00 app[web.1]: Starting the New Relic Agent. 2011-05-20T08:31:17+00:00 app[web.1]: Installed New Relic Browser Monitoring middleware 2011-05-20T08:31:19+00:00 app[web.1]: Thin web server (v1.2.6 codename Crazy Delicious) 2011-05-20T08:31:19+00:00 app[web.1]: Maximum connections set to 1024 2011-05-20T08:31:19+00:00 app[web.1]: Listening on 0.0.0.0:49201, CTRL+C to stop 2011-05-20T01:31:20-07:00 heroku[web.1]: State changed from starting to up 2011-05-20T08:31:27+00:00 app[web.1]: 2011-05-20T08:31:27+00:00 app[web.1]: 2011-05-20T08:31:27+00:00 app[web.1]: Started GET / for 72.229.127.215 at 2011-05-20 01:31:27 -0700 2011-05-20T08:31:27+00:00 app[web.1]: Processing by HomeController#index as HTML 2011-05-20T08:31:27+00:00 app[web.1]: Rendered home/index.html.erb within layouts/application (15.7ms) 2011-05-20T08:31:27+00:00 app[web.1]: [Sprockets] application.css building 2011-05-20T08:31:27+00:00 app[web.1]: [Sprockets] style.css building 2011-05-20T08:31:27+00:00 app[web.1]: [Sprockets] application.js building 2011-05-20T08:31:27+00:00 app[web.1]: [Sprockets] jquery.js building 2011-05-20T08:31:27+00:00 app[web.1]: [Sprockets] jquery_ujs.js building 2011-05-20T08:31:28+00:00 app[web.1]: Rendered shared/ _tracking_footer.html.erb (0.4ms) 2011-05-20T08:31:28+00:00 app[web.1]: Completed 200 OK in 1417ms (Views: 1417.0ms | ActiveRecord: 0.0ms) 2011-05-20T08:31:28+00:00 heroku[router]: GET mysite.heroku.com/ dyno=web.1 queue=0 wait=0ms service=1469ms bytes=1834 2011-05-20T08:31:28+00:00 app[web.1]: cache: [GET /] miss 2011-05-20T08:31:28+00:00 app[web.1]: Connected to NewRelic Service at collector-1.newrelic.com:80 2011-05-20T08:31:29+00:00 app[web.1]: !! Unexpected error while processing request: deadlock; recursive locking 2011-05-20T08:31:29+00:00 heroku[router]: Error H13 (Connection closed without response) - GET mysite.heroku.com/assets/application- b1637fec79c8bbd5d3a18e84f3da878f.css dyno=web.1 queue=0 wait=0ms service=0ms bytes=0 2011-05-20T01:31:29-07:00 heroku[nginx]: GET / HTTP/1.1 | 72.229.127.215 | 1480 | http | 200 both edge and beta1 have the same results: Gemfile: source 'http://rubygems.org' #gem 'rails', '3.1.0.beta1' gem 'rails', git: 'git://github.com/rails/rails.git' gem 'pg' gem 'therubyracer-heroku', '0.8.1.pre3' # Asset template engines gem 'sass' gem 'coffee-script' gem 'uglifier' gem 'jquery-rails' Previous post: Rails 3.1 asset pipeline causing 503? Klaus Hartl klaus.ha...@googlemail.com May 11 06:06AM -0700 ^ Hello there, I was curious and tried if I can use the new assets pipeline that comes with Rails 3.1 beta (sprockets). From time to time I am getting a 503 for requests of those merged application.js/.css files, an example from my log: 2011-05-11T12:26:10+00:00 app[web.1]: cache: [GET /assets/ application-140d82c5f1fa592792bc01518bd2906e.js] fresh 2011-05-11T12:26:10+00:00 heroku[router]: GET tweektv.heroku.com/ assets/application-140d82c5f1fa592792bc01518bd2906e.js dyno=web.1 queue=0 wait=0ms service=2ms bytes=8700 2011-05-11T05:26:10-07:00 heroku[nginx]: GET /assets/ application-140d82c5f1fa592792bc01518bd2906e.js HTTP/1.1 | 84.191.168.124 | 1325 | http | 503 I am fully aware that this is beta and I did not necessarily expect it to work just so. I'm wondering if this is something related to the app or if this is on Heroku's side anyway (in other words, should I just wait for Rails 3.1 out of beta or not)... The log message isn't very helpful to me, as is what I get in the response of such 503 request (stripped html): Application Error An error occurred in the application and your page could not be served. Please try again in a few moments. If you are the application owner, check your logs for details. Last not least I have installed the Exceptional Premium add-on and I'm
Rails 3.1 asset pipeline causing 503?
Klaus Harti posted this message originally on May 11th and I have it in my digest list - I just can't seem to find it on Google Groups. Anyhow, I'm seeing a similar problem but with this on serving the resulting CSS: !! Unexpected error while processing request: deadlock; recursive locking Log: 2011-05-20T08:31:13+00:00 heroku[web.1]: Starting process with command: `thin -p 49201 -e production -R /home/heroku_rack/heroku.ru start` 2011-05-20T08:31:17+00:00 app[web.1]: Starting the New Relic Agent. 2011-05-20T08:31:17+00:00 app[web.1]: Installed New Relic Browser Monitoring middleware 2011-05-20T08:31:19+00:00 app[web.1]: Thin web server (v1.2.6 codename Crazy Delicious) 2011-05-20T08:31:19+00:00 app[web.1]: Maximum connections set to 1024 2011-05-20T08:31:19+00:00 app[web.1]: Listening on 0.0.0.0:49201, CTRL+C to stop 2011-05-20T01:31:20-07:00 heroku[web.1]: State changed from starting to up 2011-05-20T08:31:27+00:00 app[web.1]: 2011-05-20T08:31:27+00:00 app[web.1]: 2011-05-20T08:31:27+00:00 app[web.1]: Started GET / for 72.229.127.215 at 2011-05-20 01:31:27 -0700 2011-05-20T08:31:27+00:00 app[web.1]: Processing by HomeController#index as HTML 2011-05-20T08:31:27+00:00 app[web.1]: Rendered home/index.html.erb within layouts/application (15.7ms) 2011-05-20T08:31:27+00:00 app[web.1]: [Sprockets] application.css building 2011-05-20T08:31:27+00:00 app[web.1]: [Sprockets] style.css building 2011-05-20T08:31:27+00:00 app[web.1]: [Sprockets] application.js building 2011-05-20T08:31:27+00:00 app[web.1]: [Sprockets] jquery.js building 2011-05-20T08:31:27+00:00 app[web.1]: [Sprockets] jquery_ujs.js building 2011-05-20T08:31:28+00:00 app[web.1]: Rendered shared/ _tracking_footer.html.erb (0.4ms) 2011-05-20T08:31:28+00:00 app[web.1]: Completed 200 OK in 1417ms (Views: 1417.0ms | ActiveRecord: 0.0ms) 2011-05-20T08:31:28+00:00 heroku[router]: GET mysite.heroku.com/ dyno=web.1 queue=0 wait=0ms service=1469ms bytes=1834 2011-05-20T08:31:28+00:00 app[web.1]: cache: [GET /] miss 2011-05-20T08:31:28+00:00 app[web.1]: Connected to NewRelic Service at collector-1.newrelic.com:80 2011-05-20T08:31:29+00:00 app[web.1]: !! Unexpected error while processing request: deadlock; recursive locking 2011-05-20T08:31:29+00:00 heroku[router]: Error H13 (Connection closed without response) - GET mysite.heroku.com/assets/application- b1637fec79c8bbd5d3a18e84f3da878f.css dyno=web.1 queue=0 wait=0ms service=0ms bytes=0 2011-05-20T01:31:29-07:00 heroku[nginx]: GET / HTTP/1.1 | 72.229.127.215 | 1480 | http | 200 both edge and beta1 have the same results: Gemfile: source 'http://rubygems.org' #gem 'rails', '3.1.0.beta1' gem 'rails', git: 'git://github.com/rails/rails.git' gem 'pg' gem 'therubyracer-heroku', '0.8.1.pre3' # Asset template engines gem 'sass' gem 'coffee-script' gem 'uglifier' gem 'jquery-rails' Previous post: Rails 3.1 asset pipeline causing 503? Klaus Hartl klaus.ha...@googlemail.com May 11 06:06AM -0700 ^ Hello there, I was curious and tried if I can use the new assets pipeline that comes with Rails 3.1 beta (sprockets). From time to time I am getting a 503 for requests of those merged application.js/.css files, an example from my log: 2011-05-11T12:26:10+00:00 app[web.1]: cache: [GET /assets/ application-140d82c5f1fa592792bc01518bd2906e.js] fresh 2011-05-11T12:26:10+00:00 heroku[router]: GET tweektv.heroku.com/ assets/application-140d82c5f1fa592792bc01518bd2906e.js dyno=web.1 queue=0 wait=0ms service=2ms bytes=8700 2011-05-11T05:26:10-07:00 heroku[nginx]: GET /assets/ application-140d82c5f1fa592792bc01518bd2906e.js HTTP/1.1 | 84.191.168.124 | 1325 | http | 503 I am fully aware that this is beta and I did not necessarily expect it to work just so. I'm wondering if this is something related to the app or if this is on Heroku's side anyway (in other words, should I just wait for Rails 3.1 out of beta or not)... The log message isn't very helpful to me, as is what I get in the response of such 503 request (stripped html): Application Error An error occurred in the application and your page could not be served. Please try again in a few moments. If you are the application owner, check your logs for details. Last not least I have installed the Exceptional Premium add-on and I'm not getting any error notifications in there. Any insight is very much appreciated... --Klaus -- 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: Bundle Package
Yes they will. Cheers, David On Tuesday, May 17, 2011 at 9:26 AM, Scott Watermasysk wrote: If I run bundle package and commit my gems to my repository, will they be used by heroku when it executes bundle install? Thanks, Scott -- Scott Watermasysk Founder, KickoffLabs http://kickofflabs.com -- 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. -- 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: 503 errors...
I get 503 on at least one of our apps as well. Looks like pages not cached by Varnish gets 503 errors. On Thu, Apr 28, 2011 at 22:54, Rohit Dewan dew...@gmail.com wrote: Same here. All our apps are getting 503 on every request :-( - Rohit http://www.valleyseek.com On Thu, Apr 28, 2011 at 1:52 PM, kowsik kow...@gmail.com wrote: Just started to happen. Seeing a bunch of 'Error H99 (Platform error)' in the logs. http://status.heroku.com says all systems go. Heads up, K. --- http://blitz.io http://twitter.com/pcapr http://labs.mudynamics.com -- 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. -- 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. -- David Hall, M. Sc., da...@dpg.se +46 (0)708-39 62 91 -- 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: 503 errors...
Herokus status page has been updated since then. http://status.heroku.com/incident/152 On Thu, Apr 28, 2011 at 23:35, Jeff Schmitz jeffrey.j.schm...@gmail.comwrote: No problem here FYI On Thu, Apr 28, 2011 at 4:02 PM, David Hall petters...@gmail.com wrote: I get 503 on at least one of our apps as well. Looks like pages not cached by Varnish gets 503 errors. On Thu, Apr 28, 2011 at 22:54, Rohit Dewan dew...@gmail.com wrote: Same here. All our apps are getting 503 on every request :-( - Rohit http://www.valleyseek.com On Thu, Apr 28, 2011 at 1:52 PM, kowsik kow...@gmail.com wrote: Just started to happen. Seeing a bunch of 'Error H99 (Platform error)' in the logs. http://status.heroku.com says all systems go. Heads up, K. --- http://blitz.io http://twitter.com/pcapr http://labs.mudynamics.com -- 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. -- 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. -- David Hall, M. Sc., da...@dpg.se +46 (0)708-39 62 91 -- 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. -- 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. -- David Hall, M. Sc., da...@dpg.se +46 (0)708-39 62 91 -- 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.
Heroku Client 2.0 Released
We've just released version 2.0 of the Heroku client. While most of the changes are behind the scenes, a few new things you'll notice include: * The help system has been completely revamped, including help for individual commands. * All commands now have namespaces for organizational purposes. For example, `heroku apps` is now grouped as `heroku apps:create`. These commands continue to be accessible in their short form (e.g. `heroku create`). If you're using any plugins to the heroku client, it would be a good idea to see if any newer versions have been released. If you run into any issues with the new client, please submit an issue against the github repo at http://github.com/heroku/heroku/issues -- 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.
Frequent IP changes with Hostname SSL
We are using Heroku with Hostname SSL and are experiencing problem with our domain being pointed to new IP addresses very frequently. Yesterday we had 50.17.237.46, a couple of hours ago 174.129.30.102, then 174.129.38.100 and now 174.129.38.100. When trying to fetch the web page on the host being used the moment before with curl -H Host: www.tv4play.se xx.xx.xx.xx we get no answer or an empty reply. Since visitors web browsers tend to cache their DNS lookups they will get a blank screen until they force reload or change browser. It seems like this problem has increased during the past day. Earlier we had a few spurious reports of people reaching wrong host but now we see this problem ourselves. Have anyone else noticed this? Any pointers to get rid of this problem? Thanks in advance, David -- David Hall, M. Sc., TV4 -- 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: Taps Server Error: unexpected nil
What version of the taps gem are you using? On Apr 4, 2011, at 2:05 PM, Francois wrote: wondering if anyone has encountered the following error before when using heroku db:pull ? Saving session to pull_201104041103.dat.. !!! Caught Server Exception HTTP CODE: 500 Taps Server Error: unexpected nil - thanks F -- 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. -- 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: Taps Server Error: unexpected nil
I'm working on a permanent solution. In the meantime you can roll back to taps 0.3.21. On Apr 4, 2011, at 2:13 PM, kbjerring wrote: I have just seen the exact same error (Using Taps-0.3.22) Alas, I have found no solution yet :( On Apr 4, 8:05 pm, Francois fhar...@gmail.com wrote: wondering if anyone has encountered the following error before when using heroku db:pull ? Saving session to pull_201104041103.dat.. !!! Caught Server Exception HTTP CODE: 500 Taps Server Error: unexpected nil - thanks F -- 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. -- 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: Taps Server Error: unexpected nil
Sorry, forgot to mention that you will need to roll back to heroku version 1.19.1 as well. Cheers, David On Apr 4, 2011, at 2:23 PM, Ciprian Dunareanu wrote: Unfortunately that doesn't work for me: Your taps gem is out of date (v0.3.22 or higher required). Are you using an older heroku gem? Regards. -- Ciprian Dunareanu Sent with Sparrow On Monday, April 4, 2011 at 9:21 PM, kbjerring wrote: Great! Taps 0.3.21 certainly works. On Apr 4, 8:16 pm, David Dollar ddol...@gmail.com wrote: I'm working on a permanent solution. In the meantime you can roll back to taps 0.3.21. On Apr 4, 2011, at 2:13 PM, kbjerring wrote: I have just seen the exact same error (Using Taps-0.3.22) Alas, I have found no solution yet :( On Apr 4, 8:05 pm, Francois fhar...@gmail.com wrote: wondering if anyone has encountered the following error before when using heroku db:pull ? Saving session to pull_201104041103.dat.. !!! Caught Server Exception HTTP CODE: 500 Taps Server Error: unexpected nil - thanks F -- 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 athttp://groups.google.com/group/heroku?hl=en. -- 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. -- 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. -- 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: Taps Server Error: unexpected nil
Could anyone that was running into this issue please try the latest pre-release heroku/taps gems: gem install heroku taps --pre and let me know if you're still running into issues? I just pushed them up so you may need to wait a few minutes for them to show up in the index. The versions you're looking for are: heroku 1.20.1.pre1 taps 0.3.23.pre1 Thanks, David On Apr 4, 2011, at 2:46 PM, Ciprian Dunareanu wrote: Yep, it worked with my previous heroku gem version: 1.9.14 Thanks :) On Monday, April 4, 2011 at 9:26 PM, David Dollar wrote: Sorry, forgot to mention that you will need to roll back to heroku version 1.19.1 as well. Cheers, David On Apr 4, 2011, at 2:23 PM, Ciprian Dunareanu wrote: Unfortunately that doesn't work for me: Your taps gem is out of date (v0.3.22 or higher required). Are you using an older heroku gem? Regards. -- Ciprian Dunareanu Sent with Sparrow On Monday, April 4, 2011 at 9:21 PM, kbjerring wrote: Great! Taps 0.3.21 certainly works. On Apr 4, 8:16 pm, David Dollar ddol...@gmail.com wrote: I'm working on a permanent solution. In the meantime you can roll back to taps 0.3.21. On Apr 4, 2011, at 2:13 PM, kbjerring wrote: I have just seen the exact same error (Using Taps-0.3.22) Alas, I have found no solution yet :( On Apr 4, 8:05 pm, Francois fhar...@gmail.com wrote: wondering if anyone has encountered the following error before when using heroku db:pull ? Saving session to pull_201104041103.dat.. !!! Caught Server Exception HTTP CODE: 500 Taps Server Error: unexpected nil - thanks F -- 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 athttp://groups.google.com/group/heroku?hl=en. -- 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. -- 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. -- 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. -- 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. -- 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: Is it ok to check the Heroku queue depth/wait_time and set dynos accordingly after every action in my app?
It's not worth the effort probably, even if you could. Usually the bottle neck becomes the DB anyway. Sent from my iPhone On Mar 19, 2011, at 2:13 AM, Ben H crusa...@gmail.com wrote: I am trying to work out how to respond to increasing/decreasing traffic to my Heroku site with dynos management from within the app itself. I know you can access HTTP_X_HEROKU_QUEUE_DEPTH or HTTP_X_HEROKU_QUEUE_WAIT_TIME and use those to set the amount of dynos. What I'm wondering is what process to use to do the checking. Is it okay to add an after_filter to every action in the app to do a check against some threshold, and if a threshold has been met, change the number of dynos? I would only have 5/6 thresholds, so for vast majority of users the only impact would be the increased time it takes to do the check, and then for a handful of users it would be the check + the changing of dynos time. Would it be too much of an inconvenience to the users? Is there a better way? -- 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. -- 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: Dyno wake up processing
Files generated by cron will not be there for a web process. Here's a basic summary of how Heroku's dyno grid works: When you push up a copy of your app, we run a compile process on it (runs bundler, etc) and generate a slug which is a self-contained copy of your app. When you request any process be run on your app (dyno, worker, cron) we find available space in our dyno grid, copy the slug for your app to that server, mount the slug, and launch the process you requested. In short, the process for your dyno may not even be on the same server that your cron was run on. If you need persistent storage I'd suggest using something like S3. Cheers, David On Tue, Mar 8, 2011 at 11:12 AM, Wes Gamble we...@att.net wrote: The files comprise a cache that needs to be there for the next user, even if that user is the one who's unfortunate enough to wake up the app. W On 3/8/11 9:54 AM, Miles Smith wrote: I always assume my cronies is running brand new instances. Why not just check if you files are there, if not , create them. On Mar 8, 2011 3:39 AM, Wes Gamble we...@att.net wrote: Given a Heroku app.: If I have a cron job that populates a cache directory in RAILS_ROOT/tmp once a day, and all of my dynos go idle, when they wake up, will the tmp directory be empty or will it still contain what my cron job wrote? (I think the deeper question here is whether a dyno wakes up in some pre-existing state, or whether a dyno. is simply reconstituted from the slug state at deploy-time? I apologize if my phrasing is awkward/imprecise.) If tmp will be empty, do we have any way to hook into the dyno wake-up process in order to do some filesystem initialization in /tmp? Thanks, Wes -- 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. -- 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. -- 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. -- 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: Dyno wake up processing
When your app is idled out, it is taken out of the dyno grid. The next time it boots, it will have a clean tmp/ dir. As far as hooking the dyno wake, that would just be adding some code that runs when your app is booting. If you're using Rails, this could be a script in config/initializers -- 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: Multiple users with different SSH keys
Check out https://github.com/ddollar/heroku-accounts Give the --auto option a try, but be aware that it will write to your ~/.ssh/config On Thu, Mar 3, 2011 at 10:58 AM, gezope gez...@gmail.com wrote: Hello, I would like to use different users with different keys. When I tried: git clone ...app.git it says: ! o...@user.com not authorized to access APPNAME fatal: The remote end hung up unexpectedly I generated another SSH key to another folder. Then 'heroku logout' then 'heroku login' with another user. Then I 'heroku keys:add' where the public key was added succesfully. I checked everything: heroku list - see the apps, heroku keys - see my keys with the new user. Means I have new user, I coud login, I have new SSH key, it's added, I can see the apps and have all permissions - but I still cannot use git clone. Any help is highly appriciated, many thanks, Zoltan -- 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. -- 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: Your application is too busy to open a console session.
Console sessions do happen over a dyno. A dyno will be in-use for the time between when you press enter on a command and the result comes back. Idle time sitting at the console prompt does not use up a dyno. Hope this helps, David On Feb 13, 2011, at 6:46 AM, Neil Middleton wrote: This had me worried for a minute, as I frequently open consoles on 1 dyno apps. That message suggests that if a console is open, a dyno is busy servicing the request. However, after a quick check it seems to not be the case. Maybe someone @ Heroku could tell us what the deal is here - I don't want my inquisitiveness to take a site offline ;) Neil Middleton http://about.me/neilmiddleton On Saturday, 12 February 2011 at 12:14, MikeBlyth wrote: Console sessions require an open dyno to use for execution. -- 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. -- 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: Logging - STDOUT ignores log_level
Hey there,
Try changing your log lines to this:
config.logger = Logger.new(STDOUT)
config.logger.level = Logger::INFO
Thanks,
David
On Feb 5, 2011, at 4:16 PM, Jesse wrote:
just installed the logging addon
http://docs.heroku.com/logging
I am running a rails 2.2.2 app, maybe this occurs with other versions
as well
if you use
config.logger= Logger.new(STDOUT)
then you basically end up with debug output, request, sql, partials
rendered
seems like overkill for production?
- I did not notice any difference when adjusting the config.level ?
config.log_level = :info
the behavior was the same on both localhost and deployed to heroku
if you don't use the STDOUT, then you end up with no app logging, just
the nginx
2011-02-05T13:04:40-08:00 heroku[nginx]: GET /login?testing4 HTTP/1.1
| 10.116.147.148 | 3265 | https | 200
I like the standard rails :info level logging; for each request -
includes the parameters but not much else
Processing SessionsController#new (for 127.0.0.1 at 2011-02-05
13:07:30) [GET]
Parameters: {action=new, testing5=nil,
controller=sessions}
Rendering template within layouts/application_full_width
Rendering sessions/new
Completed in 79ms (View: 18, DB: 6) | 200 OK [http://localhost/login?
testing5]
maybe this is an issue related to older versions of rails only?
has anyone else noticed this behavior or know of a workaround?
for now I am just removing the addon
Thanks,
- Jesse
--
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.
--
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: Node.js status?
Though I'd love to get it working on Heroku. I'm in the beta for duostack and haven't tried out our app since they're missing a few things like background jobs, memcache, etc. I need a Redis based node install that runs npm packages and support websockets. So far, I have to self-host. Heroku's been at it for several months now, I'm just curious to see where several long months of work have left them with their node.js stack. Any updates? The Rails side of duostack may be looking good in a few months once they add in everything I need - which isn't too much. I'm spending some decent coin a month and before I start spending more, I'd love to see Heroku start doing better at communicating both features and support. If I leave to duostack, it's going to be partially for those 2 reasons as well. Step it up boys - you have the money now. /daivd. On Jan 31, 9:34 am, Pedro Del Gallego pedro.delgall...@gmail.com wrote: http://nodester.com/aims to be the heroku of nodejs, and its available now if you can get a coupon (invite). In fact, you have a bunch of companies working in that space, e.g. duostack , nodeJsCloud, and nodejitsu. I am having fun with a nodejs game that a i'm working on, so far duostack has been great. -- 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.
Flushing memcache with Dalli
We are using Dalli and the Memcache add-on and would like to flush our cache
to observe how our application behaves while the cache fills up.
Have tried this from the console:
t_dall.stats
= {mc3.ec2.northscale.net:11211={bytes=88686484, cas_misses=0,
delete_hits=0, get_hits=406549, rusage_system=23116.67,
pid=7601, cas_hits=0, incr_misses=0,
connection_structures=1896, evictions=12901, threads=4,
limit_maxbytes=67108864, incr_hits=0, cmd_flush=9,
decr_misses=0, pointer_size=64, daemon_connections=10,
time=129478, conn_yields=0, engine_maxbytes=104857600,
version=1.4.4_188_g0117a2c, total_items=146544,
bytes_written=6622429660, rejected_conns=0, decr_hits=0,
delete_misses=0, cmd_get=479525, total_connections=13088175,
curr_connections=920, uptime=2955153, auth_cmds=1479,
cmd_set=146544, rusage_user=4756.090448, curr_items=15466,
bytes_read=1856824151, cas_badval=0, get_misses=72976}}
t_dall.flush
= [true]
t_dall.stats
= {mc3.ec2.northscale.net:11211={bytes=88685654, cas_misses=0,
delete_hits=0, get_hits=406549, rusage_system=23117.65,
pid=7601, cas_hits=0, incr_misses=0,
connection_structures=1896, evictions=12902, threads=4,
limit_maxbytes=67108864, incr_hits=0, cmd_flush=11,
decr_misses=0, pointer_size=64, daemon_connections=10,
time=1295000178, conn_yields=0, engine_maxbytes=104857600,
version=1.4.4_188_g0117a2c, total_items=146562,
bytes_written=6622499298, rejected_conns=0, decr_hits=0,
delete_misses=0, cmd_get=479554, total_connections=13089214,
curr_connections=918, uptime=2955353, auth_cmds=1479,
cmd_set=146562, rusage_user=4757.580448, curr_items=15466,
bytes_read=1857585675, cas_badval=0, get_misses=73005}}
So the flush method since ineffective. How should we do this?
--
David Hall, M. Sc.
--
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: Is there a preferred method of packaging assets in a Rails 3 app on Heroku?
Another approach if you're packaging assets like this anyway would be to upload them to S3 instead of adding them to the app. You could then use S3 as an asset host, and even take advantage of CloudFront as a CDN. On Jan 13, 2011, at 12:49 PM, Trevor Turk wrote: On Thursday, January 13, 2011 1:35:27 PM UTC, John Beynon wrote: We use https://github.com/sbecker/asset_packager under Rails3 on Heroku - works great for us, Run a rake task locally to package after any changes to js/css, commit to git and then deploy Thanks for that. I've been playing with some stuff today, and came up with this: https://gist.github.com/778234 Basically, I can use rake deploy to deploy to heroku, and it caches the assets automatically. It's an interesting strategy, I think. I'm curious if you guys have any opinion. - 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. -- 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: Is there a preferred method of packaging assets in a Rails 3 app on Heroku?
I believe if you simply set the asset host in Rails, it will keep appending the timestamp at the end of the URLs it generates in your view. On Jan 13, 2011, at 12:55 PM, Trevor Turk wrote: On Thursday, January 13, 2011 5:51:42 PM UTC, David Dollar wrote: Another approach if you're packaging assets like this anyway would be to upload them to S3 instead of adding them to the app. You could then use S3 as an asset host, and even take advantage of CloudFront as a CDN. Yeah, I was thinking the same thing. I'd just have to figure out how to keep the timestamp thing in the view (e.g. javascripts/all.js?1294939289) I'll think about it some more. This is such a huge improvement for me already, though. Going from 10+ HTTP requests for this stuff to 2 really speeds things up. - 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. -- 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: Internal Server Error After a db:push
This appears to have been an issue in the taps server itself. Please try your push/pull again and it should be working now, sorry about that! -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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.
Marketing website hosting for Heroku apps
I'm sold on using Heroku for deploying my rails app. I would like to know what others in the community use for serving up regular marketing website pages? Even deploying a rails CMS seems like overkill with services like Weebly out there. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Best way to DB import 1M+ rows?
Another possible solution would be this: Upload your data in CSV/TSV/whatever form to S3. Write a rake task that does the following: * download from S3 to RAILS_ROOT/tmp * use the psql command line tool (it's on our dyno grid) or one of the ActiveRecord bulk import extensions to read the file and import to your database Then you can run it with heroku rake my_import_task If this is going to be a regular process, you'll likely want to wrap all of this up as something you can run from a worker using DJ or its' ilk. On Dec 10, 2010, at 10:51 AM, Zach Bailey wrote: Thanks John, that's a great suggestion. Unfortunately it's looking like it will take about 7.5 hours to import 3.12M rows: 1 tables, 3,123,800 records companies: 1% | | ETA: 07:25:34 I'm wondering if there's a more expedient route... in the past I've used the postgres COPY command [1] to do bulk imports of large data sets quickly, but that requires that the server be able to read a file off the server's local filesystem. I don't suppose that's feasible given how the Heroku platform works, but would love to be pleasantly surprised :) Anyone from Heroku able to pipe up and offer any other possible suggestions? Just to restate the problem, I have a single table with about 3.12M records that I'm wanting to transfer from a local DB to my remote Heroku DB without touching the other Heroku app data. It's ok if the table gets blown away on the Heroku side as it has nothing in it (new model I just added). Happy Friday, Zach [1] http://www.postgresql.org/docs/8.4/interactive/sql-copy.html On Thursday, December 9, 2010 at 4:36 AM, johnb wrote: If it's just a single table and you have it in a db locally then db:push --tables tablename would get it up to heroku - but this will replace the contents of the remote table with the local table and not append to it. If the application is live you could put it into maintenance mode, db:pull --tables tablename append your rows to it and then push the table back and put the app live... perhaps? John. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Running a daemon process on Heroku
A Heroku worker is essentially this:
If you create a process in your app that is started by running rake jobs:work
we will keep it running. If you want to consume the Twitter firehose with that
process, it should work great. You can also use DJ, Resque, etc as your
implementation of rake jobs:work
On Dec 8, 2010, at 3:02 AM, jurglic wrote:
Hello Guys,
This is a very interesting topic, I'd also like to know more about it.
I was quite sure this wouldn't work, because you probably don't have
rights to start off a deamon in a worker. Has anyone tried it yet? Or
maybe any official answer from Heroku Team?
I was thinking of using something like that for Twitter Firehose API,
because otherwise I really don't know any way to consume twitter feed
in realtime on Heroku..
Cheers, Uros
On 8 dec., 08:09, Chris Hanks christopher.m.ha...@gmail.com wrote:
Well, since you pay for workers by the hour, I'm sure Heroku would be
perfectly happy with you keeping many of them busy for a very long
time.
On Dec 7, 10:44 pm, Jonas jo...@jonasbnielsen.dk wrote:
Nice. So that was actually what I initially thought.
And there is no limitation on what that worker does? I mean, it's okay
to preoccupy that worker till eternity? :)
On 7 Dec., 20:53, David Dollar da...@heroku.com wrote:
A Heroku worker is simply running rake jobs:work on your app so whatever
happens behind that rake task is up to your app.
On Dec 7, 2010, at 10:47 AM, Jonas jo...@jonasbnielsen.dk wrote:
Hi guys,
Hi guys,
Ok, so I've succesfully developed a daemon that fires up EventMachine,
subscribe to a data feed and communicate that data to Pusherapp.com
Everything is working beautifully in production on my OSX development
machine, and now I want to deploy to Heroku. My initial understanding
was that the Heroku workers would suite this purpose well, however
I've come to realize that I might be wrong.
My question is, how do I run a daemon in the Heroku environment?
Some facts:
Ruby 1.9.2
bamboo-mri-1.9.2 (beta)
Rails3
Daemons gem:https://rubygems.org/gems/daemons
The deamon_generator plugin:https://github.com/dougal/daemon_generator
An old Railscast that describes approx. how a daemon like this is set
up:http://railscasts.com/episodes/129-custom-daemon
How the daemon works:
I've setup a rake task to start the daemon, briefly, this is the
process:
1. Rake task calls lib/daemons/my_daemon_ctl start
2. Require some gems and start daemon: Daemons.run
File.dirname(__FILE__) + /my_daemon.rb, options
3. Loads rails env and starts the EventMachine reactor:
EventMachine::run { data feed and pusherapp black magic here }
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit this group
athttp://groups.google.com/group/heroku?hl=en.
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@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.
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@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: Running a daemon process on Heroku
A Heroku worker is simply running rake jobs:work on your app so whatever
happens behind that rake task is up to your app.
On Dec 7, 2010, at 10:47 AM, Jonas jo...@jonasbnielsen.dk wrote:
Hi guys,
Hi guys,
Ok, so I've succesfully developed a daemon that fires up EventMachine,
subscribe to a data feed and communicate that data to Pusherapp.com
Everything is working beautifully in production on my OSX development
machine, and now I want to deploy to Heroku. My initial understanding
was that the Heroku workers would suite this purpose well, however
I've come to realize that I might be wrong.
My question is, how do I run a daemon in the Heroku environment?
Some facts:
Ruby 1.9.2
bamboo-mri-1.9.2 (beta)
Rails3
Daemons gem: https://rubygems.org/gems/daemons
The deamon_generator plugin: https://github.com/dougal/daemon_generator
An old Railscast that describes approx. how a daemon like this is set
up: http://railscasts.com/episodes/129-custom-daemon
How the daemon works:
I've setup a rake task to start the daemon, briefly, this is the
process:
1. Rake task calls lib/daemons/my_daemon_ctl start
2. Require some gems and start daemon: Daemons.run
File.dirname(__FILE__) + /my_daemon.rb, options
3. Loads rails env and starts the EventMachine reactor:
EventMachine::run { data feed and pusherapp black magic here }
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@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.
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@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: db:pull = Internal server error
Give this another shot on Ruby 1.9, it should be fixed now. Thanks, David On Nov 30, 2010, at 1:10 AM, Emanuele Tozzato wrote: problem solved using ruby 1.8.7, but I am sure I successfully used more recent versions.. Did I miss any update? -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: MySQL server has gone away Amazon RDS
I'm getting PGLostConnection type situations on our dedicated DB too lately. Have no idea if its related. On 11/26/10 6:31 AM, Russell Quinn wrote: I've occasionally getting MySQL server has gone away errors from my app running on Heroku (with the Amazon RDS add-on.) I'm guessing I need to adjust some packet size or timeout parameter. Does anyone have reliable information on what I should do? Thanks, Russell. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: hostname: Unknown host
I haven't seen the error but try `heroku ps` to see if it's running or still crashing. And yes, I experience the same problems in stability and I'm not sure that I've ever talked to a support staff in 4 days. Usually because after a couple days, I send in a follow-up with nevermind, got it and they close the ticket for me. They should just have the support email set to supp...@comcast.com /david. On Nov 16, 10:01 pm, Thawatchai Piyawat thawatc...@gmail.com wrote: My app is crashed since yesterday. The log show hostname: Unknown host. I believe this is Heroku's problem. However, it's more than a day, it's still not fixed now. It seems odd. I've submitted a support request. However, according to my experience, Heroku support is slow. Heroku seems like a good service. However, their stability and support staff need quality improvement. Anybody has the same problem as mine? Thawatchai -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Automating pgbackups
I threw this together to help out a bit automating your PGbackups. https://github.com/ddollar/heroku_backup_task On Nov 16, 2010, at 1:44 PM, Andrew C. wrote: I spin up an EC2 instance from my cron job. The EC2 instance captures and downloads the backup to S3, then shuts itself down. Works well so far. Obviously, it's not free, but it's freaking cheap. On Nov 16, 10:24 am, Peter van Hardenberg p...@heroku.com wrote: On Tue, Nov 16, 2010 at 2:29 AM, Trevor Turk trevort...@gmail.com wrote: Are there plans to offer an automated solution? Definitely. Is there a way to do this now? I've tried to put the Heroku gem into my Gemfile and then execute the command from the console, but that doesn't seem to work. I've been trying to think of other ways to run the pgbackups with the cron addon, but I haven't come up with anything yet. Any ideas would be most appreciated. Check out the --expire flag on pgbackups:capture. I'm not the expert on the subject, but with a bit of work you can probably find a way to use the heroku gem from inside a heroku cron job. -pvh -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Ubuntu 10.10 (amd64) + rails 3.0.1 + heroku uninitialized constant error
I just pushed out a new version of the heroku gem that should fix this. Let me know if you're still seeing issues. Thanks, David On Nov 16, 2010, at 9:40 AM, Mateus wrote: No, I didn't work. I googled for possible errors involving rails 3 and PostGres gem. It gave me something related to bundle, and then that I don't have to do nothing about it on rails 3. Oh, I look for it on the Gemfile, it isn't there, and just adding gem 'postgres' don't help. Or I could be doing something wrong. Anyway, still with the problem. On 16 November 2010 14:18, Abel Tamayo abel.tam...@gmail.com wrote: I think the following line: /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.13.1/lib/heroku/commands/pg.rb:8:in `class:Pg': uninitialized constant Heroku::Command::Pg::Help (NameError) gives away that the culprit could be the PostGres gem. Makes sense too since it's one of the things Heroku uses but you don't usually need it in your development environment. You should probably check to see if it's correctly listed in your Gemfile. Hope that helps. On Tue, Nov 16, 2010 at 3:07 PM, Mateus mcavanh...@gmail.com wrote: Hi guys Few months ago I start to study Ruby on Rails. At the time, I was using the version 2.x of Rails (Don't remember which exactly) and it was working fine. (running on Ubuntu 9.04) I get some troubles and personal problems and I stop with rails. Now, I update my ubuntu to 10.10 and install the Rails 3 (rails 3.0.1, ruby 1.9.2p0). But, when I just start to use and I was to deploy my app to heroku, I get the following error: /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.13.1/lib/heroku/commands/pg.rb:8:in `class:Pg': uninitialized constant Heroku::Command::Pg::Help (NameError) from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.13.1/lib/heroku/commands/pg.rb:5:in `module:Command' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.13.1/lib/heroku/commands/pg.rb:4:in `top (required)' from internal:lib/rubygems/custom_require:29:in `require' from internal:lib/rubygems/custom_require:29:in `require' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.13.1/lib/heroku/command.rb:5:in `block in top (required)' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.13.1/lib/heroku/command.rb:5:in `each' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.13.1/lib/heroku/command.rb:5:in `top (required)' from internal:lib/rubygems/custom_require:29:in `require' from internal:lib/rubygems/custom_require:29:in `require' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.13.1/bin/heroku:7:in `top (required)' from /usr/local/bin/heroku:19:in `load' from /usr/local/bin/heroku:19:in `main' This happen with every single heroku command I try. I try google for it, and even check something with gem environment, which give the following: RubyGems Environment: - RUBYGEMS VERSION: 1.3.7 - RUBY VERSION: 1.9.2 (2010-08-18 patchlevel 0) [x86_64-linux] - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.9.1 - RUBY EXECUTABLE: /usr/local/bin/ruby - EXECUTABLE DIRECTORY: /usr/local/bin - RUBYGEMS PLATFORMS: - ruby - x86_64-linux - GEM PATHS: - /usr/local/lib/ruby/gems/1.9.1 - /home/cavanholi/.gem/ruby/1.9.1 - GEM CONFIGURATION: - :update_sources = true - :verbose = true - :benchmark = false - :backtrace = false - :bulk_threshold = 1000 - REMOTE SOURCES: - http://rubygems.org/ As I look for some answer to my problem, this was all I could get. And, for me, it seen fine. (I'm kind of noob with linux, so sometimes I don't get the problem) When I installed the gem, its been everything fine, no errors at all. I wonder what can I do to solve this problem, since I cannot add the SSH Key. Even the command heroku help don't work. thx for the time and help, and sorry if I'm asking in the wrong place -- Mateus Cavanholi -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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. -- Mateus Cavanholi -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group
Re: Custom error pages, we *really* need them
I've suggested in the past having a separate branch in your repo called errorpages or something, which has a few static HTML pages. Push that branch to Heroku, and it can use those files to serve errors. On Wed, Sep 15, 2010 at 7:58 AM, Daniel Spangenberg daniel.spangenb...@googlemail.com wrote: I like the idea too, but maybe I don't wan't to set up an extra heroku app or shared host for an static html page only, maybe it would be nice if you can choose to take the iframe and a textinput, where you can insert plain html. Daniel Am 15.09.2010 um 16:55 schrieb Adrian Cuadros: + 1 on this also. like the idea about the iframe On Wed, Sep 15, 2010 at 9:02 AM, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote: +1 Maybe the generic page could be a fail Koi On Wed, Sep 15, 2010 at 7:31 AM, Daniele to...@vitamino.it wrote: Hi, as you can see from the status page in the past 2 days Heroku had a lot of problems that resulted in Timeout connection and Backlog Too Deep error pages. This two pages have a message specifically addressed to the administrator that is not acceptable in a production site. We need to have personalized pages. Same logic about the Heroku Ouchie Page of course! If this is not possible immediately a quick hack could be to have a really generic white-label page (multilingual would be appreciated) and put all the system message in an html comment. We are tech guys, right? Is not a problem to look at the source to find out what is happening. This seems clever that show a ugly error message to everyone. Finally as I already suggested in another discussion: A simple solution for more personalization without the need to access any preferences could be to have a full page iframe inside the heroku's error page pointing to http://error .heroku_app_domain.tld/http_error.html The admin has to create a third/fourth level domain, point it to a different server and create the personalized pages. So every application can have an error page/backup application to handle the down. A js can check for the domain existence and switch to a plain txt message if it is not set. I'd love to get feedback on these ideas by Heroku guys. Thank you. Daniele -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- Adrian Cuadros adr...@rutanet.com (+521) 8116848310 -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Problems deploying an EventMachine + Sinatra application
There are a couple of issues with this code fragment on Heroku: * Your config.ru needs to set up and call run on a Rack-compatible application * All Heroku dynos are given one port, passed to thin, so you won't be able to have Websockets listening on an alternate port. Cheers, David On Aug 27, 7:15 am, Jose M. robe5@gmail.com wrote: Hello! I am trying to deploy an EventMachine + Sinatra application. I am getting the next error when pushing the code: Launching.. .timed out ! App timed out during testfire. The previous version of your app is still running. ! Backtrace follows: ! == Sinatra/1.0 has taken the stage on 4567 for production with backup from Thin ! Thin web server (v1.2.7 codename No Hup) ! Maximum connections set to 1024 ! Listening on 0.0.0.0:4567, CTRL+C to stop ! Stopping ... ! Thin web server (v1.2.7 codename No Hup) ! Maximum connections set to 1024 ! Listening on 0.0.0.0:46785, CTRL+C to stop ! Heroku push rejected, app timed out during testfire error: hooks/pre-receive exited with error code 1 Is it trying to run Thin twice? I am running the sinatra app inside an event machine loop with another app using event machine sockets and I am doing it like this: #config.ru require './app.rb' #app.rb require 'rubygems' require 'bundler/setup' require 'em-websocket' require 'sinatra/base' require 'thin' EventMachine.run do class Websockets Sinatra::Base #sinatra app code end EventMachine::WebSocket.start(:host = 0.0.0.0, :port = 8080, :debug = true) do |ws| # websocket server code end Websockets.run! end Am I doing something wrong? Is not possible for this kind of application to run in heroku? Thanks in advance! -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: free vs. paid heroku app performance
It's in the best interest of any web site operator to know when their web site is down external from your hosting company regardless of platform, language, or baseline hosting provider's functionality. When I get a phone call at 2am that the web site is down, I should already be on it. It just happens that it has the same benefits for spun down processes. I understand where you're coming from in regards to all the free sites but most likely the operators of those sites are leveraging Varnish and site monitoring is simply going to hit the same cached route. We can only work with what we have, if they want it done differently - give us the option. Besides, I pay plenty a month for it to work in my situation. /david. On Aug 27, 10:52 am, Stefan Wintermeyer stefan.winterme...@amooma.de wrote: Am 27.08.2010 um 15:27 schrieb David: That's what we do, setting up site monitoring is part of my normal routine so I have something checking the site every 5 mins including staging. I think that might not be in the best interest of the Heroku guys. If they wanted it that way they'd have built it in. Stefan -- AMOOMA GmbH - Bachstr. 126 - 56566 Neuwied -- http://www.amooma.de Geschäftsführer: Stefan Wintermeyer, Handelsregister Montabaur B14998 Asterisk 1.6:http://das-asterisk-buch.de Ruby on Rails 3:http://ruby-auf-schienen.de Videos and slides of AMOOCON:http://amoocon.de -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: free vs. paid heroku app performance
That's what we do, setting up site monitoring is part of my normal routine so I have something checking the site every 5 mins including staging. A couple free options: http://aremysitesup.com/ http://www.uptimerobot.com/ And when you're ready for the big time: http://pingdom.com/ (though I'll gladly hi-jack this thread if someone has better suggestions...) /david. On Aug 26, 3:04 pm, Shane Witbeck sh...@digitalsanctum.com wrote: Can't you set something up to request a page on the app every so often to simulate traffic? I ran into the same issue on Google App Engine and did this to prevent the resources behind my app to not wind down. On Thu, Aug 26, 2010 at 2:32 PM, Eric Anderson e...@pixelwareinc.comwrote: On 08/26/2010 11:30 AM, marcel wrote: Also, it often takes 10-20 seconds to get a page to load after a period of inactivity, compared to lightning speed for the production app. If you are using the free heroku plan they do spin down the single dyno when not in use. This makes sense as probably a LOT of those apps are just something someone was playing with and does not use on a regular basis. Also if they are not getting paid you can understand them wanting to minimize resources. OTOH if you pay for at least 2 dynos then they NEVER spin down meaning your app is always nice and responsive even if nobody has it it for a while. I WISH they offered the ability to purchase 1 persistent dyno. I don't really need two (my app is lightly used) but I don't want the startup delay. Seems if they offered 1 dyno that was persistent for $5-15/month that would lower the barrier to entry for becoming a paying customer and allow them to offer a single persistent dyno without dragging their profit down. Eric -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- -Shane -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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 Console and Gems
Not necessarily. .gems is deprecated IIRC, and only tells Heroku what to install. Your Rails app has to define gems in config/environment.rb w/ config.gem directives. Alternatively, switch to Bundler + Gemfile, and manage gems in one place. On Fri, Aug 27, 2010 at 1:35 PM, Scott LaBounty slabou...@gmail.com wrote: Should the gems that are in my .gems file be available to me in the Heroku console? Are they available from my rakefile? Thanks, -- Scott http://steamcode.blogspot.com/ -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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 Console and Gems
I believe so, as long as the Rakefile + your app loaded Bundler. On Fri, Aug 27, 2010 at 1:44 PM, Scott LaBounty slabou...@gmail.com wrote: Hmm... I'm not using Rails. If I do make the switch to Bundler/Gems would the gems be available via rake and the console? Scott On Fri, Aug 27, 2010 at 1:37 PM, David Balatero dbalat...@gmail.comwrote: Not necessarily. .gems is deprecated IIRC, and only tells Heroku what to install. Your Rails app has to define gems in config/environment.rb w/ config.gem directives. Alternatively, switch to Bundler + Gemfile, and manage gems in one place. On Fri, Aug 27, 2010 at 1:35 PM, Scott LaBounty slabou...@gmail.comwrote: Should the gems that are in my .gems file be available to me in the Heroku console? Are they available from my rakefile? Thanks, -- Scott http://steamcode.blogspot.com/ -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- Scott http://steamcode.blogspot.com/ -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Subdomain set up?
You need to have the custom domain add-on with your desired domain. remix.tricil.net needs to be a CNAME pointing to proxy.heroku.com That's it! David On Aug 18, 2010, at 2:55 PM, tricil tri...@gmail.com wrote: Ok, so I have a site that's my main website: http://tricil.net this has to stay the same. my heroku app is currently http://cold-sunset-12.heroku.com and i want the URL for it to be http://remix.tricil.net I looked into wildcard domains, and pointed remix.tricil.net to heroku.com, filled in the command line and it just loads heroku.com. the homepage not my app. should i just try and use DNS with zerigo? it wants to change the nameservers, and that can't change for it would mess up my main site. so confused. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: how to use a command-line utility?
On Wed, Aug 11, 2010 at 3:43 PM, Richard Conroy richard.con...@gmail.comwrote: On Mon, Aug 9, 2010 at 6:41 PM, Jacob Hodes jho...@gmail.com wrote: Hi, I'm developing a Rails app that makes use of a command-line tool called Graphviz (http://www.graphviz.org). Changes get made in the Rails app, then a background job is fired which runs graphviz as a system command. graphviz generates a graph and saves it to a file. Then I upload the file back into my Rails app. I know Heroku's filesystem is read-only, no ssh access, etc. Given these limitations, what's the best approach to take? I see I can use S3 for file storage. But how about finding a way to use this command-line utility? I'm highly doubting Heroku would install such a thing, right? Any alternative ideas? One idea I can think of is to wrap GraphViz in a web service and install it in a seperate hosting service. To this end, you can always spin up an EC2 instance. Since Heroku dynos are hosted on EC2, you can talk to any other machines over private IP addresses. You just need to allow the Heroku security group. An alternative idea: Heroku lets you use sqlite/memory databases. Its not a supported option, but they do work, and I would say the limitations are severe (I doubt Delayed Jobs would see them). You could upload the information that GraphViz needs to process into the DB. I am uncertain how you could get the GraphViz CLI app to use it, but perhaps GraphViz has a library/gem which has less restrictive use? Thanks for your thoughts, Jacob -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- http://richardconroy.blogspot.com -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Workflow to allow heroku to install a 'private' (local) gem on deploy
If Bundler is running on Heroku, the Heroku UNIX user account needs to have its public key in your Github repo as an authorized key. Each Heroku machine will have a different SSH key generated, and you non-deterministically deploy to some machine in the Heroku cloud each time you deploy. Even if you had a consistent SSH key, it would be insecure for you to add that key to your public repo, as anyone else deploying to the same machine as you would be able to download your code repo. On Wed, Aug 11, 2010 at 5:34 PM, Bradley bradleyrobert...@gmail.com wrote: Right, so I added in: Host heroku.com ForwardAgent yes to my Tomcat user's ~/.ssh/config. This is the user that checks out from Github then pushes to heroku. I still get the same error, Permission denied (publickey). Can you explain how this is supposed to work? I'm confused as to how Heroku would know that it can forward this gem fetch request through my tomcat user on my server? (if that's what's supposed to happen, I'm still pretty confused as to what this should accomplish) Thanks, Brad On Aug 11, 1:03 am, Matthew Todd matthew.t...@gmail.com wrote: On Aug 10, 2010, at 8:28 AM, Matthew Todd wrote: Host heroku.com ForwardAgent yes On Aug 11, 2010, at 7:34 AM, Bradley wrote: this should be added to the github user's ssh config? No, to the ssh config of any *local* user (having access to your private GitHub repository) who needs to run git push heroku to deploy. Cheers, -- Matthew -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Workflow to allow heroku to install a 'private' (local) gem on deploy
If you could package a custom SSH pub/private keypair with your Gemfile, you could then: 1) Add that pub key to Github 2) Set the :git source in the Gemfile for your private gem to point at your private SSH Github URL. However, I don't believe Bundler supports having an embedded public/private keypair. It would be an interesting patch, though. Currently, I just script/plugin install --force my private plugin from Github every time I update it, which I hate. - David On Mon, Aug 9, 2010 at 11:55 AM, Andrew C. andrew.c...@gmail.com wrote: You can vendor the gem too. On Aug 9, 9:44 am, Bradley bradleyrobert...@gmail.com wrote: Ya I'm just wondering the best way to reference this gem. For instance, the gem location will be different on my local machine during dev as on my CI machine during build/deploy. I'm using github and I've noticed that Bundler can use :git as a source, I assuming Heroku's deploy does this the Gem bundling locally before pushing, so maybe my best bet is to use that repo as the source and as long as my CI server has access to that private github repo, all should be gravy? On Aug 8, 9:34 pm, Michishige Kaito chris.webs...@gmail.com wrote: El 08/08/10 22:23, Bradley escribi : I'm writing a new app that uses a custom gem not publicly available on gemcutter, or anywhere for that matter. I'm building both the app and gem with Hudson CI, then I'd like the app pushed to heroku by somehow installing this gem and pushing. I'm a bit confused as to how I might do this. Do I want to bundle package? Will heroku then install the gem from vendor automatically? How do I have environment specific dependencies that work with Heroku? For instance while in development, i want to use my local gem, but in Hudson I want to package the locally built gem from hudson, then push my app to heroku. I don't want these gems available publicly which is why I'm looking for a good way to package the gem for my Heroku app to be able to use it appropriately. Doe this make sense? Any suggestions/help is greatly appreciate. **setup** Hudson 1.368 Git 1.5.6.5 Bundler 1.0.0RC2 Heroku Stack bamboo-mri-1.9.1 Rails 2.3.8 If you're using bundler, you can just push the gem file along with the rest of your app. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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.
