This script does not work with http servers that run under UNcommon user ID/GID. There is one good http server example in the Debian repos called yaws where the script becomes a problem. yaws runs under user ID/GID yaws/yaws. If one attempts to run setup.sh with a yaws http server, the script does not work.
1.Clicking on "Admin mods" after installation returns this error.
You need to run setup.sh :
./setup.sh $APACHEUSER all
Common Apache users are www-data, apache or nobody
2. Going to the command line and running setup.sh yaws all (because the username/gid is yaws, not the usual) returns no messages when in fact the script has already decided that the user will be www-data because I'm on Debian. About line 27 of the script. if -f /etc/debian_version; ....
There's no message that says how the ownership has been changed after running the script. There's no message saying the user has been chosen for me because I'm on Debian either. In both cases, I'd still have problems because the userID/GID needs to be yaws/yaws in order to make tikiwiki work right.
Perhaps another way to address the problem is to check and see who owns the server process with an lsof -p :portNumber?
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |