Experiment Config.yaml Files

Search…
The config.yaml file provides information to the rest of Pushkin about the experiment. Below is a sample of what one might look like.
1
experimentName: &fullName 'pushkintemplate Experiment'
2
shortName: &shortName 'pushkintemplate'
3
apiControllers:
4
  - mountPath: *shortName
5
    location: 'api controllers'
6
    name: 'mycontroller'
7
worker:
8
  location: 'worker'
9
  service:
10
    image: *shortName
11
    links:
12
      - message-queue
13
      - test_db
14
    environment:
15
      - "AMQP_ADDRESS=amqp://message-queue:5672"
16
      - "DB_USER=postgres"
17
      - "DB_PASS="
18
      - "DB_URL=test_db"
19
      - "DB_NAME=test_db"
20
webPage:
21
  location: 'web page'
22
migrations:
23
  location: 'migrations'
24
seeds:
25
  location: 'seeds'
26
database: 'localtestdb'
27
logo: 'logo512.png'
28
text: 'Enter your experiment description here.'
29
tagline: 'Be a citizen scientist! Try this quiz.'
30
duration: ''
Copied!
Each of the above fields is explained in detail below.
experimentName
The full name of your experiment. This is used as a display name on the website to users.
shortName
This is a short, more computer friendly version of you experiment’s name. It should be unique as it is used as the folder name in the experiments folder.
apiControllers
Note that this is an array. As many API controllers can be used as needed.
mountPath
URL this controller’s endpoint will be available at. Full path is /api/[mountPath].
location
Path relative to config file the CLI will look for this module in.
name
Used in logs.
worker
location
Path relative to config file the CLI will look for this module in.
service
This section is appended to Pushkin’s core Docker Compose file. Note that message-queue is a requirement. If you’re not using the local test database, test_db is not necessary. Database connections credentials should be unique to every user. The defaults are shown here for the testing database.
webPage
location
Path relative to config file the CLI will look for this module in.
migrations
location
Path relative to config file the CLI will look for these files.
seeds
location
Path relative to config file the CLI will look for these files. If you aren’t seeding a database table, set this to ''. Otherwise, if the folder pointed to by location is empty, database setup will fail.
database
A reference to a key defined in the core Pushkin config file. Experiments can share databases. The CLI will use this database to migrate and seed experiment data files. It is not used as connection information for any of the modules running the experiment, since these may or may not be inside containers and cannot use the same connection details as the CLI.
logo, text, tagline, duration, other
You may find it useful to include information about your experiment here that can be used by front-end to describe the experiment to potential subjects. For instance, the default pushkin site template uses:
logo: Image to be used as the logo for the experiment. The logo images should be stored in pushkin/front-end/src/assets/images/quiz.
text: The experiment description to be displayed for users to determine what quiz to play.
tagline: This is the description that shows when a quiz is shared via social media/email.
duration: The average length of the experiment to give users an idea of the time commitment.
Note that no path is given for the logo because the default pushkin site template assumes this is in front-end/src/img.