From a7d95d2811666c35084233bf84faf3ffb03c1f70 Mon Sep 17 00:00:00 2001 From: Petr Stefan Date: Tue, 10 Jan 2017 14:33:45 +0100 Subject: [PATCH] Typographic improvement --- Rewritten-docs.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/Rewritten-docs.md b/Rewritten-docs.md index 4e729c6..d2c2e2d 100644 --- a/Rewritten-docs.md +++ b/Rewritten-docs.md @@ -1113,14 +1113,14 @@ and then folders for temporary files and for results and generally files which should be uploaded back to fileserver with solution results. Of course there has to be hierarchy which separate folders from different workers on the same machines. That is why paths to directories are in format: -${DEFAULT}/${FOLDER}/${WORKER_ID}/${JOB_ID} where default means default working -directory of whole worker, folder is particular directory for some purpose -(archives, evaluation...). Mentioned division of job directories proved to be -flexible and detailed enough, everything is in logical units and where it is -supposed to be which means that searching through this system should be easy. In -addition if solutions of users have access only to evaluation directory then -they do not have access to unnecessary files which is better for overall -security of whole ReCodEx. +`${DEFAULT}/${FOLDER}/${WORKER_ID}/${JOB_ID}` where default means default +working directory of whole worker, folder is particular directory for some +purpose (archives, evaluation, ...). Mentioned division of job directories +proved to be flexible and detailed enough, everything is in logical units and +where it is supposed to be which means that searching through this system should +be easy. In addition if solutions of users have access only to evaluation +directory then they do not have access to unnecessary files which is better for +overall security of whole ReCodEx. As we discovered above worker has job directories but users who are writing and managing job configurations do not know where they are (on some particular @@ -1130,7 +1130,7 @@ represent particular folders. Marks or signs can have form of some kind of special strings which can be called variables. These variables then can be used everywhere where filesystem paths are used within configuration file. This will solve problem with specific worker environment and specific hierarchy of -directories. Final form of variables is \${...} where triple dot is textual +directories. Final form of variables is `${...}` where triple dot is textual description. This format was used because of special dollar sign character which cannot be used within filesystem path, braces are there only to border textual description of variable.