prosody-modules
fe8222112cf4
mod_migrate_http_upload/README.md
Software / code / prosody-modules
File
mod_migrate_http_upload/README.md @ 6199:fe8222112cf4
mod_conversejs: Serve base app at /
This makes things slightly less awkward for the browser to figure out which
URLs belong to a PWA. The app's "start URL" was previously without the '/' and
therefore was not considered within the scope of the PWA. Now the canonical
app URL will always have a '/'.
Prosody/mod_http should take care of redirecting existing links without the
trailing / to the new URL.
If you have an installation at https://prosody/conversejs then it is now at
https://prosody/conversejs/ (the first URL will now redirect to the second
URL if you use it).
The alternative would be to make the PWA scope include the parent, i.e.
the whole of https://prosody/ in this case. This might get messy if other
PWAs are provided by the same site or Prosody installation, however.
| author | Matthew Wild <mwild1@gmail.com> |
|---|---|
| date | Tue, 11 Feb 2025 13:18:38 +0000 |
| parent | 6003:fe081789f7b5 |
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" } ```
