[Loris-dev] LORIS Development Database Set Up

[Christine Rogers, Ms.]

Hi Eli -
As a side note further to Melanie's answer --

If your intention is to test production-ready code updates on a current copy of your production data -- our practice as a Data Coordinating Centre is to set up a (third) "staging" environment to do this, in addition to production and development environments.
Typically this staging environment is refreshed with a dump of the production database as often as needed/automated.  We set up this 3-pronged system for most projects when we serve as DCC and can advise further.

Best,
Christine


On Tue, Nov 5, 2019 at 9:11 AM Melanie Legault, Mrs <melanie.legault2 at mcgill.ca<mailto:melanie.legault2 at mcgill.ca>> wrote:
Hello Eli,

There is no need to create a new database dump from production every time you start a new project.

If you do all you development on your dev instance before porting to production and keep this dev instance to the same release of LORIS as your prod, both database instance should have the same schema.

It is also a good idea to test a new release of LORIS elsewhere than you production instance first to ensure there is no compatibility problem with your internal development before upgrading you production.

As long as database schema modification are eventually applied to both instance, there is no need to use a datadump to re-synchronize.  Of course the data itself would be out of date but it is normally not a problem for a development instance.


Mélanie Legault | Software developer | Faculty of Medicine | McGill University

3801 University, Montréal, QC H3A 2B4


________________________________
From: loris-dev-bounces at bic.mni.mcgill.ca<mailto:loris-dev-bounces at bic.mni.mcgill.ca> <loris-dev-bounces at bic.mni.mcgill.ca<mailto:loris-dev-bounces at bic.mni.mcgill.ca>> on behalf of Eli Johnson <joh17964 at umn.edu<mailto:joh17964 at umn.edu>>
Sent: November 4, 2019 14:53
To: loris dev <loris-dev at bic.mni.mcgill.ca<mailto:loris-dev at bic.mni.mcgill.ca>>
Subject: [Loris-dev] LORIS Development Database Set Up

Hi all,

We are setting up a development server and database for our instance of LORIS. I am looking for advice on how to best set up and maintain a development database that replicates our production database. From discussion with Dave and Leigh at McGill, it sounds like we will want to clone our production database. This could be done via a mysqldump from the production database which is loaded into the development database.

Several specific questions:
1. I imagine cloning the production database via mysqldump every time would take a bit of time with a larger database. Any advice on this process? Is mysqldump the best method or is there a recommended alternative method to do this?

2. Does anyone have scripts or tools they could share to help automate this process?

3. Will I need to completely clone the production database every time I want to update the development database or is there some way to update it incrementally?

Any additional advice on best practices for this are appreciated!

Thanks,
Eli

Eli Johnson
Researcher
Institute of Child Development
University of Minnesota
joh17964 at umn.edu<mailto:joh17964 at umn.edu>
_______________________________________________
Loris-dev mailing list
Loris-dev at bic.mni.mcgill.ca<mailto:Loris-dev at bic.mni.mcgill.ca>
https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-dev


--

christine.rogers at mcgill.ca<mailto:christine.rogers at mcgill.ca>
McGill Centre for Integrative Neuroscience | MCIN.ca
Montreal Neurological Institute
McGill University | Montreal | Canada
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.bic.mni.mcgill.ca/pipermail/loris-dev/attachments/20191105/5cf20d93/attachment-0001.html>