Project

General

Profile

Database Setup After Webserver initialization Shared » History » Revision 3

Revision 2 (Amber Herold, 04/27/2011 02:27 PM) → Revision 3/7 (Amber Herold, 04/27/2011 02:35 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 h3. Option 1: More secure - Restrict Drop and Delete priviledges* 
   
 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> 
 &nbsp; 
 

 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 h3. Option 2: Less secure - Allow all privileges* 
 &nbsp; 
 privileges  

 If you are allowing all privileges, no further steps need to be taken. 

 * *Option h3. Option 3: Allows access from all computers in the domain* 
 &nbsp; 
 domain 

 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> 
 &nbsp; 
 

 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>