search

Rothamsted-Ecoinformatics / farm_rothamsted

Custom farmOS features for Rothamsted Research.
GNU General Public License v2.0
6 stars 1 forks source link

RothamstedFarm.dev: Create Database Export for Development Testing in Platform.sh #611

Open aislinnpearson opened 7 months ago

aislinnpearson commented 7 months ago

Following a call on the 31st January we agreed we would add a fourth Rothamsted instance which can be used for internal development work and testing (specifically to allow @aislinnpearson and Leo to learn to build FarmOS visualisations). This instance will include the database from Harpenden so that it contains realistic data for testing/ page building. We also agreed that @paul121 could use the database from Harpenden for Platform.sh which acts as a testing platform form for the more formal coded development work carried out by Mike and Paul.

Duplicated and updated issue for #301

aislinnpearson commented 1 month ago

@paul121 - do we need this for the John Deere stuff? I'm thinking its most useful for testing management plans, new core modules, etc before release. But also for training...

@mstenta do we need to do regular database updates for this to work? Or do we just migrate across once?

Sorry if I am failing to understand the technical concepts here...

mstenta commented 1 month ago

@mstenta do we need to do regular database updates for this to work? Or do we just migrate across once?

The basic idea is that we would "copy" the database from one of the "live" instances to this one, and it would have everything that was there at the time of the copy. But at that point they are separate databases, and changes made to one don't affect the other. If we want to "update" the copy, then we would essentially delete it and re-copy. That's a manual process, so it would require effort on my end each time we want to do that, but it's not a huge amount, and I expect that it would only be needed occasionally.

aislinnpearson commented 3 weeks ago

Following discussion with @mstenta and @paul121 on Tuesday we agreed to initially implement this as a platform.sh account because this would both give @paul121 a better development environment and make it possible for myself and Leo to work with coded solutions.

We also agreed that we wouldn't copy files for this database migration because it takes significantly longer to do, but would keep this under review and at @paul121's discretion if he feels like it would be useful for issues such as #645

We didn't write off the idea of having an additional FarmOS account for development testing, but instead agreed we would wait and see if that becomes a 'required' issue.