Closing as expired, as it's been 10 years since this was filed. The
defaults for apache2's user dir is pretty well established, and changes
to that should really be discussed upstream and/or with debian.
** Changed in: apache2 (Ubuntu)
Status: Confirmed => Opinion
--
You received this
I faced the problem with wordpress installation in userdir. As the user
as no permissions on that dir, PHP scripts can't write files to that
dir. For example Worpdress can't create its configuration file on
install, or install extensions.
This is bad
My solution is to add 'my_user' to
Giving the web server (under www-data or any other user) complete write
access to Wordpress is not a good idea, regardless. The installation
docs even go in depth to tell you how to temporarily make the config
file writeable (say, chmod 666 config.php) so you can run the config
script, then tell
I faced the problem with wordpress installation in userdir. As the user
as no permissions on that dir, PHP scripts can't write files to that
dir. For example Worpdress can't create its configuration file on
install, or install extensions.
This is bad
My solution is to add 'my_user' to
Giving the web server (under www-data or any other user) complete write
access to Wordpress is not a good idea, regardless. The installation
docs even go in depth to tell you how to temporarily make the config
file writeable (say, chmod 666 config.php) so you can run the config
script, then tell
** Package changed: ubuntu-docs (Ubuntu) = apache2 (Ubuntu)
--
Apache2 UserDir defaults to User www-data
https://bugs.launchpad.net/bugs/614195
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
--
Ubuntu-server-bugs
Hi Xeno,
Please can you clarify why this is an issue; is it presenting as a
problem when using dynamic content, such as PHP?
Thanks.
** Changed in: apache2 (Ubuntu)
Status: New = Incomplete
--
Apache2 UserDir defaults to User www-data
https://bugs.launchpad.net/bugs/614195
You received
UserDir is meant specifically to allow read access to ~/public_html,
which it does just fine in the Debian/Ubuntu setup. Perhaps you're
confusing it with suEXEC? I would consider it pretty non-intuitive to
blindly enable suEXEC (a potentially large security risk, if people
don't understand it)
** Package changed: ubuntu-docs (Ubuntu) = apache2 (Ubuntu)
--
Apache2 UserDir defaults to User www-data
https://bugs.launchpad.net/bugs/614195
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi Xeno,
Please can you clarify why this is an issue; is it presenting as a
problem when using dynamic content, such as PHP?
Thanks.
** Changed in: apache2 (Ubuntu)
Status: New = Incomplete
--
Apache2 UserDir defaults to User www-data
https://bugs.launchpad.net/bugs/614195
You received
UserDir is meant specifically to allow read access to ~/public_html,
which it does just fine in the Debian/Ubuntu setup. Perhaps you're
confusing it with suEXEC? I would consider it pretty non-intuitive to
blindly enable suEXEC (a potentially large security risk, if people
don't understand it)
11 matches
Mail list logo
