view release on metacpan or  search on metacpan

doc/upgrade/index.rst  view on Meta::CPAN

publishing to CPAN.

The most significant user-facing change was the move to automated database
migrations using |Sqitch|. Because of this change, it is critical that anyone
running a version prior to 4.0, who wishes to retain any of their existing
data, follow the steps outlined here before running any newer version.

#. Stop your current |RB| instance and ensure nothing else is accessing or
   modifying its database.

#. Perform a *data only* database backup of the entire |RB| database. Assuming
   the PostgreSQL database is running on the default port of localhost and is
   named ``robobot``, the command will look like this::

       pg_dump -a -Fp -h localhost -d robobot -U robobot > robobot-dataonly.pgdump

#. Drop or rename the current database from your older |RB| instance, and
   create a new, blank |RB| database with appropriate access permissions.

#. Install version 4.002 of |RB|. Do not install any later versions yet. It is
   critical that you install this exact version first so that you can restore

doc/upgrade/index.rst  view on Meta::CPAN

#. Run |RB| once with migrations enabled. This will ensure that |RB| applies
   all of the necessary migrations to create a new, clean database schema::

       robobot -c <path to config> -m

#. Stop the |RB| instance once migrations have been applied.

#. Use ``psql`` to connect to your |RB| database, as whatever user you have
   configured for access, and issue the following SQL statement to remove the
   redundant skill level names (your data-only backup from earlier is going to
   try to recreate these, which will be a problem if they already exist)::

       DELETE FROM skills_levels;

#. Restore the data-only backup you created earlier (again, assuming your |RB|
   database is on the default port of localhost; adjust the connection settings
   as necessary to match your actual environment)::

       psql -h localhost -U robobot -d robobot < robobot-dataonly.pgdump

#. Start the |RB| instance again with the ``robobot`` command and ensure that
   everything is okay.

Assuming you have not run into any errors, and all your data remains intact
(there is very little reason it should not be -- the worst you should encounter