Ability to sync running server with config file in a single command

[GoogleCodeExporter]

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

Original issue reported on code.google.com by thomas.mangin on 3 Nov 2010 at 3:26

[GoogleCodeExporter]

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 :)

Original comment by MWild1 on 3 Nov 2010 at 3:47

• Changed title: Ability to sync running server with config file in a single command
• Changed state: Accepted
• Added labels: Priority-Medium, Type-Enhancement

[GoogleCodeExporter]

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?

Original comment by googlea...@jenserat.de on 1 May 2011 at 8:29