Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
GUI opened this issue Dec 8, 2014 · 1 comment
Closed

Comments

@GUI
Copy link
Member

GUI commented Dec 8, 2014

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.

@GUI
Copy link
Member Author

GUI commented Dec 8, 2014

Tested and new deployment seems to be working fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant