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: 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: 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: 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: 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.
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.
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.
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: 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.
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.
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: 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.
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.
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: 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: 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.
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: 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: 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: Repeated::Job cannot find Delayed::Job
Make sure the delayed_job plugin has been pushed to your app (that there is no .git subdirectory inside it masking the files) You can try to clone your app from heroku into /tmp to see a pristine state of what is in Heroku's repo. cd /tmp git clone g...@heroku.com:myapp.git On Aug 5, 2010, at 11:56 AM, Russell Quinn wrote: I'm trying to get these two things working together. Delayed::Job is installed, has the migrations and there's a background worker running, etc. However, Repeated::Job can't find it on start-up. I've tried explicitly setting the plugin load order in Rails (although they're alphabetically correct anyway,) but this doesn't help. Does anyone have any ideas? Here are my logs from straight after a slug launch. Both canary-1684341.log and dj-1891287.log complain about Repeated::Job (erroneously called Repeated::Cron in the error message from the plugin's init.rb) not finding Background::Job. Thanks, Russell. - == exceptional.log == # Logfile created on Thu Aug 05 08:50:01 -0700 2010 by logger.rb [INFO] (init.rb:18) Thu Aug 05 15:50:01 UTC 2010 - Loading Exceptional for 2.3.8 == newrelic_agent.log == # Logfile created on Thu Aug 05 08:50:02 -0700 2010 by logger.rb [08/05/10 08:50:02 -0700 railgun64.30863 (8200)] INFO : Dispatcher: thin [08/05/10 08:50:02 -0700 railgun64.30863 (8200)] INFO : Application: X-XX [08/05/10 08:50:02 -0700 railgun64.30863 (8200)] INFO : New Relic RPM Agent 2.12.3 Initialized: pid = 8200 [08/05/10 08:50:02 -0700 railgun64.30863 (8200)] INFO : Agent Log found in /disk1/home/slugs/232258_d8f7c76_6525/mnt/log/ newrelic_agent.log == production.log == # Logfile created on Thu Aug 05 08:50:01 -0700 2010 == canary-1684341.log == Exception encountered, Repeated::Cron not loaded uninitialized constant Delayed::Job ** [NewRelic] New Relic RPM Agent 2.12.3 Initialized: pid = 8200 ** [NewRelic] Agent Log found in /disk1/home/slugs/232258_d8f7c76_6525/ mnt/log/newrelic_agent.log Thin web server (v1.2.6 codename Crazy Delicious) Maximum connections set to 1024 Listening on 0.0.0.0:3693, CTRL+C to stop == production.log == # Logfile created on Thu Aug 05 08:50:11 -0700 2010 == dj-1891287.log == (in /disk1/home/slugs/232258_d8f7c76_6525/mnt) Exception encountered, Repeated::Cron not loaded uninitialized constant Delayed::Job -- 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: Koi DB upgrade
Koi database upgrades happen immediately. A Koi is the same as a Blossom, with a higher space quota. - David On May 21, 2010, at 2:34 AM, fbjork wrote: Hi, anyone who knows how long it usually takes to get a Koi DB upgrade done? I've waiting several days now and no reply from support regarding the issue. Cheers, Fredrik -- 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 handle scheduled events?
Also take a look at http://github.com/ddollar/repeated_job - David On May 17, 2010, at 3:58 PM, Steve Wilhelm wrote: Take a look at Background Jobs / Workers at http://docs.heroku.com/background-jobs - Steve W. On May 17, 7:36 am, Jim Jones jjones35...@yahoo.com wrote: I'm new to Heroku and am trying to figure how I would accomplish the following? I've got an Events table that stores the date an event is to occur. I'd like to automatically send out an email to a user when that event is close (ie. 1 day away, 1 hour away, 15 minutes, etc). How would I do this with Heroku? I was thinking I could have a cron job run every minute, that searches for events that are coming up, but it looks like I can only use hourly cron jobs, which would miss my 15 minute requirement. Any thoughts? Thanks. -- 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: Corrupted database
On Mar 18, 2010, at 11:23 PM, Mike wrote: I'm not really sure why, but now it thinks it's on version 0 of the database, even while it already has all of the tables from the full migration set. This leaves me unable to perform another db:migrate VERSION=0, and attempts to do so error out as it tries to create my first migration for some reason. My guess is that you CTRL-C'd out before the schema_migrations table got copied. The contents of this table are how Rails knows which migrations have been applied. I'm unable to perform either db:migrate:reset or db:reset because I do not have drop permission on the database. heroku db:reset(not heroku rake db:reset) What procedure should I follow to clear out the database? Also, is this type of corruption always going to happen if a db:push is canceled part way through? If my guess is correct and the corruption is just caused by the missing schema_migrations data, then it will happen if you CTRL-C before that. I wouldn't really call it corrupt, just incomplete. You could either reset and repush, or probably just start another push on top of this one. Hope this helps, David -- 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: Problem with Net::HTTP.getResponse only in heroku
Twitter rate-limits the the Search API, more details can be found here: http://apiwiki.twitter.com/Rate-limiting If you use a custom User-Agent request header, the rate-limiting is less severe. You may want to give that a shot. Hope this helps, David On Mon, Mar 1, 2010 at 12:41 PM, Daniel Lopes danielvlo...@gmail.com wrote: It's the first time I try heroku but it became a big headache. I did a really simple sinatra app but when I try to run it on heroku instead of my local machine or another host it break without any reason. The problem happens when I try to access Net::HTTP.get_response ... take a look: response = Net::HTTP.get_response(URI.parse(http://search.twitter.com/ search.json?rpp=100q=%23promorails)) Local Machine: daniellopes:~/Works/twicket/twicket (master)$ irb response = Net::HTTP.get_response(URI.parse(http://search.twitter.com/search.json?rpp=100q=%23promorails;)) = #Net::HTTPOK 200 OK readbody=true exit daniellopes:~/Works/twicket/twicket (master)$ heroku console Ruby console for twicket.heroku.com response = Net::HTTP.get_response(URI.parse(http://search.twitter.com/search.json?rpp=100q=%23promorails;)) = #Net::HTTPBadRequest 400 Bad Request readbody=true I dig deep in the docs but can't found anything related to this. Somebody have any idea what it can be? -- 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: Better logging feedback
Give it a try now, we just pushed out some fixes to the Exceptional integration. On Thu, Feb 25, 2010 at 10:05 PM, Gustavo Beathyate r...@obviamente.pe wrote: I haven't been able to install exceptional for over a week. I keep getting internal server error messages… On Feb 25, 2010, at 21:25 , Oren Teich wrote: Nothing else from anyone? This comes up all the time - is exceptional sufficient? Oren On Thu, Feb 25, 2010 at 8:21 AM, Oren Teich o...@heroku.com wrote: Rails doesn't show SQL queries when running in production mode. New Relic is your best bet for seeing this stuff, regardless of platform. 404 is an interesting one. Thanks! Other issues with logging today? Bueller? Oren On Thu, Feb 25, 2010 at 3:59 AM, Jamie Lawrence hopel...@gmail.com wrote: Two things which I've encountered that might be solved by better logging: 1. I'd like the option to see the actual SQL queries (just temporarily). Sure you can pull in the production database and test locally but it's slow and awkward. Particularly as the DB size grows, it becomes impractical 2. 404 errors fall outside the Hoptoad/Exceptional responsibility and that's something that I'd like to check for occasionally. Something like an errors.log file. One other thing: some people seem to want to archive their log files (for whatever purpose - I'm not one of them) and perhaps dumping them out to an S3 account daily would satisfy their needs (possibly for an additional charge) Having said all that, I think I've adapted to the Heroku way and can fix most problems from the Hoptoad report. Jamie On Feb 25, 3:59 am, Oren Teich o...@heroku.com wrote: One of the top requests we've had is for better logging. I'm looking for specific feedback on the problems you've run into, and who better logging would help you solve your problems. While there are of course obvious cases, I want to make sure we get some real use cases straight from you guys . Either here or off-list, I'd like to start a discussion on the problems you've run into with Heroku logs, limitations of solutions like exceptional or hoptoad, and what you'd like to see from Heroku when you think of logs. Thanks, Oren -- 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. -- 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: Delayed jobs failing with suspicious backtrace
New Relic is aware of the issue and has a fix so it just has to make it out to the gem. I'd imagine a few days at most. On Fri, Feb 19, 2010 at 6:42 PM, Doug Petkanics petkan...@gmail.com wrote: I had this issue this week and Heroku support suggested I disable New Relic add-on since their updated gem didn't play nice with Delayed Job. I did, and it immediately started working again. Heroku guys, any idea when we'll be able to re-enable New Relic? On Fri, Feb 19, 2010 at 6:38 PM, Higgaion brianpatrickd...@gmail.com wrote: My jobs don't seem to be running automatically, so I tried to start a worker with heroku rake: heroku rake --trace jobs:work (in /disk1/home/slugs/125600_b30055f_55f0/mnt) ** Invoke jobs:work (first_time) ** Invoke merb_env (first_time) ** Execute merb_env ** Invoke environment (first_time) ** Execute environment ** Execute jobs:work rake aborted! undefined method `info' for nil:NilClass /disk1/home/slugs/125600_b30055f_55f0/mnt/vendor/plugins/rpm/lib/ new_relic/delayed_job_injection.rb:18:in `initialize' : : Two general categories of questions come to mind: 1) What is that new_relic thing trying to do? where is the source code for that? what info? where am I? 2) How to I fix it? -- 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: Net::SMTPAuthenticationError when sending mail from console using Sendgrid
We have an issue with a handful of apps not picking up their credentials correctly. If you're running into this issue, try removing/re-adding your Sendgrid addon so that it picks up the proper authentication credentials. - David On Mon, Jan 25, 2010 at 11:24 AM, Simon Starr si...@starr.cx wrote: Oops, that should be 'heroku config' On Jan 25, 4:23 pm, Simon Starr si...@starr.cx wrote: They're stored as environment variables (SENDGRID_USERNAME SENDGRID_PASSWORD) so you can find them with 'heroku console' -- 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: error installing heroku gem (ruby 1.9 / mac os x)
I'm currently working on getting the heroku gem running on as many platforms as possible. If anyone would like to get involved in this effort, the gem is open source at http://github.com/heroku/heroku - David On Fri, Jan 8, 2010 at 2:32 AM, dan mr.dan.ma...@gmail.com wrote: i was looking forward to giving heroku a try but am worried about the attention this issue is getting. there are no ways to submit this issue using the heroku website as i do not have a running heroku app yet. if this issue is not even acknowledged, i will have to try other hosts with better support mechanisms. -- 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: Default rails landing page won't go away.
Try the following git rm public/index.html git commit -m remove default index page git push heroku - David On Fri, Jan 8, 2010 at 9:15 AM, JGrubb therealjohnnygr...@gmail.com wrote: I'm a complete and utter nooby, though not so new that I haven't run a search or five on this list to find if anyone else is having this problem. I'm getting my feet wet with Heroku, Rails, and Git all at the same time. I've got a couple of little projects going, each of which have had the standard index.html deleted and the map.root = 'where_I_want_it_to_go', but for some reason, upon visiting the root URL of my apps in Heroku, the Welcome to Rails page shows up. Needless to say it works fine locally. The weirder thing is that my very first project was a blog that I pushed up about 2 weeks ago. The landing page has since disappeared on it's own without any intervention on my part (that I can remember). What am I doing wrong? thanks, all... 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.
Re: Upload file and process in DJ
Maybe, but there's no guarantee of that. The dyno that received the request may be running on a totally different server than the worker that processes it. In this case, you should upload the file to S3, then download from S3 in the worker for processing. Hope this helps, David On Fri, Jan 8, 2010 at 1:37 PM, Karl threadh...@gmail.com wrote: My app uploads a file (via paperclip), and saves the file in :rails_root/tmp/:id/:basename.:extension. Works perfectly. After the file is successfully received and saved in tmp, I need to run a script on it that may take 30-60 seconds. For now I just process this within the current request cycle. I know that files stored in tmp will, eventually, be deleted. In my case, I *want* them to be deleted, after they are processed. If I wanted to use Delayed Job to process this file, will DJ still find the file as it is saved in tmp? Consider that the file should be processed immediately after it is uploaded, there is no need to wait for some time in the future. -- 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: Upload file and process in DJ
This wouldn't work on Heroku because even though it's in a different thread it's still the same request, and we only allow requests to go for 30s. This would tie up your dyno for the background request. - David On Fri, Jan 8, 2010 at 2:08 PM, Karl threadh...@gmail.com wrote: On rufus-scheduler, it looks like it simply creates a new ruby thread: class PlainScheduler SchedulerCore def start �...@thread = Thread.new do loop do sleep(@frequency) self.step end end end end Would this remain on the same dyno as the initializer? -- 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: Accidental 'heroku db:reset'
With db:reset you get a scary prompt asking you if you're sure. This is a good suggestion though. - David On Fri, Jan 8, 2010 at 9:00 PM, Ryan Heneise r...@donortools.com wrote: I should have put PREVENTING accidental 'heroku db:reset' - no, I haven't done this yet. But I have nightmares about it. On Jan 8, 8:59 pm, Ryan Heneise r...@donortools.com wrote: I was wondering if there's a way to turn off 'heroku db:push', or some way to obscure the command. The reason I'm asking is because I am deploying a second app to Heroku, and I was just thinking to myself, gosh, if I accidentally typed 'heroku db:push' or 'heroku db:reset' on my other app, all my data would be toast. So is there a way to turn that feature off, or keep that from happening? -- 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: error installing heroku gem (ruby 1.9 / mac os x)
Anyone using Ruby 1.9 feeling adventurous? Clone git://github.com/heroku/heroku.git, run rake spec, and let me know if you're green or not. - David On Fri, Jan 8, 2010 at 12:24 PM, Devyn Cairns devyn.cai...@gmail.com wrote: Why can't you guys just give an option in the app config for the Ruby version? We can already set gem versions for the app in the .gems manifest. Doesn't this make sense? Just my two cents. -- ~devyn -- 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: Question about Heroku Workers
Hey there, Like dynos, a worker is charged while it is active whether or not there is work for it to do. - David On Wed, Jan 6, 2010 at 1:19 AM, Yuri Niyazov yuri.niya...@gmail.com wrote: I installed DJ into my app, and ran heroku workers 1 My question is: do I get charged for having a worker up and available for processing, or do I get charged only when the worker actually has some work to do? -- 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: New Relic support for Merb
Hey Andy, We're currently looking into allowing non-Rails applications to use the New Relic addon. I've currently got it working on a Sinatra application, but now we need to package that up and get it into production. Unfortunately I don't have an ETA yet, but we're working on it :) As far as a manual install, it is possible. If you run heroku config --long on your application with the NR addon installed, you can see some New Relic configuration parameters that you'd need to set up the configuration file. - David On Wed, Dec 23, 2009 at 8:29 AM, Andy Shipman a...@cllearview.com wrote: I'm running a Merb app and would like to use New Relic. Currently, I can do this myself - i.e. add it to my app as a gem dependency - rather than via the Add On (as that is Rails only, apparently) but I'm concerned that this might not work right across multiple dynos. That plus the fact the Bronze level of New Relic is part of the Heroku setup makes me ask whether there are plans for direct New Relic Merb support? If not, am I likely to have any issues with the manual gem install? Thanks, Andy Shipman -- 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: application error message, where are the logs?
Run heroku logs inside the app directory and you should see your logs. - David On Thu, Dec 17, 2009 at 1:27 AM, tommy wheels...@gmail.com wrote: hi, i have a very simple toy sinatra app using flickr_fu. i deployed to heroku and it posted to http://growing-rain-77.heroku.com The site gives an application error message. where can i find the logs to debug? -- 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: ambethia-recaptcha gem not working
If that's a gem from Github you may want to add ambethia-recaptcha --source gems.github.com to your .gems file. Alternately, you can use the vanilla recaptcha gem by modifying the line that is requiring ambethia-recaptcha. If this is Rails, look for something like config.gem 'ambethia-recaptcha' and change it to config.gem 'recaptcha' Hope this helps! David On Mon, Dec 14, 2009 at 4:12 PM, StefanSiebel siebel.ste...@gmail.comwrote: Hi, I added the ambethia-recaptcha gem to my application. In the .gems file I added a line recaptcha. Pushing to heroku worked perfectly fine, but when I try to access the application I get this error: Missing these required gems: ambethia-recaptcha Is there something I missed? Do I have to run another command? Thanks! -Stefan. -- 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: If you reserve full instance for custom SSL - why don't I get more dynos?
The core of the problem is that Amazon only allows one IP per EC2 instance, which is why we have to spin up a dedicated instance for SSL at all. If Amazon ever starts allowing that, we'd be able to re-evaluate our options for providing SSL. Until then, this is a pretty decent workaround. I probably wouldn't recommend trying to share it across people as that seems destined to lead to heartache somewhere, but if you want to get custom SSL on multiple apps under one cert, this seems like the way to do it. - David Dollar On Thu, Dec 10, 2009 at 6:06 PM, Kelly Heikkila ke...@coderow.com wrote: Maybe I'm missing something and I'm not an SSL expert, but couldn't Heroku allow customers to purchase more than one IP for an SSL instance? Then they could apply multiple domains without a multi- domain cert and without constantly having to keep applying/managing a single cert when it's changed. The customer would obviously need to make sure to keep the traffic low, as Morten points out. There would be an expense for the IP, but that should be much lower than a dedicated instance. I'm sure there are technical hurdles, but he custom SSL issue is a hot topic as evidenced by the length of this thread/similar ones. Also, I've had a number of conversations with different developers and when the topic turns to heroku they say Great platform, but did you hear SSL costs $100/month? -Kelly On Dec 10, 2009, at 4:22 PM, Wojciech Kruszewski wrote: On Dec 10, 11:06 pm, Morten Bagai mor...@heroku.com wrote: Yeah, I didn't catch the multi-domain part. Well, wildcard is still interesting for me. I could replace *.heroku.com with my own wildcard as a piggyback. I'd prefer to serve sites admin/user panels of my clients from my own domain. Theoretically it might be possible. I don't think we have ever seen a multi-domain cert in the wild at Heroku. Actually I already tried this with two dummy apps and a multi-domain certificate taken from production site - worked like a charm. Will show you the apps once they are migrated (if I remember of course). Also, the solution we have in place now isn't designed for this in a couple of ways: 1) You would have to redeploy the cert every time it changed 2) With multiple busy apps, you might max out the resources of the SSL routing instance Good points. As for the resources, such a feature would be useful mostly for smaller sites. On Dec 10, 2:01 pm, Wojciech Kruszewski wojci...@oxos.pl wrote: Yes I believe it would be possible. You could even create a service that would to the pooling: I'll add your domain to my multi-domain certificate for a yearly fee. emphasisTheoretically/emphasis this business model should work... although I'd much prefer Heroku coming up with their solution. Do you know is it easy to add new domains to existing multi-domain certificates? Regards, Wojciech --http://twitter.com/WojciechK On Dec 10, 10:44 pm, Doug Petkanics petkan...@gmail.com wrote: If I am following your approach correctly, then I believe it would be possible for multiple Heroku users to cooperate on a single custom SSL addon using the following steps. 1. Alice and Bob agree to cooperate and split the costs between one another outside of the scope of Heroku's billing. 2. Alice buys a multi domain SSL cert covering her domain and Bob's domain. Alice also buys the custom SSL addon, and applies the certificate to her app. 3. Alice and Bob edit their domain's DNS settings to point to the dedicated IP. 4. Bob enables piggyback ssl on his app, and gets the benefit of Alice's custom ssl addon. The multi-domain cert they bought includes both their domains. Heroku guys, if this approach would work, would you take issue with some users pooling together to reduce the cost? I don't ask in the spirit of taking advantage of your platform, but instead ask because the current price of custom SSL is prohibitive from running smaller apps on the service right now. Thoughts? On Thu, Dec 10, 2009 at 12:00 PM, Wojciech Kruszewski wojci...@oxos.plwrote: In fact this is possible with their current environment: http://wojciech.oxos.pl/post/277669886/save-on-herokus-custom-ssl-addons On Dec 9, 7:58 pm, Wojciech Kruszewski wojci...@oxos.pl wrote: This is theoretically possible with their architecture, but they are currently reviewing how easy it would be to implement it and if it's worth the trouble. I created a public feature request: http://support.heroku.com/forums/42310/entries/87156 - would you care to add your vote? Cheers, Wojciech On Dec 8, 11:47 pm, Chris Hanks christopher.m.ha...@gmail.com wrote: Wojciech, if you ask support about that and get some good news, would you report back? I'm curious about this too. Thanks! Chris On Dec 8, 2:05 pm, Oren Teich o...@heroku.com wrote
Re: Taps gem not recognized
This is often another LoadError masking as this error. Try the following: gem install open_gem gem open heroku Navigate to lib/heroku/commands/db.rb Change the following two lines: rescue LoadError error Install the Taps gem to use db commands. On most systems this will be:\nsudo gem install taps to: rescue LoadError = ex puts ex.inspect error Install the Taps gem to use db commands. On most systems this will be:\nsudo gem install taps and try to rerun. This should give you some more visibility into what is failing. Hope this helps! David On Tue, Dec 8, 2009 at 9:37 AM, Andrei Erdoss erd...@gmail.com wrote: Hello, I was trying to use the command heroku db:pull. I keep getting this error message: Install the Taps gem to use db commands. On most systems this will be: sudo gem install taps Even though I have the taps gem installed. taps (0.2.22) What can I do to fix this? -- Andrei Erdoss -- 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: password protected site
If you want to do it with Rails, check out http://railscasts.com/episodes/82-http-basic-authentication You can set your RAILS_ENV to staging/testing using heroku config:add apply the before_filter conditionally. Hope this helps! David On Tue, Dec 8, 2009 at 2:37 PM, Nick Quaranto n...@quaran.to wrote: Rack has this baked in, the Sinatra docs have a good example of using it: http://www.sinatrarb.com/faq.html#auth On Mon, Dec 7, 2009 at 11:35 AM, Bradley bradleyrobert...@gmail.comwrote: Is it possible to password protect a site, through something like http auth? I want to set up testing and staging sites, but I don't want these to be public and I don't want to have these restrictions in the code of my 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.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 Spree Commerce + SOA
1. If I have to create all the web services as a separate heroku apps, how would I share the database instance between the more than one services or apps like admin tools or crons? While sharing a database between apps isn't officially supported, you could have a way to expose an app's ENV['DATABASE_URL'] to other apps. This URL may change periodicially, so you'd want to make sure you had a way to reacquire the new one rather than hardcoding it. Another way to accomplish similar functionality is to expose the data you need as an API that is consumed by the other apps in your architecture. 2. If the consumer facing web-app needs to call other services within the cloud to fulfill the request, do I have to use public address (may be using CNAME or whatever) or can I have it route it within the cloud? Requests would need to be made to the public address (via the domain name) as the hostname is what routes a request to a given site. Hope this helps! David -- 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: App failed to start
The Rails 2.3.5 gem (actionpack specifically) has a bug where the gem spec declares a dependency on Rack 1.0 but the gem itself tries to load Rack 1.0.1. We have now manually installed Rack 1.0.1 in the cloud. Try restarting your app using heroku restart to see if that clears it up. If it doesn't, please open a ticket so we can investigate further. - David On Wed, Dec 2, 2009 at 5:06 AM, sushi thaisi...@gmail.com wrote: Hi, my app suddenly face this problem, it's been running fine and no new code push for the past week. App failed to start /usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb: 271:in `require_frameworks': RubyGem version error: rack(0.9.1 not ~ 1.0.1) (RuntimeError) from /usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb: 134:in `process' from /usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb: 113:in `send' from /usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb: 113:in `run' from /disk1/home/slugs/71095_7fe3af5_d99b/mnt/config/environment.rb:9 from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: 31:in `gem_original_require' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: 31:in `require' from /usr/local/lib/ruby/gems/1.8/gems/thin-1.0.1/lib/rack/adapter/ rails.rb:31:in `load_application' from /usr/local/lib/ruby/gems/1.8/gems/thin-1.0.1/lib/rack/adapter/ rails.rb:23:in `initialize' ... 11 levels... from /usr/local/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/builder.rb: 29:in `instance_eval' from /usr/local/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/builder.rb: 29:in `initialize' from /home/heroku_rack/heroku.ru:1:in `new' from /home/heroku_rack/heroku.ru:1 Any idea what is causing this? -- 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: db:push unable to find taps
Try changing that rescue LoadError to rescue LoadError = ex puts ex.inspect to get a better idea of what is failing to load. - David On Wed, Dec 2, 2009 at 4:55 PM, Chris Baglieri chris.bagli...@gmail.comwrote: Installed the latest heroku gem and still no luck. Any thoughts would be appreciated. foo$ heroku version heroku-gem/1.4 foo$ taps version 0.2.22 foo$ heroku db:push Install the Taps gem to use db commands. On most systems this will be: sudo gem install taps This is where the error appears to be thrown (/opt/local/lib/ruby/gems/ 1.8/gems/heroku-1.4/lib/heroku/commands/db.rb for me): def initialize(*args) super(*args) gem 'taps', '= 0.2.8', ' 0.3.0' require 'taps/client_session' rescue LoadError error Install the Taps gem to use db commands. On most systems this will be:\nsudo gem install taps end On Dec 2, 1:47 pm, Morten Bagai mor...@heroku.com wrote: Actually, the current gem version is 1.4. It's on gemcutter. M On Dec 2, 2009, at 10:39 AM, Chris Baglieri chris.bagli...@gmail.com wrote: I'm trying to push a database and 'heroku db:push' is alerting me that I do not have the taps gem installed. The step before issuing the heroku command, I installed taps (0.2.22) and confirmed it was there. I'm attempting to do this from OSX. Someone in the IRC channel suggested I confirm all of taps dependencies where installed and it appears they are. I also updated my heroku gem (which coincidentally was a version behind) hoping that would make a difference. Looking at db.rb, the problem is happening on initialize. I am running everything out of my /opt/local/bin... directory for whatever that's worth. From my command line I can issue taps commands. Could it be that the heroku gem is unable to find my taps gem? My path is below along with some other helpful bits: foo$ echo $PATH /opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/local/sbin:/opt/ local/lib/postgresql84/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/ bin:/usr/X11/bin foo$ gem -v 1.3.5 foo$ taps version 0.2.22 foo$ heroku version heroku-gem/1.3 foo$ which taps /opt/local/bin/taps foo$ which heroku /opt/local/bin/heroku -- 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 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.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: Internal server error when adding Custom Domain + Zerigo DNS add-ons
There's currently a bug related to this that should be addressed very soon. Thanks for the stack trace, I'm adding that to the bug. I'll let you know as soon as it's fixed. Cheers, David On Mon, Nov 30, 2009 at 5:01 AM, Vitaliy Khustochka xyc...@gmail.comwrote: TypeError in Domain namesController#add can't convert Hash into String RAILS_ROOT: /mnt/home/core Application Trace | Framework Trace | Full Trace /usr/local/lib/ruby/gems/1.8/gems/json-1.1.7/lib/json/common.rb:122:in `initialize' /usr/local/lib/ruby/gems/1.8/gems/json-1.1.7/lib/json/common.rb:122:in `new' /usr/local/lib/ruby/gems/1.8/gems/json-1.1.7/lib/json/common.rb:122:in `parse' /mnt/home/core/app/models/external_account.rb:9:in `attrs' /mnt/home/core/app/models/base_domain.rb:13:in `zerigo_account' /mnt/home/core/app/models/domain_name.rb:297:in `zerigo_account' /mnt/home/core/app/models/domain_name.rb:278:in `zerigo_dns_update' /mnt/home/core/app/models/domain_name.rb:32:in `validate' /mnt/home/core/app/controllers/domain_names_controller.rb:14:in `add' /mnt/home/core/app/controllers/domain_names_controller.rb:13:in `add' /mnt/home/core/app/controllers/application_controller.rb:21:in `custom_rescues' /mnt/home/core/app/controllers/application_controller.rb:45:in `disable_query_caching' /mnt/home/core/app/controllers/application_controller.rb:45:in `disable_query_caching' /mnt/home/core/app/controllers/application_controller.rb:171:in `timeout' /mnt/home/core/app/controllers/application_controller.rb:171:in `timeout' -- 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: Something wrong with Heroku?
We had a very brief outage this morning. we identified and corrected an issue related to our AMQP infrastructure. All apps are now back up. - Heroku Support Team On Fri, Nov 27, 2009 at 10:05 AM, geolev geo...@gmail.com wrote: I can't get to any of my apps. I get the following error with a funky little graphic: Oops, we seem to have a glitch in our system. We've been notified; you might try reloading the page in a little while. This is not good. -- 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: reading database.yml
Would it be possible to have your applications expose an API to talk to each other rather than sharing a physical database? On Fri, Nov 27, 2009 at 11:30 AM, Emanuele Tozzato etozz...@gmail.comwrote: I'm aware that database.yml is generated by the deployment script, but I need to share some models between two applications. Can I read the generated database.yml and use it or is it going to change over time? -- Emanuele Tozzato http://hi.im/mek -- 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: Debugging Email
Try setting ActionMailer::Base.*raise_delivery_errors* = true in your config/environments/production.rb and see if the sending process raises anything. - David On Mon, Nov 16, 2009 at 10:05 AM, Neil neil.middle...@gmail.com wrote: We have an app that's sending out emails on certain events. In development this works fine, but in production (on Heroku) we're not getting any email coming out of the app. I can't see anything in the logs that looks useful, and am struggling to think how to debug this. Do you guys have any tips? I am using the Sendgrid add-on. -- 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. For more options, visit this group at http://groups.google.com/group/heroku?hl=. -- David Dollar -- 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.
