Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Need best practices for importing old archives (SYN-745) #1578

Closed
matrixbot opened this issue Aug 2, 2016 · 3 comments
Closed

Need best practices for importing old archives (SYN-745) #1578

matrixbot opened this issue Aug 2, 2016 · 3 comments

Comments

@matrixbot
Copy link
Member

Submitted by @​matthew:matrix.org
How do we spoof TSes in old messages? How do we cancel/revert bad imports?

(Imported from https://matrix.org/jira/browse/SYN-745)

@matrixbot
Copy link
Member Author

What about creating a script in Synapse to import data from a JSON file containing users, messages, rooms, etc?

Cancel/revert a bad import wouldn't be a problem in the case of a new server, if anything goes wrong the database can be recreated.

-- Michael Paul

@matrixbot matrixbot changed the title Need best practices for importing old archives (SYN-745) Need best practices for importing old archives (https://github.com/matrix-org/synapse/issues/1578) Nov 7, 2016
@matrixbot matrixbot changed the title Need best practices for importing old archives (https://github.com/matrix-org/synapse/issues/1578) Need best practices for importing old archives (SYN-745) Nov 7, 2016
@ara4n
Copy link
Member

ara4n commented Nov 9, 2016

@richvdh
Copy link
Member

richvdh commented Jul 22, 2021

There's a lot of work going on on this over at matrix-org/matrix-spec-proposals#2716, so I don't think we need to keep this issue open.

@richvdh richvdh closed this as completed Jul 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants