Skip to content

RE: Zero downtime deploys #43

@jonathanconway

Description

@jonathanconway

I've had to roll-back my attempt at blue-green deploys.

The steps given in this document simply do not achieve the desired effect.

Desired effect:

  • The current version of the site will be served while the new version is being deployed. After the new version is deployed, the current version will no longer be served, and only the new version will be served.

Actual effect of following the steps:

  • The current version of the site and the version immediately prior to the current version are both be served simultaneously, whether or not a newer version is being deployed. They are served at random alternating intervals, so that it's impossible to predict which one will be served. If the older version is served, and the current version is desired, the only way to get to the current version is to keep refreshing the page until the current version is served.

It's a great idea, so I will work with you all to figure out a safe way to implement this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions