Documentation and Recipes for Deploying Mimic to a Server

rackerlabs / mimic

An API mock service

Other

167 stars 57 forks source link

Documentation and Recipes for Deploying Mimic to a Server #345

Open ghost opened 9 years ago

ghost commented 9 years ago

Reach team plans on creating recipes to automate deploying mimic to a server that would allow us to hit it like a normal end point.

Things that should be covered:

Chef Recipe's to configure a server and automate deploying mimic safely to the server
SSL should be required and the articles should be very clear to not use real auth tokens or keys

In the future:

An ansible version of our recipes and articles I create would probably be useful since mimic and open stack are python focused

lekhajee commented 9 years ago

@tokunbo, @ksheedlo : This might be of interest to Cloud Intelligence.

ghost commented 8 years ago

Published initial cookbook here: https://github.com/gabecase/mimic-cookbook

Moving this to rackerlabs soon. What I published is a simplified cookbook that installs mimic via pip, we can add another recipe to get the latest mimic from master but that would require a github deploy key(basically a read only key a machine can use to checkout code but cant commit or push any upstream changes): https://github.com/blog/2024-read-only-deploy-keys

glyph commented 8 years ago

Why would this need deploy keys? The Mimic repository is open source; anyone can clone it without authenticating. Deploy keys are for cloning private repositories.