On Sun, Aug 16, 2009 at 10:39 AM, Alex Chaffeeale...@gmail.com wrote:
During the few seconds the restart is happening, what happens to
incoming HTTP requests? Are they queued or do they fail? If the
latter, where's the error page and can we change it?
And what's the timing like for applying
Awesome. That's even better than I'd hoped! :-)
- A
On Aug 17, 12:00 pm, Adam Wiggins a...@heroku.com wrote:
On Sun, Aug 16, 2009 at 10:39 AM, Alex Chaffeeale...@gmail.com wrote:
During the few seconds the restart is happening, what happens to
incoming HTTP requests? Are they queued or do
Ricardo -
Thanks for the detailed replies but I'm still unclear on a few things
about downtime during deploy.
During the few seconds the restart is happening, what happens to
incoming HTTP requests? Are they queued or do they fail? If the
latter, where's the error page and can we change it?
Good point Richard, if we have to handle it ourselves I think it
deserves a little mention in the docs.
I assume that most people are use to capistrano which had a cap
deploy:migrations command that would run the migrations before
symlinking the new code. (Although I never personally tested it.)
running migrations before updating the code would still leave you in a
similar broken state because the database schema has changed but your
code has not been updated for it. Depending on how much has changed
will be the severity of your brokenness. Keep in mind that this is
still a small
I think it might still say that somewhere in the docs because I remember
being confused when I updated something a little while ago and something
wasn't working, so when I figured out that my migration hadn't been
activated yet, which took a little while to pin down as the problem, I was
able to
This is going to be a problem wherever you deploy your application
to. And what happens during that gap is really up to you.
Once the push completes the old version of your codebase is no longer
running. If the migration changes the database schema radically odds
are you're going to see a lot
Between the push to heroku (which will automatically launch the app)
and heroku rake db:migrate what happens?
I know it's only a few seconds, but potentially the site would be
broke right?
--~--~-~--~~~---~--~~
You received this message because you are subscribed
