Conversation
Notices
-
!gnusocial Is there a mechanism for transferring accounts or account data between GNU Social instances? For instance, lets say I run an instance for a while, but eventually have to stop running it for whatever reason. Is there a way for the users on my instance to sign up on another instance and transfer everything over so they don't lose all their posts, images, etc?
-
@echosa I asked the same thing, and it seems the answer is no. People thought it was a good idea though... https://sealion.club/attachment/87030
-
I don't see a big problem in writing some kind of script to move stuff from one database to other. It is matter of 1-2 day of work.
Users would be exported, imported into database, they would get new internal IDs.
Their notices would be exported, and hooked on new IDs. Their likes, whatever is inside, I did not look into it.
General rule is to always make backups. One method is to make a periodical computer job (cron) to make encrypted backups and send it to some outside email address. In the same time, GNU Social file system shall be synchronized daily. That makes it easy to restore information or move users later to other instance.-
@louis I'd be ecstatic to see something like this implemented in GNU Social proper. https://sealion.club/attachment/98277
-
-
-
@echosa I THINK you can backup your account and then load it somewhere else as long as the engine is the same? but I'm not sure how well that works. One of the reasons I don't migrate.
Saturday, 30-Apr-16 20:36:59 UTC from web -
@echosa Yes, you can tell them "hey, I'm moving over here!". Personally I wouldn't want my subscriptions to suddenly change distributor/source, which is the risk of an automated method for that.
-
