Форуми / Cotonti / Core Labs / Archive / Install/Upgrade script

Is what we actually need

Trustmaster
#1493 24.11.2008 02:51
We have been skipping this for quite a long time, but now I see that having a handy Install/Upgrade script would save a lot of time and help to involve more people to be using Seditio-N.

The main requirements are:
  • Make new installations completely automated in a few steps.
  • Possible to upgrade from Seditio starting with v110 (also v120, v121 and v125) to very recent version by using SQL patches shipped in docs/sql.
  • Providing both version upgrades (for stable releases) and revision updates (for SVN trunk).
  • Should use existing configuration and skin if possible.
  • Template layout (no built-in HTML).
  • The script itself doesn't depend on current version.

On the very first step it should try to detect an existing installation. It prompts for MySQL account details and checks for existing Seditio(-N) database. If a previous installation can be found, there will be 2 options: Install and Upgrade. Otherwise, it will automatically start with Install.

Install process goes this way:
[list=1]
  • Try to set write permission to folders in datas and tell a user do it manually if the script has failed doing it.
  • Ask database and other configuration options and write the config.php file.
  • Import the latest SQL dump.
  • Ask main site's configuration options and set them in the database.
  • Ask Administrator's account details and create it.
  • Tell a user to remove the script and log into his newly created account.

  • Upgrade process goes this way:
    [list=1]
  • Get full version number from current installation.
  • If it is an old Seditio (like v110), apply patches to update it to v125. Then, as it is still Seditio, run patches to update it to N-0.0.1.
  • Continuously apply SQL patches to update it from existing Seditio-N revision up to the latest revision contained in the package (according to datas/sql scripts).
  • Inform the user of the progress and errors if any.
  • When patching is done, tell him to remove the script.

  • In fact, this task is a high priority because it would help testers and developers a lot, so it is a must for 0.0.2.
    May the Source be with you!