> > - - Upgrade to Midgard 1.7.4
> This is long time due. Now we run the last 1.6.x release, and don't
> have even QB on the server.
> Piotras, could you help me do this? Some issues with this upgrade are:
Sure, datagard_test on test server prooved that midgard-data may be used
without user and there are plenty of places where we can automate and tune
scripts for our needs.
> * There are several hosts and databases, none of them in ML format
> * All Midgard databases run on the remote mysql.nehmer.net host
> * There is no local DB process for the "MLization" temporary DBs
That should be no problem. Temporary database is needed only when ML'ed
package must be imported to ML'ed database.
Typical database update can be done in database itself.
The only "problem" with datagard and remote server is that we can not set
permissions on remote server.
I will prepare some test scripts and will make sure it's repligard free.
However we should import languages.xml.
> * VirtualHost configuration is not in datagard format
It depends what and how much directives should be changed.
In most cases we should only add cache dir and change root files.
To sum up, I would suggest to make this ASAP.
1.7.4 release fixed some <1.5 memory problems.
And what is more important:
Tarjei and me was tuning test server last days and now it's obvious that php leaks itself.
At least there are no single byte in HEAD which leaks suing basic operations.
But PHP reported leaks are reproducable every time.