To enable this mode, you juste have to create the `/var/www/peertube/storage/plugins/data/peertube-plugin-livechat/debug_mode` file (replacing `/var/www/peertube/storage/` by the correct path onyour installation).
This file can contain some JSON to enable more advanced options.To have a list of existing parameters, check `server/lib/debug.ts`.Restart Peertube after each content modification.
When debug mode isenabled, youcan restart Prosody using this API call: `http://your_instance.tld/plugins/livechat/router/api/restart_prosody`.This call don't need any authentificaiton.It can be done from a command line, for example using `curl http://your_instance.tld/plugins/livechat/router/api/restart_prosody`.
For Prosody to connect to the debugger, call the API `http://your_instance.tld/plugins/livechat/router/api/restart_prosody?debugger=true`.This call does not need any authentication.It can be done from a command line, for example with `curl http://your_instance.tld/plugins/livechat/router/api/restart_prosody?debugger=true`.Youcan even configure your debug server to launch this request automatically.
There is a tutorial, in french, onthe [Peertube forum](https://framacolibri.org/t/tutoriel-creer-un-environnement-de-developpement-de-plugin-peertube-rapidement-en-utilisant-docker-et-qui-permet-de-tester-la-federation/17631) that explains how to quickly build a dev env using Docker.
Note: for an unknown reason, Prosody can't resolve containers DNS address when using the lua-unbound library.There is a dirty hack in the plugin: just create a `/data/plugins/data/peertube-plugin-livechat/no_lua_unbound` file in your docker-volumes, then restart containers.