Skip to content

Re-figure out deployment process for individual API Umbrella components #159

@GUI

Description

@GUI

The October upgrade to the system changed a lot, including how API Umbrella gets installed. While the new installation makes it easier to upgrade API Umbrella as a whole, one thing we've been missing since that rollout is an easy way to deploy some of the individual components of API Umbrella independent from new API Umbrella releases. We need better deployment functionality for the individual components so we can push live new features and functionality as we develop them, rather than trying to batching things into larger API Umbrella releases.

The fundamentals of how we will deploy this are still the same as before the October release (using Capistrano), but enough things have changed that I need to step through the deployment process again, and verify that deployments still occur without any downtime or dropping any connections.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions