File

mod_server_contact_info/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 5948:254a21a104aa
line wrap: on
line source

---
labels:
- 'Stage-Alpha'
summary: Backported mod_server_contact_info for Prosody 0.12
...

## Overview

In February 2024 we improved the internal API to allow multiple modules to
publish information about the server, this includes mod_pubsub_serverinfo.

Although Prosody 0.12 comes with its own mod_server_contact_info, this version
uses the new API so that 0.12 users can hopefully use mod_pubsub_serverinfo
and other modules which use the new API.

To use it, you must ensure that your Prosody 0.12 deployment is loading *both*
mod_server_contact_info **and** mod_server_info community modules.

Configuration of contact addresses is the same, whatever version of the module
you use. See the official documentation on [Prosody's mod_server_contact_info](https://prosody.im/doc/modules/mod_server_contact_info)
page.

## Compatibility

This module should be compatible with Prosody 0.12, and will fail to load in
later versions (which already provide the same functionality without community
modules).