File

mod_migrate_http_upload/README.markdown @ 5173:460f78654864

mod_muc_rtbl: also filter messages This was a bit tricky because we don't want to run the JIDs through SHA256 on each message. Took a while to come up with this simple plan of just caching the SHA256 of the JIDs on the occupants. This will leave some dirt in the occupants after unloading the module, but that should be ok; once they cycle the room, the hashes will be gone. This is direly needed, otherwise, there is a tight race between the moderation activities and the actors joining the room.
author Jonas Schäfer <jonas@wielicki.name>
date Tue, 21 Feb 2023 21:37:27 +0100
parent 4469:6844733ad2f5
line wrap: on
line source

---
summary: mod_http_upload to mod_http_file_share migrator
labels:
- Stage-Alpha
---


This is a migration script for converting records of [mod_http_upload]
into the format used by the new [mod_http_file_share][doc:modules:mod_http_file_share]
which will be available with Prosody 0.12 (currently in trunk).

# Usage

If your main `VirtualHost` is called "example.com" and your HTTP upload
`Component` is called "upload.example.com", then this command would
convert records of existing uploads via [mod_http_upload] to
[mod_http_file_share][doc:modules:mod_http_file_share]:

```bash
sudo prosodyctl mod_migrate_http_upload upload.example.com example.com
```

In order to preserve URLs you will need to configure the
[path][doc:http#path_configuration] to be the same as mod_http_upload:

```lua
Component "upload.example.com" "http_file_share"
http_paths = {
    file_share = "/upload"
}
```