Hello Deepak,
A single / free dyno spins down when it is not in use.
Much like passenger / mod_rails on your local box.
It cost ram/cpu/money to run a dyno on an ec2 instance.
If you are not using it (and you are not paying for it), then there is no
reason why Heroku should dish out the money
My slug is pretty big, about 50 MB, mostly due to gem dependencies. I
figure I could shave about 5 MB if I spent an entire day shaving off
unused bits. But I doubt this would make any perceivable difference.
I don't really mind the sluggish spin up time. What I do mind is
having slug compilation
Can you store the results in memcache or mongo? How much space do all
the sitemap files consume?
--
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
Type 'gem sources' on a console and you'll probably see github in
there. gem sources -r http://github.com/; should remove it.
On Aug 30, 8:06 pm, brianp brian.o.pea...@gmail.com wrote:
I get this error every time but none of my gems source github.
WARNING: RubyGems 1.2+ index not found
Don't know how to solve your issue, but just as an FYI, you don't need
memcached-northscale when you're doing development. The 'memcached'
gem will behave identically.
(Just make sure to use memcached-northscale when you're pushing your
app to heroku)
On Aug 28, 6:45 am, tmac22
I know this is a bit cutting edge but the memcached gem was actually deprecated
today and replaced with http://github.com/mperham/dalli.
Most intersting is the fact that dalli is pure ruby and aims to be a drop in
replacement for memcached-client with performance increases and SASL (Mike
I don't really mind the sluggish spin up time. What I do mind is
having slug compilation occasionally take 4+ hours instead of the
normal 3 minutes. That means I can't show my boss the current state of
Slug compile should never take that long. It sounds like a bug - we have
noticed a few
What's heroku's official stance on users using various methods to prevent
dynos from being idle? I personally have a production app that only uses 1
dyno and need to wait a while for the first request to get processed while
the dyno spins back up.
While I understand Heroku's reasons for spinning
On 30 Aug 2010, at 23:54, Terence Lee wrote:
In the near future we're going to start requiring the Gemfile.lock to be
checked into your git repository since this is the recommended deploy
path set by the bundler team. Please take the time to do so if you
haven't already.
There's an
I just checked, and the sitemaps are even bigger than I expected.
Every 1,000 entries in the sitemap seems to take about a meg...which
means the total size is in the gigabyte range. Now the sitemap
protocol allows for gz compressed sitemaps, which reduces the size by
more than 90%, which means
What other questions do you guys have on the area that I should include?
Two:
What is Heroku's timeout when spinning up dynos/workers? I thought
that I'd seen this mentioned somewhere, but I can't find it now. I ask
because an app I'm thinking of would need to hit external services and
the
What is Heroku's timeout when spinning up dynos/workers? I thought
that I'd seen this mentioned somewhere, but I can't find it now. I ask
because an app I'm thinking of would need to hit external services and
the database when starting up, which could take a while.
30 seconds.
Is there
You're not alone -- would be great to have a solution for this.
Heroku's official stance is to just include them and don't worry
about the bloat, but obviously that won't work in your case.
On Aug 31, 2:32 pm, Ashley Moran ashley.mo...@patchspace.co.uk
wrote:
On 30 Aug 2010, at 23:54, Terence
It's rolled out. Please file a support ticket if there are any issues.
Thanks,
Terence
On Mon, 2010-08-30 at 17:54 -0500, Terence Lee wrote:
We're planning on doing a rollout for Bundler 1.0.0 to support Rails 3.
As always, please test things locally and on production. You can view
the full
Thanks for the reply unfortunately that is not listed as a gem source.
So it cannot be removed.
Any other suggestions?
On Aug 31, 10:18 am, chris mcclellan...@gmail.com wrote:
Type 'gem sources' on a console and you'll probably see github in
there. gem sources -rhttp://github.com/; should
All of a sudden, the login form on my site results in
InvalidAuthenticityToken exceptions. This happened without changing
any code. The same code base is working fine in my staging app.
The only difference between production and staging is the use of the
New Relic Custom Domain add-ons.
I'm
Ugh. Lesson learned: Don't cache forms.
On Aug 31, 10:36 pm, Andrew C. andrew.c...@gmail.com wrote:
All of a sudden, the login form on my site results in
InvalidAuthenticityToken exceptions. This happened without changing
any code. The same code base is working fine in my staging app.
The
17 matches
Mail list logo
