Database Setup After Webserver initialization Shared » History » Version 2
Amber Herold, 04/27/2011 02:27 PM
1 | 1 | Anchi Cheng | h1. Additional Setup After Webserver initialization |
---|---|---|---|
2 | |||
3 | 2 | Amber Herold | 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. |
4 | 1 | Anchi Cheng | |
5 | 2 | Amber Herold | h3. Option 1: More secure - Restrict Drop and Delete priviledges |
6 | |||
7 | 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: |
||
8 | |||
9 | 1 | Anchi Cheng | <pre> |
10 | GRANT DELETE ON leginondb.ViewerImageStatus TO usr_object@'localhost'; |
||
11 | GRANT DELETE ON leginondb.ImageStatusData TO usr_object@'localhost'; |
||
12 | GRANT DELETE ON projectdb.processingdb TO usr_object@'localhost'; |
||
13 | </pre> |
||
14 | |||
15 | 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: |
||
16 | <pre> |
||
17 | GRANT DELETE ON projectdb.gridboxes TO usr_object@'localhost'; |
||
18 | GRANT DELETE ON projectdb.grids TO usr_object@'localhost'; |
||
19 | GRANT DELETE ON projectdb.gridlocations TO usr_object@'localhost'; |
||
20 | </pre> |
||
21 | 2 | Amber Herold | |
22 | h3. Option 2: Less secure - Allow all privileges |
||
23 | |||
24 | If you are allowing all privileges, no further steps need to be taken. |
||
25 | |||
26 | h3. Option 3: Allows access from all computers in the domain |
||
27 | |||
28 | You may choose to assign a domain to your commands and use a wildcard to allow access from all computers in the domain. |
||
29 | |||
30 | <pre> |
||
31 | GRANT DELETE ON leginondb.ViewerImageStatus TO usr_object@'%.mydomain.edu'; |
||
32 | GRANT DELETE ON leginondb.ImageStatusData TO usr_object@'%.mydomain.edu'; |
||
33 | GRANT DELETE ON projectdb.processingdb TO usr_object@'%.mydomain.edu'; |
||
34 | </pre> |
||
35 | |||
36 | 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: |
||
37 | <pre> |
||
38 | GRANT DELETE ON projectdb.gridboxes TO usr_object@'%.mydomain.edu'; |
||
39 | GRANT DELETE ON projectdb.grids TO usr_object@'%.mydomain.edu'; |
||
40 | GRANT DELETE ON projectdb.gridlocations TO usr_object@'%.mydomain.edu'; |
||
41 | </pre> |