@ -115,9 +115,9 @@ Worker is cabable of 2 things - download file and upload file. Internally, worke
File server has it's internal directory structure, where all the files are stored. It provides REST API to get them or create new ones. File server doesn't provide authentication or secured connection by itself, but it's supposed to run file server as WSGI script inside a web server (like Apache) with proper configuration. For communication with worker are relevant these commands:
- **GET /submission_archives/<id>.<ext>** - gets an archive with submitted source code and corresponding configuration of this job evaluation
- **GET /tasks/<hash>** - gets a file, common usage is for input files or reference result files
- **PUT /results/<id>.<ext>** - upload archive with evaluation results under specified name (should be same _id_ as name of submission archive)
- **GET /submission_archives/\<id\>.\<ext\>** - gets an archive with submitted source code and corresponding configuration of this job evaluation
- **GET /tasks/\<hash\>** - gets a file, common usage is for input files or reference result files
- **PUT /results/\<id\>.\<ext\>** - upload archive with evaluation results under specified name (should be same _id_ as name of submission archive)
If not specified otherview, `zip` format of archives is used. Symbol `/` in API description is root of file server's domain. If the domain is for example `fs.recodex.org` with SSL support, getting input file for one task could look as GET request to `https://fs.recodex.org/tasks/8b31e12787bdae1b5766ebb8534b0adc10a1c34c`.
Petr Stefan
9 years ago