There is no easy way to get a full reload of the configuration afte change for prosody. So adding and removing vhost, conferences, etc. is tedious. A new command should be created accessible via the telnet server. Prosody could behave like many deamon and perform this reload on reception of a SIGHUP

Yes, config:reload() intentionally *only* reloads the config from disk. Detecting what has changed in the config file between various loads, and then the differences between this and the running server is not trivial. That said, this is something we'll need to look at some day. For the moment config:reload()/host:activate()/host:deactivate() are your friends :)

• owner MattJ
• tags Type-Enhancement Priority-Medium Status-Accepted
• title Ability to sync running server with config file in a single command

I justed stumpeld upon this issue when changing a conference room and doing a "service prosody reload". Maybe Prosody should print some message that prosody reload (looks like it triggers a config:reload()?) does not load all the changes and a prosody restart could be neccessary or even disable prosody reload in init.d-file?

These modules may be useful to those interested in this issue: http://modules.prosody.im/mod_reload_modules.html http://modules.prosody.im/mod_auto_activate_hosts.html

Since https://hg.prosody.im/0.9/rev/abcbcb15205c prosodyctl does print a message about maybe needing to reload individual modules.