Rake tasks to start workers and Tweetstream
What I'm trying to do: Spin up daemonizedTweetsteam via a heroku rake
tweetstream:start task and have it run with a worker.
Basic idea is this:
tweetstream.rake
class TweetStreamRunner
def self.start
# Account username and password go in new daemon and then keywords
you want to grabin track
# If want combos of words in a a particular tweet best to handle
in query in controller code
TweetStream::Daemon.new(ENV['TWITTER_USERNAME'],
ENV['TWITTER_PASSWORD']).track('term1', 'term', etc) do |status|
# Grab all tweets from the stream tracking the keywords listed
end
end
end
namespace :tweetstream do
desc "Fires up the TweetStream daemon"
task :start => :environment do
TweetStreamRunner.start
end
end
Keep getting this error when I get heroku rake tweetstream:start
ERROR: no command given
Usage: tweetstream --
* where is one of:
start start an instance of the application
stop stop all instances of the application
Stumped since I do, in fact, believe I'm doing this with the daemon
I've got here.
Anyone got any pointers as to what I'm doing wrong? (And yes, this is
a repost since I realized I may have asked the question in the wrong
way or confusingly before).
Help appreciated,
thanks !
Daryl.
PS> I should point out I have this working on EC2 no problem, it just
seems to be porting it to heroku and using MongoHQ (now working) and
using a background worker for tweetstream that seem to be the problem.
--
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: Daemonized workers on heroku and tweetstream via heroku rake jobs:work
The unlocked gemfile message comes from using padrino I believe... it
is not a Rails app I should probably point out.
D
On Apr 10, 6:55 pm, Abel Tamayo wrote:
> From the error message you get, it looks like you have a Gemfile that you
> should "lock" with bundle lock before you deploy your application.
>
>
>
> On Sun, Apr 10, 2011 at 9:23 AM, Daryl wrote:
> > I keep getting the following error when running a rake task that is
> > supposed to start a worker daemon on heroku.
>
> > => Located unlocked Gemfile for production
> > ERROR: no command given
> > Usage: tweetstream --
>
> > However, I've created a rake task in lib/tasks (I'm using padrino)
> > which defines jobs:work (which I trigger with heroku rake jobs:work as
>
> > exec {ruby 'lib/tasks/tweetstreamer.rb' start}
>
> > The tweetstreamer.rb file adds a class to connect to the MongoHQ
> > database, but other than that is straight up out of the docs in terms
> > of daemonizing tweetstream
>
> > ie.
> > TweetStream::Daemon.new(ENV['TWITTER_USERNAME'],
> > ENV['TWITTER_PASSWORD']).track('term1', 'term2', 'term3') do |status|
> > status.do stuff
> > end
>
> > So, a bit stumped here and can't seem to fund much doc love on heroku
> > on the use of background processes if it's not delayed job or on
> > github for background worker processes using heroku. It's possible I'm
> > just not googling smart, but seems like it's a bit of a hole here (and
> > am putting my hand up for the blog post that'll help everyone who
> > might be working on this).
>
> > Can anyone point to a similar code example or provide some help here
> > to guide me?
>
> > thanks !
> > Daryl.
>
> > --
> > 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: Daemonized workers on heroku and tweetstream via heroku rake jobs:work
Hey Abel,
As far as I'm aware, bundle lock is depracted and whenever I run
bundle install/update the applicaiton is now locked so I don't think
this can be the source of the issue. Also, the gem is included in my
Gemfile and in the top of the file I'm calling so I don't think it's a
gem issue (unless I've missed something). Any other ideas?
thanks for the suggestion though!
ciao !
Daryl
On Apr 10, 6:55 pm, Abel Tamayo wrote:
> From the error message you get, it looks like you have a Gemfile that you
> should "lock" with bundle lock before you deploy your application.
>
>
>
> On Sun, Apr 10, 2011 at 9:23 AM, Daryl wrote:
> > I keep getting the following error when running a rake task that is
> > supposed to start a worker daemon on heroku.
>
> > => Located unlocked Gemfile for production
> > ERROR: no command given
> > Usage: tweetstream --
>
> > However, I've created a rake task in lib/tasks (I'm using padrino)
> > which defines jobs:work (which I trigger with heroku rake jobs:work as
>
> > exec {ruby 'lib/tasks/tweetstreamer.rb' start}
>
> > The tweetstreamer.rb file adds a class to connect to the MongoHQ
> > database, but other than that is straight up out of the docs in terms
> > of daemonizing tweetstream
>
> > ie.
> > TweetStream::Daemon.new(ENV['TWITTER_USERNAME'],
> > ENV['TWITTER_PASSWORD']).track('term1', 'term2', 'term3') do |status|
> > status.do stuff
> > end
>
> > So, a bit stumped here and can't seem to fund much doc love on heroku
> > on the use of background processes if it's not delayed job or on
> > github for background worker processes using heroku. It's possible I'm
> > just not googling smart, but seems like it's a bit of a hole here (and
> > am putting my hand up for the blog post that'll help everyone who
> > might be working on this).
>
> > Can anyone point to a similar code example or provide some help here
> > to guide me?
>
> > thanks !
> > Daryl.
>
> > --
> > 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.
Daemonized workers on heroku and tweetstream via heroku rake jobs:work
I keep getting the following error when running a rake task that is
supposed to start a worker daemon on heroku.
=> Located unlocked Gemfile for production
ERROR: no command given
Usage: tweetstream --
However, I've created a rake task in lib/tasks (I'm using padrino)
which defines jobs:work (which I trigger with heroku rake jobs:work as
exec {ruby 'lib/tasks/tweetstreamer.rb' start}
The tweetstreamer.rb file adds a class to connect to the MongoHQ
database, but other than that is straight up out of the docs in terms
of daemonizing tweetstream
ie.
TweetStream::Daemon.new(ENV['TWITTER_USERNAME'],
ENV['TWITTER_PASSWORD']).track('term1', 'term2', 'term3') do |status|
status.do stuff
end
So, a bit stumped here and can't seem to fund much doc love on heroku
on the use of background processes if it's not delayed job or on
github for background worker processes using heroku. It's possible I'm
just not googling smart, but seems like it's a bit of a hole here (and
am putting my hand up for the blog post that'll help everyone who
might be working on this).
Can anyone point to a similar code example or provide some help here
to guide me?
thanks !
Daryl.
--
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.
Rake v. Delayed Job on heroku
I have a small app which I have been using a Rake task for to execute a weekly database churn task which then mails out to bunches of users to update. I'm in the process of rolling this app out to a much wider audience and assuming that rake running on heroku means that it is running this on one dyno when the rake task runs and tying up that process completely (and I'm assuming rake just uses one dyno even if I'm using, say... 8 in the app.). I do use this rake to weekly emails technique a lot in apps on normal machines but just wondering if there is a best practice for handling this in heroku, particularly where the processing job and email send out would be quite large. (I figure the better way to handle this is to rewrite the rake function so it dumps the processing to a /lib function and then dump the processing and email to delayed_job in order to make this inherently more scalable on heroku (and have workers pound it so it goes quickly without affecting the responsiveness of the application itself).) Any help or insight appreciated on what other people are doing with larger apps. thanks, Daryl. -- 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: Simple static served Rack app failing to respond at root domain - Rack File.open issue ?
I should point out that I solved this via a different method (though
still have no idea why the above doesn't work, so would love someone
to enlighten me).
I used rack-rewrite in a .gems file and went from there :
I've detailed what I did on my blog :
http://blog.wakatara.com/2010/09/15/serving-up-static-sites-on-heroku-redux/
It definitely works.
On Sep 12, 8:34 pm, Daryl wrote:
> A strange one. I have a static served site I threw up on heroku with a
> simple config.ru file that was working fine until someone pointed out
> it was down yesteday.
>
> The app is only not serving the index.html page if you navigate to the
> domain root ie.www.example.com. It works if you usewww.example.com/index.html
> for example.
>
> config.ru
> use Rack::Static, :urls => ["/css", "/images", "/index.html", "/
> contact.html", "/home.html", "/password.html"], :root => "public"
> run lambda { |env| [200, { 'Content-Type' => 'text/html', 'Cache-
> Control' => 'public, max-age=86400' }, File.open('public/index.html',
> File::RDONLY)] }
>
> Runs fine under thin 1.2.7 on my dev laptop.
>
> When I heroku logs I get :
> !! Unexpected error while processing request: uninitialized constant
> Rack::File::RDONLY
>
> Removing that parameter just creates other Rack::File errors which
> makes me assume something has change don heroku since this worked fine
> in the past (only thing I can think of is the fact I have multiple
> domains iw. example,com,www.example.com,
> example_second.com,www.example_second.compointing at it).
>
> directory tree is :
> .
> |-- config.ru
> `-- public
> |-- contact.html
> |-- css
> | |-- microsite_v1.css
> | `-- microsite_v2.css
> |-- home.html
> |-- images
> | |-- animation70.gif
> | |-- blank.gif
> | |-- logo.gif
> | `-- square.gif
> |-- index.html
> `-- password.html
>
> Anyone able to help me here ? There are no bundled gems on this in
> a ,gem or Gemfile file as the thing worked previousl without them so
> assuming a change in heroku has affected this somewhat... or I'm just
> being dense, but I've had someone else look at this and they can't
> puzzle it out either.
>
> thanks for any assistance. I've sure it's something very small.
> ciao !
> Daryl.
--
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.
Simple static served Rack app failing to respond - was working fine up till recently...
A strange one to be sure. I have a static served site I threw up on
heroku with a simple config.ru file that was working until someone
pointed out it was done yesteday,
config.ru
use Rack::Static, :urls => ["/css", "/images", "/index.html", "/
contact.html", "/home.html", "/password.html"], :root => "public"
run lambda { |env| [200, { 'Content-Type' => 'text/html', 'Cache-
Control' => 'public, max-age=86400' }, File.open('public/index.html',
File::RDONLY)] }
Runs fine under thin 1.2.7 on my dev laptop.
When I heroku logs I get :
!! Unexpected error while processing request: uninitialized constant
Rack::File::RDONLY
Removing that parameter just creates other Rack::File errors which
makes me assume something has change don heroku since this worked fine
in the past (only thing I can think of is the fact I have multiple
domains iw. example,com, www.example.com, example_second.com,
www.example_second.com pointing at it).
directory tree is :
.
|-- config.ru
`-- public
|-- contact.html
|-- css
| |-- microsite_v1.css
| `-- microsite_v2.css
|-- home.html
|-- images
| |-- animation70.gif
| |-- blank.gif
| |-- logo.gif
| `-- square.gif
|-- index.html
`-- password.html
Anyone able to help me here ? There are no bundled gems on this in
a ,gem or Gemfile file as the thing worked previousl without them so
assuming a change in heroku has affected this somewhat... or I'm just
being dense, but I've had someone else look at this and they can't
puzzle it out either.
thanks for any assistance. I've sure it's something very small.
ciao !
Daryl.
--
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.
Simple static served Rack app failing to respond at root domain - Rack File.open issue ?
A strange one. I have a static served site I threw up on heroku with a
simple config.ru file that was working fine until someone pointed out
it was down yesteday.
The app is only not serving the index.html page if you navigate to the
domain root ie. www.example.com. It works if you use www.example.com/index.html
for example.
config.ru
use Rack::Static, :urls => ["/css", "/images", "/index.html", "/
contact.html", "/home.html", "/password.html"], :root => "public"
run lambda { |env| [200, { 'Content-Type' => 'text/html', 'Cache-
Control' => 'public, max-age=86400' }, File.open('public/index.html',
File::RDONLY)] }
Runs fine under thin 1.2.7 on my dev laptop.
When I heroku logs I get :
!! Unexpected error while processing request: uninitialized constant
Rack::File::RDONLY
Removing that parameter just creates other Rack::File errors which
makes me assume something has change don heroku since this worked fine
in the past (only thing I can think of is the fact I have multiple
domains iw. example,com, www.example.com, example_second.com,
www.example_second.com pointing at it).
directory tree is :
.
|-- config.ru
`-- public
|-- contact.html
|-- css
| |-- microsite_v1.css
| `-- microsite_v2.css
|-- home.html
|-- images
| |-- animation70.gif
| |-- blank.gif
| |-- logo.gif
| `-- square.gif
|-- index.html
`-- password.html
Anyone able to help me here ? There are no bundled gems on this in
a ,gem or Gemfile file as the thing worked previousl without them so
assuming a change in heroku has affected this somewhat... or I'm just
being dense, but I've had someone else look at this and they can't
puzzle it out either.
thanks for any assistance. I've sure it's something very small.
ciao !
Daryl.
--
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 monitoring and DR/BC backups - SMS and email alerting etc
Had seen them mentioned before but hadn't heard whether people were really happy with them or not. Have you used them and like them? They look close to what we need. Daryl. On Jun 11, 11:17 pm, Ben Lovell wrote: > On 11 June 2010 09:18, Daryl wrote: > > > Hey there! > > > In the past, I've generally had dedicated servers (or Amazon EC2) that > > have allowed me to use monit and be pointed at via Nagios for > > monitoring and alerting when things went all pear shaped. > > > What are people using as reasonably priced options for monitoring the > > uptime and such of their heroku apps ? Looked at Scout but sms > > monitoring is not available for less than $159 USD a month which is a > > bit steep for our NGO on top of the fees we'll be paying heroku. > > Have you heard of these folks: > > http://pingdom.com/ > > Cheers, > Ben > > > > > thanks ! > > Daryl. > > > -- > > 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.
Application monitoring and DR/BC backups - SMS and email alerting etc
Hey there! In the past, I've generally had dedicated servers (or Amazon EC2) that have allowed me to use monit and be pointed at via Nagios for monitoring and alerting when things went all pear shaped. What are people using as reasonably priced options for monitoring the uptime and such of their heroku apps ? Looked at Scout but sms monitoring is not available for less than $159 USD a month which is a bit steep for our NGO on top of the fees we'll be paying heroku. Would be interested to hear what other people have come up with. Primarily we'd be looking at alerts when the app is down, there are performance issues or services are otherwise disrupted (ie. site slow, unreachable, or for example, delayed job throws a fit). Additionally, while we're looking at just backing up hourly to an S3 snapshot or the like for the datbase we'd be interested in hearing about what experiences people have had with that when things have gone horribly horribly wrong and in general what the time to recover and such is. thanks ! Daryl. -- 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: Time zone issue, Rails 3 - Time.zone = set, but heroku still using local server time
I could be wrong but I believe in Rails 3 the options in Initializers affect the ActiveRecord time (ie. writing to the DB in the local time zone rather than UTC) but Time Zones set in the controllers are supposed to make the application honour time zone settings versus the System Date/Time. I also thought this was double true if you set it in your application_controller. Can anyone confirm? I've run into quite a few things on Rails 3 that have had bugs (ok, or weirdness between Ruby 1.9.1, Heroku, Rails 3 beta 2/3 or what have you) so just trying to run this one down to earth. ciao ! Daryl. On May 4, 12:09 am, "Matthew A. Brown" wrote: > Hi Daryl, > > The Time.zone code only affects the behavior of Time.zone > (Time.zone.now, Time.zone.parse, ActiveRecord's casting of Date > columns, etc) inside your application; it doesn't have any effect on > system time (which is what `date` as well as Time.now will give you). > The best practice is to write your application to always use the > Time.zone.* functions to deal with times, and not make any assumptions > about the system time. > > Mat > > > > On Mon, May 3, 2010 at 01:30, Daryl wrote: > > Hey there herokuistas, > > > So, I'm using Rails 3.0.0.beta3 and am trying to get the default time > > in my app to be London while the servers, as you know, are on Pacific > > time (I'm in Aus myself). > > > I've set the application_controller.rb to have a before filter which > > sets the timezone and then sets that to London (I still want AR to > > write to the DB in UTC, so have not touched the environment/ > > application.rb). > > > === > > before_filter :set_timezone > > > def set_timezone > > Time.zone = 'London' > > end > > === > > > Checking heroku console `date` *still* shows the machines on Pacific > > time, as does a check of the code when I got there (it should show > > Monday but instead stuck on Sunday at the mo). > > > Can anyone tell me what I need to do to get the code to see this as > > London time ? > > > Also, I've asked the fine folks at heroku to reset the daily cron to > > go off at 1.15am London time and just wondering if changing this > > setting to London time will then affect that daily cron job kicking > > off. > > > Any help appreciated! A bit stumped here. Thanks ! > > Daryl. > > > -- > > 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 > 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.
Time zone issue, Rails 3 - Time.zone = set, but heroku still using local server time
Hey there herokuistas, So, I'm using Rails 3.0.0.beta3 and am trying to get the default time in my app to be London while the servers, as you know, are on Pacific time (I'm in Aus myself). I've set the application_controller.rb to have a before filter which sets the timezone and then sets that to London (I still want AR to write to the DB in UTC, so have not touched the environment/ application.rb). === before_filter :set_timezone def set_timezone Time.zone = 'London' end === Checking heroku console `date` *still* shows the machines on Pacific time, as does a check of the code when I got there (it should show Monday but instead stuck on Sunday at the mo). Can anyone tell me what I need to do to get the code to see this as London time ? Also, I've asked the fine folks at heroku to reset the daily cron to go off at 1.15am London time and just wondering if changing this setting to London time will then affect that daily cron job kicking off. Any help appreciated! A bit stumped here. Thanks ! Daryl. -- 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.
Email deploy hook add on not working with Rails 3 beta 3 ?
I keep trying to install the email deploy hook (I like infomring myself I've depoyed... ahem... ) and it keeps giving me a heroku error when I try to activate and Test it. Also, while configured, it's not sending mails when I deploy. Still being worked on for Rails 3? Are there any other AddOns not working that you can still install ? (please don't say SendGrid). ciao ! Daryl. -- 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.
Bug report?: New Relic Bronze Add On having issues on mri-1.9.1 and with Rails 3.0.0.beta2
Something to check. Adding it in borked my app with no failure messages in heroku logs but removing it brought it back to normal. Have left it out for now. Too bad. It's nice... =] ciao ! Daryl. -- 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: Bamboo mri 1.91 stack, Rails 3 and strange bundler problem when pushing to heroku
Solved... For some reason it appears that when I created the app the 1.9.1 stack did not stick. Detroying the app and then recreating it again with the bamboo-mri-1.9.1 stack and then redeploying did the trick. D On Apr 28, 1:33 am, Daryl wrote: > Oh and bundler is (0.9.24) > > -- > 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.
Re: Bamboo mri 1.91 stack, Rails 3 and strange bundler problem when pushing to heroku
Oh and bundler is (0.9.24) -- 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.
Bamboo mri 1.91 stack, Rails 3 and strange bundler problem when pushing to heroku
Have my app working on dev lappie on Ruby 1.9.1 and Rails 3.0.0.beta3 (yay!). The Gemfile for the app is as follows: source :gemcutter gem 'rails', '3.0.0.beta3' gem 'devise', '1.1.rc1' group :development do gem 'mysql' end group :test do gem 'rspec' gem 'rspec-rails' gem 'capybara' gem 'database_cleaner' gem 'cucumber-rails' gem 'cucumber' gem 'pickle' end group :production do gem 'pg' end When I push to heroku (and am on the bamboo 1.9.1 stack) I'm getting the following error : === -> Gemfile detected, running Bundler -> Bundler works best on the Bamboo stack. Please migrate your app: http://docs.heroku.com/bamboo Unresolved dependencies detected; Installing... Fetching source index from http://gemcutter.org/ Resolving dependencies Installing abstract (1.0.0) from system gems Installing actionmailer (3.0.0.beta3) from rubygems repository at http://gemcutter.org/ /usr/local/lib/ruby/site_ruby/1.8/rubygems/ installer.rb:186:in `install': actionmailer requires Ruby version >= 1.8.7 (Gem::InstallError) === Not quite getting it since the thing is on 1.9.1 but could appreciate any pointers to what may be wrong. Figure it's a gotcha I don't know about (do I need to explicitly list every gem in the rails bundle required for example?). thanks ! Daryl. -- 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: pull/push in one step?
+1 (and +4 for the devs on my team.. =] I *really* like the S3 export/import idea as well. We've got a 4G database that is only going to grow bigger soon as we migrate to heroku for production. Daryl. On Mar 16, 4:57 am, Mike Doel wrote: > I imagine we're not alone in having both a staging and production environment > up on heroku. We frequently use heroku db:pull to grab the production > database and will occasionally put it up to our staging environment with > heroku db:push. > > Is it possible to do this in one step? Something like: > > heroku db:copy app1 app2 > > Ideally, this would happen without having to download locally and uploading > as separate steps (i.e. direct server-to-server transfer). > > Mike -- 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.
Dedicated database CPU Units equivalent ?
Apologies if this is listed somewhere and I just couldn't find it on the site, but in looking at the CPU Units measure I need an idea of the benchmark CPU and I/O performance of the Ronin and Fugu compared to a piece of hardware so we can figure out our sizing (and do cost estimates). Can someone provide what the equivalent is to CPU Units in off-heroku units ? thanks! Daryl -- 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: Spin up and down workers from within my app?
Yes, I've seen the Heroku gem inclusion idea (which seems like a damn good one for me). This does seem like a killer feature for heroku though, so kinda curious as to why there aren't any published "best practice" ways to do it from the heroku mother ship ? (and for some reason searching on this group didn't turn up any posts you alluded to... =< ). So, can you qualify the "feint of heart" comment ? Just wondering. Being foolhardy instead, I should probably be informed... =] BTW, the use case in particular would be punting something to a delayed_job and then sicking a whack of ramped up workers on it till it was done. Dynos would be interesting too, so are you advising checking an increasing queue depth to tell when this needs to happen ? Anyhow, thank you very much Oren. ciao ! Daryl. On Jan 30, 5:45 am, Oren Teich wrote: > There's been some discussion on the list before about how to achieve this. > It's possible, but not for the feint of heart. You can include the heroku > gem and just call "heroku dynos X", or look at the heroku gem source code on > github to see the API calls we make. http://github.com/heroku/heroku > Search the archives for HEROKU_QUEUE_DEPTH as well. > > Oren > > On Thu, Jan 28, 2010 at 9:03 PM, Daryl wrote: > > +1. I was just about to ask if anyone had some code samples of doing > > this we could study (or point at them if we're just being dense with > > google searches). > -- 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: Spin up and down workers from within my app?
+1. I was just about to ask if anyone had some code samples of doing this we could study (or point at them if we're just being dense with google searches). In particular, for certain tasks I'd like to dump to delayed job, we'd like to bang the hell out of it with ramped up workers and then shit them down. Also, same with our dynos as well. We have very, very spikey traffic (we're an activist campaigning org), so if anyone has examples of ramping up dynos as load on them increases or something (think EC2 autoscaling), I'd really really like to see it. ciao ! Daryl. On Jan 26, 7:55 pm, Justin Kan wrote: > I have various events that occur in my app that I where I want to > trigger adding heroku workers. Is this possible? How would I do this > from my rails 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.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Showing the git hash and date in a view on heroku
Disclaimer: New to heroku so I'm sure someone has figged this out, but googling didn't help. Normally, I deploy via capistrano to servers and simply have a task which takes a small part of the hash and posts it to a partial. So, on heroku, tried installing grit gem and then creating an application helper to get the last commit via a Grit::Repo.new (Rails.root + '.git') and then render it in a partial view but reading the fine print on the read only file system detail on heroku I guess that access to git is not supported. Has anyone got a workaround for displaying a bit of the git hash and date in the footer of pages ? Or have I missed something blindingly obvious ? thanks, Daryl. -- 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.
