RE: Is Site Initializer a good option for replicating data from env to env

Prathibha hallur, modified 3 Years ago. New Member Posts: 7 Join Date: 10/21/21 Recent Posts

Hi All,

We have a UAT and Prod environments. If we need developer machine and testing systems to have ENV similar to UAT . will Site initializer implementation help ?

Is copying data folder and database from one env and using the same to setup new machines is a good option?  Or implementing SI is a better option?

Former is the one being used mostly . But would like to know success stories on Site initializer.

 

Regards,

Prathibha

thumbnail
Olaf Kock, modified 3 Years ago. Liferay Legend Posts: 6441 Join Date: 9/23/08 Recent Posts

Deploying a production backup to any test/dev/uat system brings you the most similar content to your actual production system. It also endangers you to send notification mails to actual users of the system (pay special attention to the user accounts that you're using) and might be prohibited by industry standards (e.g. don't try to run with production data in non-prod systems).

On the other hand, it neatly tests/demonstrates that your backup/restore procedures work nicely - I'm sometimes quoted by restricting the use of the word "backup" to cases where you have "recently demonstrated that you can use it to restore to a completely different system" - and this qualifies.

Site Initializers work if you use them on all systems - but if you then divert from what they've created, you have to judge for yourself if the result is "similar enough".

Can't go without this recommended read.

Prathibha hallur, modified 3 Years ago. New Member Posts: 7 Join Date: 10/21/21 Recent Posts

Thanks for your input. 

Not using prod data but using UAT data without realtime users here. 

What is the best practice used in liferay way to get the dev/test machines up and running and which do have content such a UAT and production but may not have users. ( If site initializer is not an option)

Please let me know.