![]() ![]() This makes your server a completely new one from the point of view of the network, You are changing the server_name in the homeserver configuration.Instance, a local deployment which the outside world can't talk to. You have never joined any rooms which are federated with other servers.There are two exceptions when it might be sensible to delete your database and start again: In general, there are better solutions to any problem than dropping the database. Think that you are not, and you'll probably be unable to interact with that room Network: lots of other servers have information about your server.įor example: other servers might think that you are in a room, your server will Slate by dropping your database, but things don't work like that in a federated It's easy to make the mistake of thinking that you can start again from a clean Can I just delete my database and start again?ĭeleting your database is unlikely to make anything better. Alternatively, a server adminĬan reset a user's password using the admin API. Users can reset their password through their client. If ! wget -o /dev/null -P $target_directory $url then Url=$repository_url/_matrix/media/v3/download/$serverName/$filename download_media.sh /tmp/export_data/media_ids/ /tmp/export_data/media_files/ # serverName: Name of the server (`server_name` from homeserver.yaml). # repository_url: Address of the media repository resp. # target_directory: Directory into which all files are to be downloaded. # source_directory: Directory which contains the export with the media_ids. ![]() The following script can help with download the media files: #!/usr/bin/env bash Media that have been sent in encrypted rooms are only retrieved in encrypted form. With the media_ids the media files can be downloaded. Is used, the data must be exported separately. ![]() The media_ids folder contains only the metadata of the media uploaded by the user.įurthermore, only the media_ids that Synapse manages itself are exported. The exported data has the following layout: output-directory If this parameter is not provided, Synapse defaults to creatingĪ temporary directory (which starts with "synapse-exfiltrate") in /tmp, output-directory parameter ensure that the provided directory isĮmpty. The directory to store the export data in can be customised with the To run Synapse: poetry run python -m _cmd -c export-data -output-directory It takes the homeserverĬonfiguration file and the full Matrix ID of the user to export: python -m _cmd -c export-data -output-directory Synapse includes a Python command to export data for a specific user. What users are registered on my server? SELECT NAME from users WHERE room_id = '!cURbafjkfsMDVwdRDQ:' AND membership = 'join' INNER JOIN room_memberships AS m USING (room_id, event_id) Run this sql query on your db: SELECT DISTINCT split_part(state_key, ':', 2) What servers are currently participating in this room? Run this sql query on your db: SELECT * FROM destinations UPDATE users SET admin = 1 WHERE name = servers are my server talking to? Generally not recommended so once you have an admin account: use the admin APIs So you'll have to edit the database manually. If you don't have any admin accounts yet you won't be able to use the admin API, To promote other accounts to become admins. If your server already has an admin account you should use the
0 Comments
Leave a Reply. |