(Disclaimer: i don't work for Heroku)
Ryan - I haven't seen any such feature, but you could just read the heroku gem
source code and comment out those parts of the code that actually do the
db:push if you are that paranoid
On Jan 8, 2010, at 9:00 PM, Ryan Heneise wrote:
I should have put
will be charged for 48 hours or
for 30 minutes (1 hours) = 0.05 USD ?
On 6. Jan, 16:26 h., David Dollar da...@heroku.com wrote:
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
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
Maybe you are the first one to do this that deeply - I just run my tests
manually before pushing it to staging, the way its described in deploying
multiple environments that you mentioned below. If you find a solution that
works, I would love to hear about it.
On Dec 21, 2009, at 10:49 PM,
if I put my app into maintenance mode, does hourly/daily cron still
run, and do delayed jobs continue executing? Since the purpose of
maintenance mode is to prevent database errors before migrations are
run, it seems like you can have code in rake and in djobs that fails
in the same way as
I haven't checked out the online cron services yet, but there's
another issue that I had to solve, and I don't know whether they would
support this or not:
Heroku limits the execution time of every request to 30 seconds each,
and a request that takes longer than that is abruptly interrupted.
do something clever (and I was unable to
figure out what that something clever is), X email processor instances
run at the same time. If you need guarantee that each email is
processed once only, this will screw it up for you.
On Wed, Oct 7, 2009 at 11:05 AM, Yuri Niyazov yuri.niya...@gmail.com
Heroku runs on ec2, no? What prevents exposure of an EBS block to an app?
On Tue, Oct 6, 2009 at 5:32 PM, Oren Teich o...@heroku.com wrote:
Hi Neil,
There aren't any plans for shared storage right now. I wish I could
say otherwise. The big challenge is that we're able to achieve our
Heroku comes with cron support, but only once an hour. I need it more
often than that, so I have a separate box with actual crond on it, and
it has a script that hits a specific URL on my app on heroku every x
minutes to process email.
On Tue, Oct 6, 2009 at 3:06 PM, Carl Fyffe
Make it explicit that Heroku runs on EC2, which means that there's no
per-GB charge for data transfers into S3 from Amazon.
On Wed, Jul 29, 2009 at 3:26 PM, Justin Frenchjus...@indent.com.au wrote:
Given how often the DNS issues come up on this list, I'm guessing the
documentation needs some
There are significant SEO implications to having your blog under the
same domain as the application itself.
On Sun, Jul 26, 2009 at 11:37 PM, SimianLogiclearnyoura...@gmail.com wrote:
Seems like you'd be better off setting it up as a subdomain (i.e.
blog.myapp.com), which could be served from
needed optimal SEO. He just asked if there
was a way to get a wordpress blog working alongside a Heroku app.
On Jul 26, 9:13 pm, Yuri Niyazov yuri.niya...@gmail.com wrote:
There are significant SEO implications to having your blog under the
same domain as the application itself.
On Sun
I don't think Heroku supports dropping the DB associated with your
application, unless you delete the application itself - I am pretty
sure that the Heroku guys do not create a separate user in their
server for every user that signs up for the service - the management
overhead would be insane.
in my experience, db:push does exactly that: it takes your local
development database and converts it into the heroku production
database. I've seen that error before; once it was an intermittent
issue with heroku. Another time a new heroku ruby gem came out and I
forgot to update it.
On Thu,
This doesn't seem like a heroku issue:
I just went to http://mightyverse.heroku.com/ and then clicked on the
main link that points to http://mightyverse.heroku.com/home and I got
a 404 back.
On Thu, Jul 9, 2009 at 6:19 PM, Sarah Allensa...@ultrasaurus.com wrote:
My app works, sort of. It
for the page will
load.
On Jul 9, 2009, at 3:25 PM, Yuri Niyazov wrote:
This doesn't seem like a heroku issue:
I just went to http://mightyverse.heroku.com/ and then clicked on the
main link that points to http://mightyverse.heroku.com/home and I got
a 404 back.
On Thu, Jul 9, 2009 at 6:19
'/', :controller = 'media', :action = 'index'
# Install the default route as the lowest priority.
# map.connect ':controller/:action/:id.:format'
map.connect ':controller/:action/:id'
end
On Jul 9, 2009, at 3:47 PM, Yuri Niyazov wrote:
The reason why I bring it up is, when I do a
wget http
I think I agree with the decision that the Heroku team took to support
Postgresql only if thats what makes sense for them.
One of the claimed selling points for Rails itself is that switching
between databases is supposed to be trivial. Calling something a
plugin implies that it is supposed to
?
On Sun, May 24, 2009 at 5:54 PM, Yuri Niyazov yuri.niya...@gmail.comwrote:
I had an app called treatblogdev that I renamed to treatblogdev-old. I made
some nasty mistakes that polluted my repository, and I decided to just start
anew, and I created a new treatblogdev from a new git repository. I did
I had an app called treatblogdev that I renamed to treatblogdev-old. I made
some nasty mistakes that polluted my repository, and I decided to just start
anew, and I created a new treatblogdev from a new git repository. I did:
rails treatblogdev
git push heroku master
heroku rake db:migrate
Now,
I haven't tried this yet, but this came up on HN earlier and might be
exactly what you want:
http://alumnit.ca/~apenwarr/log/?m=200904#30
The author concentrates on talking about the split command, whereas I
imagine what you are more interested is in the pull command.
On Tue, May 12, 2009 at
I actually ended up solving this problem by maintaining two local
repositories (pushing and pulling locally while developing). It's not ideal,
but it's a simple local workaround that works, whereas I am assuming that
the heroku guys would have to do some serious infrastructure magic in order
to
oh come on, your users could crowd-source all your docs :)
On Thu, Apr 23, 2009 at 10:25 PM, Morten Bagai mor...@heroku.com wrote:
Eh, disregard that :) Shouldn't have been sent to this list.
On Apr 23, 7:20 pm, Oren Teich o...@teich.net wrote:
I like sentence #1 and #3. A single Dyno
Well, the whole thing already sounds like a no-go because heroku doesn't
allow writing to the fs
On Apr 17, 2009 2:27 PM, Keenan Brock kee...@thebrocks.net wrote:
dot (and nice)is a command line app.
Graphviz is the package/library name. It is in macports and basically
all distributions.
Most
This is the response I got from hoptoad when I posted the same problem there
-- Forwarded message --
From: Hoptoad Support no-re...@help.hoptoadapp.com
Date: Wed, Mar 18, 2009 at 5:18 PM
Subject: Re: errors not reported, seeing standard rails error page
[Problems]
To:
script/destroy seems to have worked for me in the past; what do you
mean by doesn't seem to work?
On Apr 10, 2009, at 3:36 AM, Clive wrote:
In Heroku Garden, is there a way of reversing or changing a 'generate
scaffold' command?
I often find I need to make changes to the scaffolded
git:master] heroku domains:add www.yurified.com
Internal server error
[dali:~/yurified git:master] heroku domains:add www.yurified.com
Added www.yurified.com as a custom domain name to yurified.heroku.com
[dali:~/yurified git:master]
On Wed, Apr 8, 2009 at 9:10 AM, Yuri Niyazov yuri.niya
This is actually the reason I am asking - I found that it doesn't run
for me regularly either. It always runs on the hour after the first
deployment, but then it is anyone's guess whether it will run again.
On Apr 4, 2009, at 7:10 PM, Eric Anderson wrote:
For me it doesn't actually run
28 matches
Mail list logo