TaskConfig
Related Docs:
object TaskConfig
| package tasks
The ActorSystem we're using to manage tasks and host the server.
The URL used by HTMLQuestion and ExternalQuestion question types to submit assignments.
The URL used by HTMLQuestion and ExternalQuestion question types to submit assignments. (See http://docs.aws.amazon.com/AWSMechTurk/latest/AWSMturkAPI/ApiReference_QuestionAnswerDataArticle.html for documentation on these question types.) In particular, if we want to provide our own HTML with which to render the task (which we usually do), instead of using the default "Submit HIT" button, we must make our own HTML form and embed it in the HIT. That form then needs to submit to this URL.
Service for storing and getting finished HIT data
What port we're hosting HTTP at.
What port we're hosting HTTPS at.
The interface (IP address) we're using to host the server.
Whether we are working in production as opposed to the sandbox.
Name of the project we're building your JS files with; used to determine what JS files the client asks for.
Name of the project we're building your JS files with; used to determine what JS
files the client asks for. Needs to agree with the project name in your build.sbt
The domain at which we're hosting our server.
The API hook with which we communicate with MTurk.
The API hook with which we communicate with MTurk. We need a different hook depending on whether we're in sandbox or production, because it uses a different URL.
Contains the global configuration of our usage of the MTurk API, including relevant values (URLs, API hooks) and whether we are running on production or in the sandbox.