03-09-2017, 08:26 AM
This is a little more tricky, but not much. The steps are like this:
- get a fresh copy of the project: git clone, let say you name this "uptodatecorebos", so it would be:
- copy from you production install, into this new directory:
storage
test/logo
user_privileges (overwrite any existing files)
config.inc.php
and any non standard modules that you may have:
for example, PDFMaker would require that you copy:
modules/PDFMaker
Smarty/templates/PDFMaker
if you have others, then you copy their directories
- now move your production install, let's suppose you have your production install in a directory called "corebos", you would do
- now move the new directory to where the production one was:
now you should be able to login and load and apply all the coreBOS updater changesets and have everything up to date and under git version control
Please make a backup of everything before starting
let us know how it goes
- get a fresh copy of the project: git clone, let say you name this "uptodatecorebos", so it would be:
Code:
git clone https://github.com/tsolucio/corebos uptodatecorebos
- copy from you production install, into this new directory:
storage
test/logo
user_privileges (overwrite any existing files)
config.inc.php
and any non standard modules that you may have:
for example, PDFMaker would require that you copy:
modules/PDFMaker
Smarty/templates/PDFMaker
if you have others, then you copy their directories
- now move your production install, let's suppose you have your production install in a directory called "corebos", you would do
Code:
mv corebos savemycorebos
- now move the new directory to where the production one was:
Code:
mv uptodatecorebos corebos
now you should be able to login and load and apply all the coreBOS updater changesets and have everything up to date and under git version control
Please make a backup of everything before starting
let us know how it goes
Joe
TSolucio
TSolucio