Replicate/mirror/port data from one network to another #197

New Issue

raucao · 2020-01-16T17:12:17Z

bumi commented

2020-01-16 17:12:17 +00:00

(Migrated from github.com)

In order to have useful test data we should replicate data from our main instance to some test instance (potentially on a different network)

Current ideas/plan

added June 1, 2021

Script to retrieve all existing data (except ERC20 ownership) from current network; write to local file and/or IPFS document
Script to create all contribution and contributor objects from backup anew (careful with IDs)
Contract addition: allow setting confirmedAtBlock dynamically when creating object, until migration done. Set boolean flag to disallow afterwards

In order to have useful test data we should replicate data from our main instance to some test instance (potentially on a different network) ### Current ideas/plan *added June 1, 2021* * [x] Script to retrieve all existing data (except ERC20 ownership) from current network; write to local file and/or IPFS document * [x] Script to create all contribution and contributor objects from backup anew (careful with IDs) * [x] Contract addition: allow setting `confirmedAtBlock` dynamically when creating object, until migration done. Set boolean flag to disallow afterwards

raucao commented

2020-05-29 08:18:19 +00:00

(Migrated from github.com)

I was just wondering if there's a fairly easy way for me to mirror the current Rinkeby data to my local testnet. Then I had an idea: could this be a function that is only called when deploying the contracts/DAO? By this, I mean it wouldn't usually be allowed to e.g. create a contribution with a confirmed_at in the past, but I guess during contract deployment the function could actually do this by directly storing all data from a JSON dump or something, right?

I was just wondering if there's a fairly easy way for me to mirror the current Rinkeby data to my local testnet. Then I had an idea: could this be a function that is only called when deploying the contracts/DAO? By this, I mean it wouldn't usually be allowed to e.g. create a contribution with a `confirmed_at` in the past, but I guess during contract deployment the function could actually do this by directly storing all data from a JSON dump or something, right?

raucao added the

dev environment

feature

labels 2022-07-16 15:24:48 +00:00

raucao referenced this issue

2022-08-23 18:06:05 +00:00

Add export/import functionality #224

raucao closed this issue

2022-10-23 13:41:51 +00:00

Sign in to join this conversation.