17 lines
1.2 KiB
Text
17 lines
1.2 KiB
Text
|
Sylver Update Server -- PHP
|
||
|
|
|
||
|
|
database driven?
|
||
|
|
|
||
|
|
Should be able to do the following:
|
||
|
|
Check latest version available for a specific script package
|
||
|
|
List all available script packages
|
||
|
|
Download individual files from the script package (or, perhaps, a single package file when the packaging routines for mIRC are finished)
|
||
|
|
|
||
|
|
script package specs are contained in the main addon file (.sa). Should the php engine parse this? or should it be entered into the database?
|
||
|
|
That would require an ini parser for PHP..... interesting.
|
||
|
|
On the other hand of course, the client could simply parse the .sa and get the files, needing only the base directory from the server. Quite possibly the better idea.
|
||
|
|
Whaddya know,.... $nofile() can handle relative unix paths, this can work!
|
||
|
|
|
||
|
|
The system cannot be built soley around a full-script update construct, since I still prefer to release the addons in a standalone fashion as well. Addons will have a menu option to update themselves, which can work without the full update suite.
|
||
|
|
This will most likely mean splitting the update suite into two scripts: an update "library", containing the basic functions required to perform a sa-based web update, and the full script's update client.
|