Confirmed users
927
edits
Services/Sync/Server/ReleaseProcess: Difference between revisions
Jump to navigation
Jump to search
→Proposal 1 : release-based
Tarek.ziade (talk | contribs) |
Tarek.ziade (talk | contribs) |
||
| Line 32: | Line 32: | ||
The application is installed in the virtualenv-ed Python's site-packages, and the .ini file in /etc/sync.ini, so other apps can use it when needed. | The application is installed in the virtualenv-ed Python's site-packages, and the .ini file in /etc/sync.ini, so other apps can use it when needed. | ||
This solution removes the dependency the server to install has with the mercurial | This solution has several advantages: | ||
* it removes the dependency the server to install has with the mercurial repositories: an installation is done with static files. | |||
* it automates the deployment of data files and scripts on the target system. | |||
* the releases can be pushed at PyPI and used by the community with standard installation tools. | |||
== Release process == | == Release process == | ||