Package Details: movim v0.14.bbaa1e4f-1

Git Clone URL: https://aur.archlinux.org/movim.git (read-only)
Package Base: movim
Description: Movim is a decentralized social network, written in PHP and HTML5 and based on the XMPP standard protocol.
Upstream URL: https://movim.eu
Licenses: AGPL3
Provides: movim
Submitter: Ppjet6
Maintainer: Ppjet6
Last Packager: Ppjet6
Votes: 3
Popularity: 0.000211
First Submitted: 2016-11-05 02:49
Last Updated: 2018-11-19 16:22

Latest Comments

Ppjet6 commented on 2017-10-18 12:17

Hi there, thanks for the comment.

The package is not perfect and I'm sure there's a lot of things to fix indeed. I'll try and reply to your points separately.

1. This is already the case for log and config, I will update it to do that for other directories. I create directories which I symlink to the movim folder because movim doesn't yet allow me to specify paths anywhere. I talked to author a while ago about it but I just reported the issue (https://github.com/movim/movim/issues/509).

2. Will see to that once 1. is done.

3. Sure, can do. The best even would be to have movim:movim.

theYinYeti commented on 2017-10-18 11:13

Hi! Thanks a lot for packaging Movim. I hope to use it soon. First, however, I would like some changes in the PKGBUILD, if that is possible:

— Most importantly, no Movim-editable directories should be in /usr (/usr/share/webapps/$_pkgbase/{cache,users}); use /var instead, eg. /var/lib/movim for important data, or /var/cache/movim for data that may be removed at any point without data-integrity consequences. This is the only real showstopper for me.

— Optionally, the systemd service unit should be reasonably hardened, as is often seen in other Archlinux units. Eg, this unit could easily use PrivateTmp, PrivateDevices, and ProtectSystem (provided the previous point has been taken care of).

— Apart from that, I only see a subtle and minor point: I would use root:http rather than http:root for ownership (and thus add Group=http to the systemd unit), because root:http allows a choice to have either only root, or all members of group http, being able to alter the files, whereas http:root is only really useful for _users_ http and root. If I want to let someone alter the web configuration at large, I’d rather add them to the http group than to the root group ;-)

Cheers