kredits/contracts
9
1 Fork 0
Code Issues 21 Pull Requests Actions Projects 1 Releases 8 Activity

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

New Issue
Closed
opened 2020-01-16 17:12:17 +00:00 by bumi · 1 comment
bumi commented 2020-01-16 17:12:17 +00:00 (Migrated from github.com)
Copy link
Copy source

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)
Copy link
Copy source

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 environmentfeature labels 2022-07-16 15:24:48 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
good first issue
Good for newcomers
 ipfs
rsk
scaling
bug
Something is not working
 dev environment
Config, builds, CI, deployment, etc.
 docs
Documentation
 duplicate
This issue or pull request already exists
 enhancement
Improving existing functionality
 feature
New functionality
 idea
Something to consider
 invalid
Not a bug
 kredits-1
Small contribution
 kredits-2
Medium contribution
 kredits-3
Large contribution
 question
Looking for an answer
 security
All your base are belong to us
 ui/ux
User interface, process design, etc.
 wontfix
This won't be fixed
release
major
release
minor
release
patch
No labels dev environment feature
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
bkero (bkero) bumi (bumi) fsmanuel (fsmanuel) galfert (galfert) greg (Greg) haythem (haythem) hueso (hueso) raucao (Râu Cao) slvrbckt (Nick Jennings)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kredits/contracts#197