| | 28 | === After install, setting up === |
| | 29 | |
| | 30 | * Start the application. |
| | 31 | * After a few moments, you should see the home page with a message telling you the database was created. This means the table structure inserted and some basic metadata was added, such as an 'admin' and 'anonymous' user. |
| | 32 | * Log in with user 'admin', password 'admin' at the login screen. You are returned to the home page. |
| | 33 | * At the homepage you will see a message that you can now prefill the database with example users, permissions and some data. Doing this is highly recommended. |
| | 34 | |
| | 35 | To run analysis, you should install some R packages into the 'libs' folder located in the home directory of your OS user. |
| | 36 | * Go to 'Admin panel' and then 'Install R packages'. Click 'Install' for the packages. |
| | 37 | * If this fails, you should perform R package installation manually to this location. Hint: for Linux and Mac, the location is '~/libs'. |
| | 38 | |
| | 39 | Other admin capabilities include: |
| | 40 | * 'Database status': perform loading / removing the example data, or resetting the database. |
| | 41 | * 'File storage': configure the location where files are stored. |
| | 42 | * 'Users and permissions': management of persons, users, groups, permissions and security tokens. |
| | 43 | * 'Admin utilities': update or remove jobs and subjobs manually. |
| | 44 | * 'Archiver': create database exports in archives (note: just relational data, so no files) or import existing archives. Useful for database migration. |
| | 45 | |
| | 46 | |
