BenoitTalbot / bungeni-portal

Automatically exported from code.google.com/p/bungeni-portal
0 stars 0 forks source link

Critical Review - Installation Process #656

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
The installer must be simplified as much as possible. 

1) the procedure must be run in a single command 
it must use mostly released packages, at cost to lose some features 
it must compile only components you cannot avoid to, for example: 
Zope/Plone: the compilation is part of the buildout system then ok 
Python: not needed 
Postgres, Xapian, other softwares: not needed 

for Python modules use only released eggs on pypi or on reliable repositories
There is a package index for this purpose (http://dist.bungeni.org)

Python, Postgres, Xapian are software having packages released for 
debian/ubuntu, there is not need to compile from source code. 

2) It must document the steps to install/re-install single parts: 
only Zope 
only Plone 
only ’x’ module (if compilation needed)
it must check dependencies and versions, but only: 
as an helper for sysadmin 
to be not blocking (no strictly versions at least for stand-alone software as 
Postgres) 
to check for missing packages and advice for tested version 
for eggs always pick/dumps the versions in the buildout configuration

3) it must move all operations related to buildout in recipes and entry point 
scripts and if it is possibile try to remove capistrano and use only buildout 
recipes, to have only one technology to learn. Both Capistrano and Buildout are 
very complex products to learn and manage, Buildout is needed in any case 
because it is the normal way to install Zope and Plone

4) it must avoid to put user and password in a file: it is a security risk, 
expecially because the user must be in the sudoers on the target server 

5) it must not delete the content of /tmp folder but only specific directories, 
because on desktop machines this behavior generate malfunctions

6) it must provide a way to install the system without having a ’commit’ 
account on the svn repository 
the process must be tested on a clean server (eg. a virtualbox server) each 
time a new package is integrated.

Original issue reported on code.google.com by ashok.ha...@gmail.com on 5 Jul 2010 at 7:36

GoogleCodeExporter commented 9 years ago
Most of these issues have been resolved in the fabric build

Original comment by ashok.ha...@gmail.com on 27 Sep 2010 at 9:42