Hello I’m facing issues because I push pub files from my local develop env to staging env. One of the are db.php and db.tpl.
I would like to know what I should care if I’m using code control version.
5 answers
Hi there,
Let’s push all related database tables (table with prefix ub_mirate) and related folders/files of our tool (pub/ub-tool/) to your staging env and excluded folder pub/ub-tool/protection/runtime/cache/
Once done, you must manual update new databases information at two files:
pub/ub-tool/protected/config/db.tpl
pub/ub-tool/protected/config/db.php
Once done, you could continue with your tool in your new instance.
Regards,
Mall.
After manual update of db.tpl and db.php and deleted cache files except .htaccess, I had to go to Backend > Databases and save it again, are you sure that there are no more files ?
It’s not possible to add db.* files to gitignore and regenerate them individually in the final host?
In my case I don’t want to migrate ubtheme tables, local env was a clean installation.
Hi there,
In my case I don’t want to migrate ubtheme tables, local env was a clean installation.
There’s an alternative option that I highly recommend you consider to follow is to create a fresh M2 instance and install our migration tool, instead of following manual tweaks as per my previous reply. This would be way simpler.
Regards,
Mall.
As you know, we use git to code versioning, as a lot of companies. So if we don’t use git, we have to apply pub/ub-tool modificacions again and again, with the possibility of committing carelessness and forgetting things. And wasting time, because doing the work already done is wasting time with the tools we have today.
And we are working a couple of people in different projects in the same instance so, we cannot work with your way.
Hi there,
we are working a couple of people in different projects in the same instance
I wonder if your approach is to use our migration tool for multiple Magento 1 databases? And the first pull of your repo is a fresh M2 instance with our tool installed?
If yes, then the answer to your question below is yes as well:
It’s not possible to add db.* files to gitignore and regenerate them individually in the final host?
Under this circumstance, even though the source code of our migration is in place, you still need to re-install following our guideline. This is aimed at letting Magento regenerate needed tables and database config files that need for our tool.
Regards,
Mall.
