When set up using webapp-config, www-apps/moinmoin-1.6.3 creates files in two directories. HTML, JavaScript, XML, PHP and other contents end up in the /var/www/<vhost>/htdocs subdir, as specified by the -d option for webapp-config. (As expected.) But the configuration and data files always end up in /var/www/<vhost>/moinmoin-1.6.3. This is fine as long as there is only one instance of moinmoin per vhost. But once you set up another instance (by calling webapp-config with a different -d option), the second instance gets its own htdocs subdir - but overwrites the data and config files of the first instance (unless hindered by config file protection, which results in a flood of ._cfg0000* files). Suggested fix: When installed with option "-d XYZ", use XYZ as a subdirectory not only in htdocs, but in moinmoin-1.6.3 too, so multiple instances don't collide. Reproducible: Always
(In reply to comment #0) > When set up using webapp-config, www-apps/moinmoin-1.6.3 creates files in two > directories. HTML, JavaScript, XML, PHP and other contents end up in the > /var/www/<vhost>/htdocs subdir, as specified by the -d option for > webapp-config. (As expected.) > > But the configuration and data files always end up in > /var/www/<vhost>/moinmoin-1.6.3. > > This is fine as long as there is only one instance of moinmoin per vhost. But > once you set up another instance (by calling webapp-config with a different -d > option), the second instance gets its own htdocs subdir - but overwrites the > data and config files of the first instance (unless hindered by config file > protection, which results in a flood of ._cfg0000* files). Yup, problem acknowledged. > > Suggested fix: > > When installed with option "-d XYZ", use XYZ as a subdirectory not only in > htdocs, but in moinmoin-1.6.3 too, so multiple instances don't collide. webapp-config is unable to do such a thing and it is in fact not what we want to do with hostroot files. So I think the only valid solution would be to store the data stuff within htdocs, too. Somewhere in a directory that should get protected via .htaccess. I'm not yet convinced that this is a good solution either because I believe the data should not necessarily be stored within htdocs. There might be some security problem. I'd have to study the moinmoin installation instructions somewhat closer. Other suggestions welcome. > > Reproducible: Always >
I'm trying to pick up where the last maintainer left off. Is this still a problem in 1.50.16-r4?
Cannot tell, really, as I am no longer using Gentoo on any of my machines. Sorry. But unless there have been appropriate changes to webapp-config, I don't see how this could have "gone away".
(In reply to comment #2) > I'm trying to pick up where the last maintainer left off. Is this still a > problem in 1.50.16-r4? This is still a problem, even running against portage HEAD.
(In reply to Devan Franchini from comment #4) > (In reply to comment #2) > > I'm trying to pick up where the last maintainer left off. Is this still a > > problem in 1.50.16-r4? > > This is still a problem, even running against portage HEAD. any fixes here?
I think the question is: can we change a dir name like that without modifying the webapp (see, code) itself or will it cause breakage if we change the name of the dir the webapp expects to find its configuration/data files?
Wow. From IN_PROGRESS to RESOLVED / WONTFIX without so much as a statement?
*** This bug has been marked as a duplicate of bug 550188 ***