Directories structure users
From GBWiki
Users are structured under a directory hierarchy. Visit command aliases for shortcut to those file access.
Contents |
Root
In $PHENYXCONFIGFILE, the phenyx.users property points to a directory where each user is represented into a sub directory
User directory
Properties file
user.properties
The main info about one user
- user.name=username
login user name
- user.email=name@example.com
the contact email
- user.groups=default
list of groups (other users) for definition inheritance, separated with comma
- user.job.default.permissions=rwd
Default permission when instanciating a new job
- r: can read
- w: can write file in directory (such as selected peptide matches)
- d: can delete the directory
For example, if a user has only right to read/write, the property is set to 'rw'. Therefore, when he will delete a job, the job will only be removed from its list, but no physically removed from the disk.
- user.roles=admin
The list of roles (comma separated)
- mandatory one (just one of them) Will give access to more menu, cross link access privileges etc.
- admin : administrator privileges
- user : casual user
- anonymous : limited features [guest]
- mandatory one (just one of them) Will give access to more menu, cross link access privileges etc.
- user.access
It replace for the moment roles that were supposed to be thought multiples ...
- privatedb : allows for private databank access (management console)
- user.ui.submission.level=advanced
- advanced : extra convertSpectra.pl argument textfield...
default.job.properties
Limits & usage
We keep track of limit and usage also via properties files
user.limit.properties
job.limit.properties
This file contains limit for individual job limit (typically size, number of peak lists etc.)
user.usage.properties
After each job, the job properties file is summed up into this file, which will be checked versus the user.limit.properties
