Project

General

Profile

Database Setup After Webserver initialization Shared » History » Revision 5

Revision 4 (Amber Herold, 04/27/2011 02:36 PM) → Revision 5/7 (Amber Herold, 04/28/2011 05:54 PM)

h1. Additional Setup After Webserver initialization 

 If your webserver installation is successful, a number of tables will be propagated in the databases. There were several options for setting up databse user privileges recommended in [[Database Server Installation]]. The following additional steps should be taken, depending on which option you previously used. 

 * *Option 1: More secure - Restrict Drop and Delete priviledges* 
   
 If you are using the more secured privilege settings we recommended in [[Database Server Installation]], you should expand the privileges of these three tables at this point: 
   
 <pre> 
 GRANT DELETE ON leginondb.ViewerImageStatus TO usr_object@'localhost'; 
 GRANT DELETE ON leginondb.ImageStatusData TO usr_object@'localhost'; 
 GRANT DELETE ON projectdb.processingdb TO usr_object@'localhost'; 
 </pre> 
 If you use Leginon to do robotic grid screening, you will also need to do the following to grant delete privileges to the these tables at the mysql prompt: 
 <pre> 
 GRANT DELETE ON projectdb.gridboxes TO usr_object@'localhost'; 
 GRANT DELETE ON projectdb.grids TO usr_object@'localhost'; 
 GRANT DELETE ON projectdb.gridlocations TO usr_object@'localhost'; 
 </pre> 

 * *Option 2: Less secure - Allow all privileges* 
 &nbsp; 
 If you are allowing all privileges, no further steps need to be taken. 

 * *Option 3: Allows access from all computers in the domain* 
 &nbsp; 
 You may choose to assign a domain to your commands and use a wildcard to allow access from all computers in the domain. 
 &nbsp; 
 <pre> 
 GRANT DELETE ON leginondb.ViewerImageStatus TO usr_object@'%.mydomain.edu'; 
 GRANT DELETE ON leginondb.ImageStatusData TO usr_object@'%.mydomain.edu'; 
 GRANT DELETE ON projectdb.processingdb TO usr_object@'%.mydomain.edu'; 
 </pre> 
 Again, if you use Leginon to do robotic grid screening, you may want to grant delete privileges to the these tables at the mysql prompt: 
 <pre> 
 GRANT DELETE ON projectdb.gridboxes TO usr_object@'%.mydomain.edu'; 
 GRANT DELETE ON projectdb.grids TO usr_object@'%.mydomain.edu'; 
 GRANT DELETE ON projectdb.gridlocations TO usr_object@'%.mydomain.edu'; 
 </pre>