Migrating from mautrix-facebook about matrix-docker-ansible-deploy HOT 10 OPEN

I've added a link to that documentation in #3254, but have been unsuccessful in completing it. A few issues:

1. The migration feature isn't there in v0.2.0, so it needs the latest Docker image (which makes my doc link misleading).
2. Database permissions need to be manually altered in order to run the migration, and it's still not straightforward to modify the mautrix-meta-messenger service etc. as needed.
3. Migration requires identical bot name and username prefixes, which I think is only partially supported by the playbook variables.
4. hs_token and as_token may or may not have to be identical, I didn't manage to get it running either way.

At this point, I'm very curious about people who have made the switch already, did you get any message history without db migration? A meta bridge issue mentions backfill, does that pull in old messages?

from matrix-docker-ansible-deploy.

I've started preparing to run migration, but didn't take the plunge yet. I think these configuration variables will be needed to match the old bot username etc. at least.

matrix_mautrix_meta_messenger_appservice_username_prefix: facebook
matrix_mautrix_meta_messenger_bridge_username_prefix: facebook
matrix_mautrix_meta_messenger_version: latest
matrix_mautrix_meta_messenger_bridge_permissions_custom:
  '@<myuser>:{{ matrix_domain }}': admin

I needed version because db migration wasn't enabled in the meta_messenger version used by default. Good luck @MrAnno !

from matrix-docker-ansible-deploy.

@MrAnno I'll be your friend! 😄 Following your instructions now but the meta bridge won't start at the first just setup-all, app registration fails. I suspect it's the bot username and will retry tomorrow with that removed.

from matrix-docker-ansible-deploy.

Migration did not work for me and i had to manually remove each room from my matrix element session and then re-add the chats... it was painful but fine in the end

from matrix-docker-ansible-deploy.

@Joshndroid But did you get chat history? 😱

from matrix-docker-ansible-deploy.

@jswetzen no I lost all history. I am not too concerned with the Facebook messages history though so was okay.

I was more annoyed that I ran everything and it never did the clean up/out. It was weird at first as I thought that the new bridge was broken until I realised that it was the old Facebook bridge rooms and I needed to find the new ones created by the new meta bridge and delete the old ones

from matrix-docker-ansible-deploy.

I lost all history as well, but got hundreds of extra rooms.

The old bridge only created rooms as they were used, this one pulled out to I think at least 6 months.

from matrix-docker-ansible-deploy.

Meta started to enable their e2e encryption automatically, even though I refused to set their PIN thingy for long months:

It seems I can't delay the migration any longer.
I'll let you know if I succeed.

from matrix-docker-ansible-deploy.

It hit me that I don’t actually have a life or friends, so naturally, my first task was to make some new friends and ask them to use Facebook instead of Matrix, just to justify my desire of migrating to the new bridge.

Anyway, three months late, but here are the successful steps of the migration:

1. Enable the new bridge, override the username prefixes (note the _ character in the bridge prefix and the lack of it in the appservice prefix:

matrix_mautrix_meta_messenger_enabled: true
matrix_mautrix_meta_messenger_bridge_username_prefix: facebook_

# only if you want the same bot username as before
# matrix_mautrix_meta_messenger_appservice_username_prefix: facebook

2. Run just setup-all
3. Stop the mautrix-facebook bridge: systemctl stop matrix-mautrix-facebook
4. Exec into the mautrix-meta-messenger container and run the migration command.

docker exec -it matrix-mautrix-meta-messenger bash

/usr/bin/mautrix-meta -c /config/config.yaml -r /config/registration.yaml --no-update \
  --db-migrate-from postgres://matrix_mautrix_facebook:<pass>@matrix-postgres:5432/matrix_mautrix_facebook?sslmode=disable

5. Start the mautrix-facebook bridge again and run clean-rooms
6. Disable mautrix-facebook in your configuration
7. Run just setup-all again
8. Send a login message to the new bridge bot

from matrix-docker-ansible-deploy.

How kind you are, thank you :)

I realized that my steps won't work properly if one wants to use the same appservice username for both bridges.
I didn't mind keeping them separate, the only thing that mattered to me was my existing chat history with others.

from matrix-docker-ansible-deploy.