comparison doc/installation.txt @ 2658:d3a8613fd8c3 maint-0.7

merge from HEAD
author Richard Jones <richard@users.sourceforge.net>
date Sat, 07 Aug 2004 22:19:14 +0000
parents 7b2ea468381a
children 89b276643bb5
comparison
equal deleted inserted replaced
2656:b386e8811932 2658:d3a8613fd8c3
470 should also add the username your web server runs as to the group. 470 should also add the username your web server runs as to the group.
471 My group now looks like this:: 471 My group now looks like this::
472 472
473 support:*:1002:jblaine,samh,geezer,mail,apache 473 support:*:1002:jblaine,samh,geezer,mail,apache
474 474
475 The tracker "db" directory should be chmod'ed g+sw so that the group can 475 After this change, you'll need to make sure you restart roundup-server,
476 write to the database, and any new files created in the database will be owned 476 apache and any other long-running process associated with Roundup.
477 by the group. 477 The tracker "db" directory permissions and owner information should be
478 fixed with::
479
480 chmod g+sw db
481 chgrp support db
482
483 This allows the group to write to the database, and any new files
484 created in the database will be owned by the group.
478 485
479 If you're using the mysql or postgresql backend then you'll need to ensure 486 If you're using the mysql or postgresql backend then you'll need to ensure
480 that the tracker user has appropriate permissions to create/modify the 487 that the tracker user has appropriate permissions to create/modify the
481 database. If you're using roundup.cgi, the apache user needs permissions 488 database. If you're using roundup.cgi, the apache user needs permissions
482 to modify the database. Alternatively, explicitly specify a database login 489 to modify the database. Alternatively, explicitly specify a database login

Roundup Issue Tracker: http://roundup-tracker.org/