-
Notifications
You must be signed in to change notification settings - Fork 5
Plato configuration
Plato can be configured through a properties file in three locations:
- At the user level at ~/.plato/configuration.properties
- At the system level at /etc/plato/configuration.properties
- Default values at classpath:config/configuration.properties
The upper locations take precedence over the lower locations. Configuration can contain variables that reference, for example, OS-specific environment variables. See the Apache Commons Configuration user guide for further details. You can change the location of the user or system configuration by providing configuration options during build.
mvn package -Dconfiguration.location.user=~/.plato -Dconfiguration.location.system=/etc/plato
Plato stores binary data on the filesystem. You can define the location of the filestorage in this configuration file.
Key | Default | Description |
---|---|---|
filestorage.path | ${env\:JBOSS_HOME}/standalone/data/plato/filestorage |
Path to the file storage where files of plans (e.g. samples, experiment results, workflows) are stored. |
filestorage.repository.name | plato |
Namespace for the object PID according to Fedora Identifiers. |
Key | Default | Description |
---|---|---|
mail.from | plato@localhost |
Email address used as sender when sending mails |
mail.feedback | ${mail.from} |
Email address where user feedback will be sent to |
mail.smtp.host | emtpy | SMTP server used for sending mails |
If you want to deploy triggers to Scout you have to configure the endpoint
Key | Default | Description |
---|---|---|
watch.rest.uri | http://localhost:9998/api/ |
Address of the Scout endpoint to deploy triggers |
watch.rest.user | admin |
User to connect to the endpoint |
watch.rest.password | admin |
Password of the user to connect to the endpoint |
Planning experiments can be run on an external server over SSH. Plato will connect to the server with the provided username. The user can either be authenticated with a private key or password.
- If tavernaserver.ssh.privatekey.location is set, use the key with tavernaserver.ssh.privatekey.password as password.
- Otherwise if tavernaserver.ssh.password is set, use this password.
- Otherwise use the private key from a typical OS specific location (e.g. ~/.ssh). The key must not be password protected.
If tavernaserver.ssh.fingerprint is specified, the fingerprint of the server is verified.
Key | Default | Description |
---|---|---|
tavernaserver.ssh.host | localhost |
Hostname of the server |
tavernaserver.ssh.port | 22 |
Port of the server |
tavernaserver.ssh.command.timeout | 600 |
Timeout for remote commands |
tavernaserver.ssh.command | $TAVERNA_HOME/executeworkflow.sh -inputdoc %%inputdoc%% -outputdoc %%outputdoc%% %%workflow%% |
Taverna execution command |
tavernaserver.ssh.user | plato |
Username for authentication |
tavernaserver.ssh.fingerprint | empty | Server fingerprint to check, the check will be omitted if no fingerprint is specified |
tavernaserver.ssh.privatekey.location | empty | Private key location |
tavernaserver.ssh.privatekey.password | empty | Private key password |
tavernaserver.ssh.password | empty | Password |
tavernaserver.ssh.server.cleanup | false |
Clean up files on server after each command |
MyExperiment contains preservation components for migration, characterisation and quality assurance. These can be used to define alternatives, migrate files and evaluate criteria.
Key | Default | Description |
---|---|---|
myexperiment.rest.uri | http://www.myexperiment.org/ |
URI of the myExperiment instance for preservation components |
Key | Default | Description |
---|---|---|
minimee.home | Path to the minimee installation directory |
Key | Default | Description |
---|---|---|
mail.from | plato@localhost |
Email address used as sender when sending mails |
mail.smtp.host | emtpy | SMTP server used for sending mails |
Key | Default | Description |
---|---|---|
recaptcha.publickey | empty | Public key for the reCaptcha API |
recaptcha.privatekey | empty | Private key for the reCaptcha API |