mirrors/prosody
1
0
Fork 0
mirror of https://github.com/bjc/prosody.git synced 2025-04-04 05:37:39 +03:00
Code Issues Projects Releases Packages Wiki Activity Actions

util.startup: Add prosody.started promise to easily execute code after startup

Browse source 
To avoid a race where server-started fires before the promise function body is
run (on next tick), I moved server-started to fire on the next tick, which
seems sensible anyway.

Errors are logged, I'm not sure if we ought to be doing something more here.
I'm sure we'll find out.
This commit is contained in:
Matthew Wild 2023-04-01 11:56:38 +01:00
parent 13084baa38
commit 5ce1fe2603
1 changed files with 14 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

17
util/startup.lua
View file

@ -430,8 +430,16 @@ end
function startup.prepare_to_start()
log("info", "Prosody is using the %s backend for connection handling", server.get_backend());
-- Signal to modules that we are ready to start
prosody.events.fire_event("server-starting");
prosody.start_time = os.time();
prosody.started = require "util.promise".new(function (resolve)
prosody.events.add_handler("server-started", function ()
resolve();
end);
prosody.log("debug", "Firing server-starting event");
prosody.events.fire_event("server-starting");
prosody.start_time = os.time();
end):catch(function (err)
prosody.log("error", "Prosody startup error: %s", err);
end);
end
function startup.init_global_protection()
@ -476,7 +484,10 @@ function startup.log_greeting()
end
function startup.notify_started()
prosody.events.fire_event("server-started");
require "util.timer".add_task(0, function ()
prosody.log("debug", "Firing server-started event");
prosody.events.fire_event("server-started");
end);
end
-- Override logging config (used by prosodyctl)