Explanation of Sample Names » History » Revision 7
Revision 6 (Amber Herold, 05/17/2010 04:49 PM) → Revision 7/11 (Anchi Cheng, 05/20/2010 11:35 PM)
h1. Explanation of Sample Names MySQL h3. Names used in the example installation From this point on, you will need to enter database usernames, Leginon/Appion username, user names for different configuration files and your linux login username settings. These are all different. Each serves its own purpose. NOT Leginon or Appion user names. They are usernames required for MySQL database interactions. Consistent names are essential. In our example, we have: |purpose|example name| |database name for the example shown here, the leginon parameters and metadata|leginondb| |database name for database is called "leginondb", the project management|projectdb| |database database is called "projectdb". The MySQL user name prefix for appion processing|ap| |database user name|usr_object| username for Leginon image viewing is the same, "usr_object", and appion processing/reporting from the web = username registered for Leginon running Firstname used in the registration + Lastname used in the registration = fullname entered in leginon.cfg this case does not have a password. ______ [[Configure leginon.cfg|< Configure leginon.cfg]] | [[Configure sinedon.cfg|Configure sinedon.cfg >]] ______