Disqus - Latest Comments for mortenheroku

Re: Heroku | SSL Hostname Add-on Public Beta

Morten Bagai (Heroku) — Wed, 31 Mar 2010 12:50:39 -0000

To be on the safe side, I'd recommend: 1) remove the current add-on with "heroku addons:remove ssl:ip" 2) re-upload your certs and 3) add the new add-on with "heroku addons:add ssl:hostname".

Re: Heroku | Manage Heroku with your iPhone

Morten Bagai (Heroku) — Wed, 27 Jan 2010 18:02:39 -0000

Hi Tom,

The basic source for the docs app is here: http://github.com/heroku/he....

Re: Heroku | DJ has evolved into Workers

Morten Bagai (Heroku) — Thu, 03 Dec 2009 19:03:39 -0000

Paul,

I think Oren stated it clearly in his comment.

What we're doing with this release of Heroku Workers is responding to one of the top demands from our customer base: getting access to multiple workers for high-volume job processing, and being able to scale up/down just as easily as you do with dynos. Delivering support for this important use case required an infrastructure and pricing change as outlined in the announcement.

In addition to that, we're aware that there's a different use case for background workers that involves deferring of lightweight/occasional tasks. The typical example is email, and as mentioned Rails 3 is even going to internalize that.

We plan to support that use case too, but we are small team so we have to do things incrementally.

To ensure service and cost continuity for our paying customers who have committed to using the DJ add-on on Heroku, we're offering the monthly service credits. This way, they can continue operating as-is knowing they're covered until we offer a new solution for occasional/lightweight background job processing.

Re: Heroku | DJ has evolved into Workers

Morten Bagai (Heroku) — Thu, 03 Dec 2009 18:14:28 -0000

Yuri, I don't understand why you would go remove DJ from your apps. If you read the announcement, you'll see that we're issuing you credits to guarantee the $15 price point for the next 6 months.

Best,

Morten

Re: Heroku | DJ has evolved into Workers

Morten Bagai (Heroku) — Thu, 03 Dec 2009 13:50:11 -0000

Good question. First of all, a dyno is a one, single-threaded web server process. When a request comes in, the goal should be for your dyno to process it as quickly as possible. A reasonable goal would be that a request should take no more than 100-200ms. Sometimes you'll have request that take longer. Sending email, or modifying an image would be examples of that. The modern approach to such requests is to *not* let the user wait for the page to return, but rather to offload the task to a separate, background process and return immediately with a page that says "Processing your request...". Typically you'd use an AJAX call to poll for the background process complete, and update the page as soon as the job is done. In summary, the whole point of background processing is to hand off jobs from the main web server process to another process, so as not to block the main, user-facing web server process. I hope that explains why polling for Delayed Jobs in your dyno does not make any sense.

As for github, I'm sure what defunkt means is probably that they're running their background processing software on the same virtual or physical server as their web serving software. The point is that they're still separate processes, or even processing tiers.

Re: Heroku | Radiant CMS in 5 Minutes Or Less

Morten Bagai (Heroku) — Mon, 31 Aug 2009 17:40:32 -0000

Yes, you should be able to get going with the free plan. I've done many small Radiant deployments, and it works great. Keep in mind that the 5mb limit is for database records only - it takes a pretty serious blog to accumulate that much data in a year, for example. Of course, depending on traffic and other feature requirements the success of your site will hopefully take you into paid territory at some point :)

Re: Heroku | Pimp Your Cart: Shopify Apps on Heroku

Morten Bagai (Heroku) — Fri, 12 Jun 2009 19:31:29 -0000

I believe they're currently running the website here, and some components related to this developer platform. We're super excited to have them, and hope to work even more closely together in the future.

Re: Heroku | Radiant CMS in 5 Minutes Or Less

Morten Bagai (Heroku) — Fri, 22 May 2009 12:08:22 -0000

You should ignore log, tmp, config/database.yml and probably also any db/*.sqlite3 files. While it's technically possible to use sqlite3 in the tmp/ dir on Heroku it is most decidedly *not* recommended. The tmp/ is for temporary storage only, so you should always use the provided PostgreSQL db for persistent data storage.

Re: Heroku | Commercial Launch

Morten Bagai (Heroku) — Sat, 25 Apr 2009 13:37:37 -0000

Yes, you'll get a notification. We'll be providing a variety of ways for you to gain visibility into your current resource usage through the API (and client) as well as the web UI.

Many thanks for the great screencast btw. Really awesome stuff!

Re: Heroku | Deploy Merb, Sinatra, or any Rack App to Heroku

Morten Bagai (Heroku) — Fri, 06 Mar 2009 12:01:55 -0000

Yes, we do. You can read more about it here: http://heroku.com/how/archi....

Best,

/Morten

Re: Heroku | Why Instant Deployment Matters

Morten Bagai (Heroku) — Tue, 24 Feb 2009 15:28:11 -0000

Misfo, you raise a great point. An important aspect of friction in the deployment process is the context shift from application development to system administration/SCM. By curating a managed, best-of-breed production stack that's dead simple to deploy to, we strive to make deployment a seamless extension of development, thereby eliminating the need for that context switch, and the inefficiencies that often follow.