File

mod_host_status_check/mod_host_status_check.lua @ 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 2221:3d80f8dba886
line wrap: on
line source

local time = require "socket".gettime;

local heartbeats = module:shared("/*/host_status_check/heartbeats");
local connection_events = module:shared("/*/host_status_check/connection_events");

if prosody.hosts[module.host].type == "component" and module:get_option_string("component_module") == "component" then
	module:hook("component-authenticated", function ()
		connection_events[module.host] = { connected = true; timestamp = time() };
	end);

	-- Note: this event is not in 0.9, and requires a recent 0.10 or trunk build
	module:hook("component-disconnected", function ()
		connection_events[module.host] = { connected = false; timestamp = time() };
	end);

	module:hook("stanza/xmpp:prosody.im/heartbeat:heartbeat", function ()
		heartbeats[module.host] = time();
		return true;
	end);
else
	connection_events[module.host] = { connected = true, timestamp = time() };
end

function module.unload()
	connection_events[module.host] = { connected = false, timestamp = time() };
	heartbeats[module.host] = nil;
end