Confirmed users
927
edits
Services/Sync/Server/ReleaseProcess: Difference between revisions
→Background
Tarek.ziade (talk | contribs) |
Tarek.ziade (talk | contribs) |
||
| Line 6: | Line 6: | ||
To go further, virtualenv allows you to create a new Python interpreter copied from the main one. This creates an isolated Python environment somewhere on your system. In other words, every package that will be installed by a Python interpreter created by virtualenv, will be installed under a specific tree and not interfer with the main Python installation. | To go further, virtualenv allows you to create a new Python interpreter copied from the main one. This creates an isolated Python environment somewhere on your system. In other words, every package that will be installed by a Python interpreter created by virtualenv, will be installed under a specific tree and not interfer with the main Python installation. | ||
Ideally, the Weave application should be installed in a virtualenv-ed Python in /var/sync for example. | |||
= Weave application structure = | |||
The Weave application we are building will be organized in three parts | The Weave application we are building will be organized in three parts | ||
| Line 12: | Line 16: | ||
* a .wsgi file used by Apache to run the application | * a .wsgi file used by Apache to run the application | ||
* some Python packages. Right now just one called "weave.server" | * some Python packages. Right now just one called "weave.server" | ||
= Proposal = | = Proposal = | ||