don't really have a way of conveying this across the
platform. We're mostly relying on users checking their email but that's
understandably hard for orgs.
On Fri, Aug 30, 2013 at 5:09 AM, Daniel Doubrovkine dbl...@dblock.orgwrote:
Got it. We have a shared IT account that subscribes to those
Got it. We have a shared IT account that subscribes to those, took a while
to dig it up. Would be nice if everything online reflected this reality.
On Tue, Aug 27, 2013 at 5:31 PM, Robbie rob...@heroku.com wrote:
Hi Daniel,
We sent this out to users that we identified as having Couchbase
For the life of me I cannot find that announcement. Where did you read that
the date is October 31st? Thanks.
On Mon, Aug 26, 2013 at 10:04 AM, jonathan jonathan.bauda...@gmail.comwrote:
As many of you know, Heroku is deprecating their memcache addon in favor
of the Memcachier service.
Having gone that path, we eventually gave up. Any high resolution image
cannot be processed with ImageMagick without 2-4GB of RAM. We now run our
workers on EC2, documented in
http://artsy.github.io/blog/2012/01/31/beyond-heroku-satellite-delayed-job-workers-on-ec2/
.
On Thu, Jun 13, 2013 at 5:20
Fyi, we had no trouble for new instances with Memcachier, you can either
set their environment variables or use
https://github.com/memcachier/memcachier-gem that does the same.
On Mon, Jun 3, 2013 at 4:58 AM, Daniel Farina dan...@fdr.io wrote:
On Wed, May 29, 2013 at 2:58 PM, Daniel Doubrovkine
Can we please have an update from Heroku on whether we need to migrate to
someone else's addon ASAP, too, before the addon decides to stop responding
to memcache read/writes? :)
On Wed, May 29, 2013 at 5:53 PM, Daniel Farina dan...@fdr.io wrote:
On Wed, May 29, 2013 at 2:48 PM,
Does that command run locally as is? It's likely that you have a global
unicorn in /etc/init.d or something like that which supports those start
commands (like this one: https://gist.github.com/jaygooby/504875). Unicorn
by itself takes port and config via -p and -c. See the example in Procfile
belongs in the Heroku API.
That's a longstanding known deficiency. I hope we can fix it
soon, but can't make any promises.
On Sat, Feb 2, 2013 at 9:35 PM, Daniel Doubrovkine dbl...@dblock.org
wrote:
I published heroku-commander (https://github.com/dblock/heroku-commander
)
that wraps `heroku
Issue #186 https://github.com/heroku/heroku/issues/186 (processes don't
pass their return code down to *heroku run*) has been open for about a
year, which makes it very poorly suitable for automation. We thought it was
time to build some more robust workarounds.
Taking the basic idea of echo-ing
it would require cooperation from the server-side, but for the client-side
credentials, not so much.
cheers
dB.
On Thu, Dec 27, 2012 at 2:23 PM, Daniel Doubrovkine dbl...@dblock.orgwrote:
Indeed, maybe this does belong in a gem. Either way one wants to be able
to do programmatically everything
Every single one of these has been a problem with our application. I
suggest using NewRelic, which will instrument the requests and show you
where you're spending time during those requests that time out.
Another idea is to use the https://github.com/kch/rack-timeout gem and set
the timeout
*|* (360) 904.5947 *|*
@scottmessinger *|* www.commoncurriculum.com
On Fri, Jan 25, 2013 at 10:01 AM, Daniel Doubrovkine dbl...@dblock.orgwrote:
Every single one of these has been a problem with our application. I
suggest using NewRelic, which will instrument the requests and show you
where you're
:-)
On Wed, Dec 26, 2012 at 8:30 AM, Daniel Doubrovkine dbl...@dblock.orgwrote:
This might be a stretch, but it could also be quite cool :)
I would divide dyno start in two: a web proxy that responds to requests
quickly while waiting for the actual service to start. Check out
https
Indeed, maybe this does belong in a gem. Either way one wants to be able to
do programmatically everything that the `heroku` command does without
having to call it.
On Thu, Dec 27, 2012 at 1:53 PM, geemus wes...@heroku.com wrote:
I think Daniels approach is the easiest currently (thanks dB!).
This might be a stretch, but it could also be quite cool :)
I would divide dyno start in two: a web proxy that responds to requests
quickly while waiting for the actual service to start. Check out
https://github.com/dblock/heroku-forward - it's an em-proxy that is up
almost immediately and is
We've asked a similar question a while ago, and the best we could come up
with is a hack to run `heroku config -s`.
config = {}
config_output = `heroku config -s#{app_param}`.chomp
if ($?.to_i != 0)
raise error running heroku config: #{$?}
$stderr.puts config_output
end
Many have been struggling with the Heroku R10 boot timeout.
Announcing heroku-forward, a new gem for those with larger or slower
applications struggling to boot on Heroku within the 60s timeout limit. See
started?
--
Neil
On Thursday, 13 December 2012 at 15:21, Daniel Doubrovkine wrote:
Many have been struggling with the Heroku R10 boot timeout.
Announcing heroku-forward, a new gem for those with larger or slower
applications struggling to boot on Heroku within the 60s timeout limit. See
of preventing deploys from working due to R10 rather than
preventing H20's?
--
Neil
On Thursday, 13 December 2012 at 16:06, Daniel Doubrovkine wrote:
Heroku-preboot doesn't achieve the same thing: it changes the order in
which dynos stop/start - instead of first stopping dynos, then queuing
, it
doesn't really go away.
On Thu, Dec 13, 2012 at 2:03 PM, Neil Middleton n...@neilmiddleton.comwrote:
Nowhere. Just wondering ;)
On Thursday, December 13, 2012, Daniel Doubrovkine wrote:
Correct. Where did I say it prevents H20? :)
On Thu, Dec 13, 2012 at 11:18 AM, Neil Middleton
n
We occasionally get 503s, caused by all kinds of things - a dyno will be
sitting in a lock, a database went MIA, Heroku is having trouble, etc.
How do you track 503s? I'd like to keep their counts, graph, etc. Ideally
I'd like to get them in New Relic, but these are errors that happen outside
of
available dynos
are being consumed. This may not be related to 503s, but it often is.
On Mon, Nov 12, 2012 at 12:36 PM, Daniel Doubrovkine dbl...@dblock.orgwrote:
We occasionally get 503s, caused by all kinds of things - a dyno will be
sitting in a lock, a database went MIA, Heroku is having trouble
I have 2.21.2 heroku client, running on Linux. I see this from a heroku
rake output and command fails:
/home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/heroku-2.21.2/lib/heroku/helpers.rb:21:in
`write': \xC3 from ASCII-8BIT to UTF-8
(Encoding::UndefinedConversionError)*04:34:27* from
I would definitely prefer the SSH key because:
1. Every developer already has one.
2. It's the preferred authentication with Heroku for the command line
client, you have to upload your key when you set it up the first time.
3. It's the preferred authentication with Github and many
I tried to get it to work on bamboo and I can't get Heroku to use bundler
1.2.0-pre, it keeps defaulting to 1.0.7.
- Heroku receiving push
- Ruby/Rails app detected
- Detected Rails is not set to serve static_assets
Installing rails3_serve_static_assets... done
- Configure
No, please, lets get going :) I really appreciate you replying. Something
good will come out of this!
I want users to have one single secret - their SSH key should let me obtain
their API key, I don't want to store that anywhere. No?
On Mon, May 7, 2012 at 11:46 AM, geemus wes...@heroku.com
Lets back-up for a second :)
The point is that we don't want to hard-code any credentials on the client.
You have an SSH key and that's the key to the kingdom. And it's your SSH
key, not someone else's. And we want to be able to fetch variables from
your default heroku application identified by
Take the example of a rake task that pushes a deployment to Heroku along
with some S3 assets. Every developer has their own heroku application, and
they configure it by creating a Heroku remote origin.
To push to heroku a developer does do *git push heroku master*, then they
need to push some
I'm trying to replace some code in a Rake task that executes 'heroku config
--long' and parses the output.
I can do this:
c = Heroku::Client.new(* Heroku::Auth.read_credentials)
c.config_vars(my-app)
Awesome, this returns the configuration variables for my-app as a Hash.
The next problem is
Translating from French :)
On Sat, Apr 28, 2012 at 2:24 PM, Jeff Schmitz
jeffrey.j.schm...@gmail.comwrote:
Don't you mean perfect is the enemy of good?
Jeff
On Apr 28, 2012, at 10:42 AM, dB. dbl...@dblock.org wrote:
I don't know about what's ideal, but the list has been working very well.
I ran `heroku rake ...`, I can see the task in `heroku ps`. I press
Ctrl+C, that says canceled. Then I run it again. Now I see this:
rake.1 up for 13m bundle exec rake db:users:dedup db..
rake.2 up for 12m bundle exec rake db:users:dedup db..
I can do a heroku ps:stop 'rake.1'
31 matches
Mail list logo
