Hi,
I have installed TL 1.8.3 on a workstation but now I would like to install the 1.8.5 on a fresh server.
Is it necessary to perform the migration or only restore the database on server and install TL 1.8.5 will be sufficient?
In another words, can we use a database created for TL 1.8.3 on TL 1.8.5 without migration?
Thanks for your answer
Is it necessary to migrate TL V1.8.3 to V1.8.5?
Moderators: Amaradana, TurboPT, TL Developers
Re: Is it necessary to migrate TL V1.8.3 to V1.8.5?
The short answer is yes, but there are some other minor considerations to know.
Save a copy of the current 1.8.3 tree. [more on this in a moment]
Copy the database [data + structure] to the new server
Install the 1.8.5 tree on the new server.
Then...
From the 1.8.3 copy:
The 'config' files will be needed:
1. db_config.php [should be a straight copy]
2. config.inc.php [might want to do a quick diff against 1.8.5]
3. custom_config.inc.php [straight copy if this file was never modified -- meaning a diff will not show changes]
4. bug tracker config. [if used] copy the relative config file(s) [i.e. bugzilla.cfg.php]
5. Your custom application changes [if any were made] those will need to be manually merged into the relative 1.8.5 files.
I think that's about it. Try these steps on the new server [while still keeping the workstation available] and see how it goes.
Save a copy of the current 1.8.3 tree. [more on this in a moment]
Copy the database [data + structure] to the new server
Install the 1.8.5 tree on the new server.
Then...
From the 1.8.3 copy:
The 'config' files will be needed:
1. db_config.php [should be a straight copy]
2. config.inc.php [might want to do a quick diff against 1.8.5]
3. custom_config.inc.php [straight copy if this file was never modified -- meaning a diff will not show changes]
4. bug tracker config. [if used] copy the relative config file(s) [i.e. bugzilla.cfg.php]
5. Your custom application changes [if any were made] those will need to be manually merged into the relative 1.8.5 files.
I think that's about it. Try these steps on the new server [while still keeping the workstation available] and see how it goes.