I haven't been able to find anything useful on the horde sites, and I haven't found anything useful with 'yum search'.
I am trying to set up horde webmail using the PEAR install on a new CentOS 5 system intending to migrate existing horde-3.x sites to horde-4.x.
The PEAR installation procedure asked for the database type, db name, and password. I had not created the mysql database before running the installation thinking that this would be done as part of the installation (silly me :-). I know little or nothing about the internals of PEAR as I generally avoid PHP if at all possible so I don't know what's necessary to nuke the entire installation and start from scratch other than to restore the VMware VM from the snapshot I made before starting this project.
In the past I have done this manually from the various tarballs available from horde.org, and these had the appropriate SQL scripts to initialize mysql and postgresql back ends. The PEAR installation doesn't seem to have these, nor do the sources obtained with 'git'. They do have upgrade scripts to update from various earlier version of horde which could work for existing installations, but would require more work with new installs.
I tried finding appropriate SRPMs so I could look at their SPEC files to see how others have done this, but haven't been able to find ones for horde-4.x.
The options seem to be:
+ Get SQL scripts to create the necessary databases.
+ Find the appropriate SPRMs for the horde components to see how they take care of this in their %post installation processing.
+ Uninstall the existing stuff using pear, and start from scratch after first creating the appropriate database.
+ Give up and continue to use the older versions of horde components which do work.
Suggestions, pointers to documentation, ???
Bill
On Jan 25, 2012, at 11:53 AM, Bill Campbell wrote:
I haven't been able to find anything useful on the horde sites, and I haven't found anything useful with 'yum search'.
I am trying to set up horde webmail using the PEAR install on a new CentOS 5 system intending to migrate existing horde-3.x sites to horde-4.x.
The PEAR installation procedure asked for the database type, db name, and password. I had not created the mysql database before running the installation thinking that this would be done as part of the installation (silly me :-). I know little or nothing about the internals of PEAR as I generally avoid PHP if at all possible so I don't know what's necessary to nuke the entire installation and start from scratch other than to restore the VMware VM from the snapshot I made before starting this project.
In the past I have done this manually from the various tarballs available from horde.org, and these had the appropriate SQL scripts to initialize mysql and postgresql back ends. The PEAR installation doesn't seem to have these, nor do the sources obtained with 'git'. They do have upgrade scripts to update from various earlier version of horde which could work for existing installations, but would require more work with new installs.
I tried finding appropriate SRPMs so I could look at their SPEC files to see how others have done this, but haven't been able to find ones for horde-4.x.
The options seem to be:
Get SQL scripts to create the necessary databases.
Find the appropriate SPRMs for the horde components to see how they take care of this in their %post installation processing.
Uninstall the existing stuff using pear, and start from scratch after first creating the appropriate database.
Give up and continue to use the older versions of horde components which do work.
Suggestions, pointers to documentation, ???
---- you're going to have to make up your mind which you want to use, MySQL or PostgreSQL
After that decision is made, you would simply create the databases using the client tools of either or if you are unfamiliar/uncomfortable using command line to create user/database/privileges for the database of choice, you probably just want to use something like webmin (can do either postgres or mysql), MySQL_Query_Browser (mysql) or PgAdmin3 (postgres)
Craig
On Wed, Jan 25, 2012, Craig White wrote:
On Jan 25, 2012, at 11:53 AM, Bill Campbell wrote:
I haven't been able to find anything useful on the horde sites, and I haven't found anything useful with 'yum search'.
...
The options seem to be:
Get SQL scripts to create the necessary databases.
Find the appropriate SPRMs for the horde components to see how they take care of this in their %post installation processing.
Uninstall the existing stuff using pear, and start from scratch after first creating the appropriate database.
Give up and continue to use the older versions of horde components which do work.
Suggestions, pointers to documentation, ???
you're going to have to make up your mind which you want to use, MySQL or PostgreSQL
While I much prefer PostgreSQL, I have been using MySQL with horde as it looks like that's where there support is best.
After that decision is made, you would simply create the databases using the client tools of either or if you are unfamiliar/uncomfortable using command line to create user/database/privileges for the database of choice, you probably just want to use something like webmin (can do either postgres or mysql), MySQL_Query_Browser (mysql) or PgAdmin3 (postgres)
I've been doing *nix systems since 1982 with Radio Shack Xenix so I'm fine with the CLI tools. I've also done a fair amount of DB work in python and perl using their DBI modules.
What I haven't been able to find are the sql script files to do the initial database creation that were present in older versions of horde, imp, kronolith, turba, etc.
Bill
On Jan 25, 2012, at 3:45 PM, Bill Campbell wrote:
On Wed, Jan 25, 2012, Craig White wrote:
On Jan 25, 2012, at 11:53 AM, Bill Campbell wrote:
I haven't been able to find anything useful on the horde sites, and I haven't found anything useful with 'yum search'.
...
The options seem to be:
Get SQL scripts to create the necessary databases.
Find the appropriate SPRMs for the horde components to see how they take care of this in their %post installation processing.
Uninstall the existing stuff using pear, and start from scratch after first creating the appropriate database.
Give up and continue to use the older versions of horde components which do work.
Suggestions, pointers to documentation, ???
you're going to have to make up your mind which you want to use, MySQL or PostgreSQL
While I much prefer PostgreSQL, I have been using MySQL with horde as it looks like that's where there support is best.
After that decision is made, you would simply create the databases using the client tools of either or if you are unfamiliar/uncomfortable using command line to create user/database/privileges for the database of choice, you probably just want to use something like webmin (can do either postgres or mysql), MySQL_Query_Browser (mysql) or PgAdmin3 (postgres)
I've been doing *nix systems since 1982 with Radio Shack Xenix so I'm fine with the CLI tools. I've also done a fair amount of DB work in python and perl using their DBI modules.
What I haven't been able to find are the sql script files to do the initial database creation that were present in older versions of horde, imp, kronolith, turba, etc.
---- Don't quote me on this - you can probably get a better definitive answer from the horde mail list but I think the actual scripts are located in your PEAR directory (perhaps under Horde/Test)
Of course you need to get into mysql and create a user for horde, create a database for horde and grant permissions to the horde user for the horde database and obviously configure that in horde/config/conf.php (which should be possible with the web configuration tool.
Craig
On Wed, Jan 25, 2012, Craig White wrote:
On Jan 25, 2012, at 3:45 PM, Bill Campbell wrote:
...
What I haven't been able to find are the sql script files to do the initial database creation that were present in older versions of horde, imp, kronolith, turba, etc.
Don't quote me on this - you can probably get a better definitive answer from the horde mail list but I think the actual scripts are located in your PEAR directory (perhaps under Horde/Test)
Of course you need to get into mysql and create a user for horde, create a database for horde and grant permissions to the horde user for the horde database and obviously configure that in horde/config/conf.php (which should be possible with the web configuration tool.
That got me there.
After digging around in the $prefix/bin/webmail-install script and grep'ing my way through the Horde directories, I figured out that I could rerun webmail-install script after creating the mysql database, user, and password, and all the appropriate tables were created.
Now I need to look at the schema to see what's necessary in migrating an older horde/imp installation to this.
Thanks again.
Bill
On Jan 25, 2012, at 5:34 PM, Bill Campbell wrote:
On Wed, Jan 25, 2012, Craig White wrote:
On Jan 25, 2012, at 3:45 PM, Bill Campbell wrote:
...
What I haven't been able to find are the sql script files to do the initial database creation that were present in older versions of horde, imp, kronolith, turba, etc.
Don't quote me on this - you can probably get a better definitive answer from the horde mail list but I think the actual scripts are located in your PEAR directory (perhaps under Horde/Test)
Of course you need to get into mysql and create a user for horde, create a database for horde and grant permissions to the horde user for the horde database and obviously configure that in horde/config/conf.php (which should be possible with the web configuration tool.
That got me there.
After digging around in the $prefix/bin/webmail-install script and grep'ing my way through the Horde directories, I figured out that I could rerun webmail-install script after creating the mysql database, user, and password, and all the appropriate tables were created.
Now I need to look at the schema to see what's necessary in migrating an older horde/imp installation to this.
---- the 'migration' of the db's should be done within the administration panel of Horde except if your previous version was too old.
Craig
Craig White craig.white@ttiltd.com wrote:
On Jan 25, 2012, at 5:34 PM, Bill Campbell wrote:
Now I need to look at the schema to see what's necessary in migrating an older horde/imp installation to this.
the 'migration' of the db's should be done within the administration panel of Horde except if your previous version was too old.
And, IIRC, for older versions there was a migration script somewhere in the distribution, too.
Devin
-
Bill Campbell -
Craig White -
Devin Reade