Any ideas anyone? Haven't solved it yet.
Thanks
Petros
--
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.
Hi Jim,
One solution is to schedule all of these events as jobs to be processed by
delayed job workers at the specified time. Take a look at the Heroku Delayed
Job documentation for info on using workers and setting up DJ. The
documentation doesn't cover job scheduling using the :run_at
it's been working here for a week or so with a beta3 app on bamboo
1.9.1. i didn't do anything special to get it working but maybe the
stats i'm getting from it are all worthless...not a terribly important
application so i guess worthless stats are ok for now as long as it's
not actively breaking
I currently have one app running with one dyno in production env. I'd
like to create a staging one too, but am not sure if I can do that,
with one dyno and its still free, or if I'll now have to pay for a 2nd
dyno.
thanks,
Brian
--
You received this message because you are subscribed to the
On Mon, May 17, 2010 at 3:44 PM, Brian bburr...@gmail.com wrote:
I currently have one app running with one dyno in production env. I'd
like to create a staging one too, but am not sure if I can do that,
with one dyno and its still free, or if I'll now have to pay for a 2nd
dyno.
No, you only
Hello Brian,
You want to have one code base that is hooked up to 2 heroku apps. (staging,
production)
Each of the heroku apps gives you 1 dyno for free.
I like the article at:
http://jqr.github.com/2009/04/25/deploying-multiple-environments-on-heroku.html
(see also:
Thanks!
On May 17, 3:08 pm, Nicolás Sanguinetti h...@nicolassanguinetti.info
wrote:
On Mon, May 17, 2010 at 3:44 PM, Brian bburr...@gmail.com wrote:
I currently have one app running with one dyno in production env. I'd
like to create a staging one too, but am not sure if I can do that,
Thanks for the info and the links. Very helpful.
Brian
On May 17, 3:18 pm, Keenan Brock kee...@thebrocks.net wrote:
Hello Brian,
You want to have one code base that is hooked up to 2 heroku apps. (staging,
production)
Each of the heroku apps gives you 1 dyno for free.
I like the article
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
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
Got the same problem and solved it.
I'm using ubuntu linux, but every debian based system should work the same way.
1. Installing libreadline-dev,
sudo apt-get install libreadline-dev
2. go to the ruby source ext/readline and
3. sudo ruby extconf.rb
4. make
5. make install
and it should
Something strange started happening yesterday my workers started
Exiting... by them selfs. I did see the message where workers where
locked for some time yesterday, was there an update to workers process
management?
--
You received this message because you are subscribed to the Google Groups
12 matches
Mail list logo