Updates

Updating the files

Git

If you installed Novius OS with Git, run these commands from Novius OS directory:

git fetch origin
git checkout master/dubrovka
git submodule update --recursive --init

Note

The submodule update can display a line

warning: unable to rmdir packages/log: directory not empty

in this case, execute this command

rm -rf novius-os/packages/log/

Zip

If you downloaded the Zip file, the procedure is more complex.

• Let’s say you installed novius OS in my_site/.

• First, backup your old directory (copy it and make a .zip file with it).

• Download the new Zip of Novius OS and extract it. You now have a novius-os/ directory.

• In my_site/, delete the following directories:

  • my_site/novius-os/
  • Every my_site/local/applications/noviusos_* directories

• Copy the following directories and files from novius-os/ to my_site/ :

  • novius-os/
  • Tous les répertoires local/applications/noviusos_*
  • novius-os/
  • Every local/applications/noviusos_* directories
  • Every local/config/*.sample files
  • public/htdocs/install/, public/htdocs/install.php and public/htdocs/migrate.php.sample
  • Every files in root directory

Now you can continue the update.

Run the migration

Before running the automated migration tools, please backup your database.

Via SSH

If you’re allowed to acces SSH on the server, run this command from your Novius OS directory:

sudo php oil refine migrate
sudo php oil refine migrate -m

Via Browser

If you can’t access SSH, you can run the migration from your browser:

• First, you need to rename the public/migrate.php.sample file to public/migrate.php.
• Open the file in your browser, such as http://www.my_site.com/migrate.php.

Via back-office

If you can’t access SSH, you can run the migration from back-office of your Novius OS:

• Connect to your back-office
• Open the “Applications manager” application
• Click on “Apply changes” for each applications, or on “Refresh all metadata” in toolbar if your in expert mode.

Warning

When you access to your back-office without migrated, your software is in a instable state. Sources not matches with the DB state. You will probably see error messages. You can ignore them.

Migrate your developments

If you have personnal developments, you need to follow the Migration guide from the Chiba 2 version to the D version.