On 10/15/2011 10:05 AM, Thomas Mortagne wrote:
Restarting the vote since the first one was a bit
fuzzy, too late in
3.2 cycle and I made some required improvements since then.
The idea is to make as easy as possible to install production ready
XWiki Enterprise (and others later probably) on debian/ubuntu.
Here is what is provided right now:
* a "common" package which is a base package containing a XWiki with
everything except the hibernate setup (but it provide some templates
which are used by other packages)
* a "tomcat-mysql" package which depends on xwiki commons, tomcat6,
mysql-server, libmysql-java debian packages and make sure a MySQL
database is created for XWiki and that it's properly added to tomcat
applications
* a "tomcat-pgsql" package which depends on xwiki commons, tomcat6,
postgresql, libpg-java debian packages and make sure a PostgreSQL
database is created for XWiki and that it's properly added to tomcat
applications
* I wrote a script to run in a cron which update a Debian repository
descriptor (Packages.gz) in releases and snapshot maven repositories
and also create a virtual "stable" Debian repository which contains
only stable releases
* it of course follow Debian standard path (configurations files in
/etc/xwiki/ etc...) and you get nice conflict resolution tools when
upgrading files thanks to dpkg
+1.
Internally, the resulting package looks good (as far as I can understand
from a .deb).
I don't like the artifactId xwiki-enterprise-common. Shouldn't it be
xwiki-enterprise-debian-common, at least in the current place?
After moving it inside xwiki-enterprise, we'll probably have to change
all the IDs into something like xwiki-enterprise-distribution-debian-common.
WDYT about an (optional?) Apache HTTPD front-end configuration, as in
also provide and enable the perfect way of proxying XWiki?
--
Sergiu Dumitriu
http://purl.org/net/sergiu/