[ php-blog-Bugs-2992079 ] make s9y friendlier for downstream

Bugs item #2992079, was opened at 2010-04-25 19:11
Message generated for change (Comment added) made by garvinhicking
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=542822&aid=2992079&group_id=75065

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Installer/Upgrader
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: J.M. Roth (jmroth)
Assigned to: Nobody/Anonymous (nobody)
Summary: make s9y friendlier for downstream

Initial Comment:
When packaging this application it 
- may be a policy not to write to /usr/share/...: which is what the native installer/upgrader does in order to write the installed version number,
- is difficult to introduce 'multi-site' behavior: according to existing instructions files would need to be installed for each user wishing to use the application.

Most problems could be alleviated by storing the currently installed version number in the database instead of some file (which the webserver user (think of suexec etc.) might not be able to modify anyhow).

Like this, the native upgrade procedure (maybe even install) could be used (simplifying the packaging) as well as easy multi-site behavior would be possible at no additional cost: each DB/site would carry its own version number, which would be automatically updated if a new release is installed in the central location. The current version number of the installed files would be available from serendipity_config.inc.php and could be compared to the version in the DB.

So my proposal: why not store actual version number in database?

(PS: Yes it is true that one might to introduce some more patches to customize the compiled template and uploads directory path and such.)

----------------------------------------------------------------------

>Comment By: Garvin Hicking (garvinhicking)
Date: 2010-04-26 07:25

Message:
Hi!

I'm not really sure I understand this. I assume you are talking about the
"Shared Installation" feature specifically?

Those should always only need to write data to their own document root,
not the shared /usr/share/... directory. serendipity_config_local.inc.php
is the local version where database credentials are held, and also the
version number.

I don't see a problem with storing that data inside there, because this
file always needs to hold DB credentials, they can't really be stored
somewhere else, so having the version number inside that file instead of
instead the database doesn't seem to make a big difference for me?

I do agree that the data in there should be as minimal as possible. But in
the case of installation problems, or if s9y changes the DB layer API, it
would be helpful to have version information outside the DB connection, so
that it can be modified. Also, users for whom the upgrade failed can easily
re-execute updates by modifying that file - for those people it would be
way harder to do that using possible unknown tools like phpMyAdmin for
them?

Maxbe if you can explain a bit more, I can better understand the issue?

Regards,
Garvin

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=542822&aid=2992079&group_id=75065

------------------------------------------------------------------------------