Add Deployment Documentation #155
Conversation
| ----------- | ||
|
|
||
| Warehouse is deployed on Ubuntu 12.04 with the PyPy interpreter. It uses | ||
| PostgreSQL as it's database and Elasticsearch for it's search implementation. |
|
You've asked a number of questions where the answer is basically "it's controlled by Chef and the Chef cookbooks". I think I'll expand out the documentation to contain more information about the chef side of things which controls the deployment and configuration of the various services that compromise a full Warehouse installation. Essentially we use Chef to setup all the servers (Build Server which creates the deb packages, App server which hosts the Warehouse application, Search server which hosts the Elasticsearch instance) and we use Jenkins running on the build server to build the deb package that chef deploys to the App servers. All of the configuration of all of those services is controlled by Chef which makes it easy to send out an update to those configurations in a multiple server environment. This will be more important once things are setup so that there can be multiple App servers without needing to manually replicate configuration changes across servers. It also means that Warehouse requires no manual setup besides running the bootstrap command that installs chef on a server and associating the pypi role with that server. |
|
Is the server requirements, roles and quantity described in human readable form? |
|
Closing this PR in deference to python/psf-chef#77 |
|
"it's controlled by Chef and the Chef cookbooks". Chef is ok for bots. If we need human contributors (and not only corporations) there should be human-oriented instruction with a "automated by chef" note. Not vice versa. Or else the system becomes exclusive and "closed" for the majority of Python folks who don't use Chef and Ruby. |
|
On importance scale, it is much worse that patent menace. =) |
No description provided.