[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Phpgroupware-tracker] [ 100615 ] Upgrade Ease Idea
From: |
nobody |
Subject: |
[Phpgroupware-tracker] [ 100615 ] Upgrade Ease Idea |
Date: |
Mon, 18 Mar 2002 20:05:33 -0500 |
Support Request #100615, was updated on 2002-Mar-19 01:05
You can respond by visiting:
http://savannah.gnu.org/support/?func=detailsupport&support_id=100615&group_id=509
Category: Feature Request
Status: Open
Priority: 5
Summary: Upgrade Ease Idea
By: BadlandZ
Date: 2002-Mar-19 01:05
Message:
Logged In: YES
user_id=6018
Browser: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020204
Very nieve question.
Would it be possable to ditch/pass ALL of the
configuration information into a database (SQL) in
order to ease upgrades?
Say, the tarball with every single new phpGroupWare
file is there, and the user just tar -zxvf's out the
tarball... EXCEPT, some file in setup/inc that is
called config.inc.unset or something, that has to be
modified with the database account and password for new
installs, and for upgrades it just doesn't overwrite
the original config.inc file?
And then, when upgraded, all admin features still work,
reguardless of database structure changes. And you
simply can go into the admin pages and click a "upgrade
database" button or something?
I think it's a good idea. Obviously, I may have the
correct files to do this with wrong, and maybe there is
a better way to do this, but hopefully you get the
general idea???
And if there already is such a feature, please let me
know, because I missed it ;-)
----------------------------------------------------------------------
You can respond by visiting:
http://savannah.gnu.org/support/?func=detailsupport&support_id=100615&group_id=509
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Phpgroupware-tracker] [ 100615 ] Upgrade Ease Idea,
nobody <=