Congratulations on making it official! Big achievement.
I have a few questions that need answers spelling out, I’m afraid:
Can we use prosodyctl (if advisable)? If so, how?
I think I can guess the answer, but can we add email aliases in the Yunohost Users panel and use them as XMPP addresses? Or do our XMPP addresses have to match the domain of the server on which Prosody is installed?
Do we use the global config file (in /etc/prosody/config.cfg.lua) for all modifications?
If I remember correctly, in Metronome we used to modify modules by editing both the master config file and the module’s own config file, which were in two separate locations. I think.
The XEP modules listed in ‘What works’ in the app’s description – is it only the last one that is TBC, or does that ‘TBC’ apply to the whole list?
Thank you. So, as for prosodyctl, do we use it as a command on its own, or do we have to pass it through the Yunohost shell with sudo yunohost app shell prosodyctl?
Either way, this should make it possible to use the Prosody docs more easily.
Separately, is there a built-in way to delete uploaded & sent files from the server without using a cron job?
I know there are automated tools for clearing the mam archive or expiring shared files (http_file_share_expires_after*), but the files remain on the server in /var/xmpp-upload/ and stay there for at least a few hours, if not days, before vanishing. Rather than being deleted, it’s just access to the files that gets removed.
I can set up a cron job if this is the only way; just wasn’t sure if Prosody already had a way.
*This is the new replacement for the http_file_upload module, which apparently became deprecated sometime in the last six months (that link redirects to the http_file_share page).
Hello @jwqos and @cptbichez, it seems there is a missing parameter in the old anubister version:
You could either try to fix it manually, by adding in /etc/yunohost/apps/prosody/scripts/_common.sh :
app=prosody
config_path=/etc/prosody
Or remove the app prosody and then install the app prosody.
To answer my own question in the hope it helps someone else, the Prosody devs say that the software should remove the files itself from your server after a short time, and that newer versions of Prosody (at least 12.4 onwards) are shipped with mod_http_file_share in place of mod_http_upload.
The new Yunohost version of Prosody has mod_http_upload in the VirtualHost config files (separate from the global config file), so I imagine it will be phased out in an update at some stage.
i tried the other way around,
by remove i understood ‘remove the app and install it again’ and it worked. i did not removed the files when removing the app though. i don’t know if it will change anything overtime.
I removed prosody then install it form the webinterface, one server all good. The other one it won’t start, I tried three times already verifying which domain it’s isntall, but in the end it always gets installed on a subdomain I didn’t really choose.:
Apr 27 22:33:24 prosody[140332]: A problem occurred while reading the config file /etc/prosody/prosody.cfg.lua
Apr 27 22:33:24 prosody[140332]: Error: Error loading included /etc/prosody/conf.d/subdomain.xxxx.noho.st.cfg.lua: /etc/prosody/conf.d/.subdomain.xxxx.noho.st.cfg.lua: Permission denied
Apr 27 22:33:24 prosody[140332]: More help on configuring Prosody can be found at https://prosody.im/doc/configure
Apr 27 22:33:24 prosody[140332]: Good luck!
Apr 27 22:33:24 prosody[140332]: **************************
Apr 27 22:33:24 systemd[1]: prosody.service: Main process exited, code=exited, status=1/FAILURE
Apr 27 22:33:24 systemd[1]: prosody.service: Failed with result 'exit-code'.
Then you might want have a try of Movim which is implementing Stickers
(but unfortunately hosting our own Movim instance with Yunohost is not yet working (subliminal message if some people with JS knowledges are reading this!))
