Skip to content

Releases: NYUCCL/psiTurk

ON_HEROKU to ON_CLOUD backwards compatibility

Choose a tag to compare

@deargle deargle released this 18 Mar 22:16
1d91a6e

Fixes backwards compatibility for translating ON_HEROKU=1 to ON_CLOUD=1

testing travis deploy fix

Pre-release

Choose a tag to compare

@deargle deargle released this 21 Mar 06:14
docs: add static ip flexible cloudflare

first pass

Avoid OWASP api-psiturk-org block

Choose a tag to compare

@deargle deargle released this 17 Mar 18:47
f4859ee

Last week, api-psiturk-org's dreamhost server started blocking attempts to create psiturk ad server ads, because the html in the POST triggers a threat warning. Removing all html comments from ad.html and setting the Content-Type: application/json header on the POST seems to let the ads get through. Sigh.

This release removes all comments from the ad.html created by the example code. You can remove the html comments from your own ad if you're having trouble getting it to post. HTML comments look like this: <!-- -->. You can safely delete them.

Don't forget though, the ad server is being sunset, at some point!

Small bugfixes to the shell's output behavior

Choose a tag to compare

@deargle deargle released this 16 Mar 00:07
9f86efd

Fixed

  • fix shell's error during hit_create that prevented ad url from showing.
  • fix shell's messaging about invalid aws credentials

fix default ad_url port, set to 443

Choose a tag to compare

@deargle deargle released this 15 Mar 22:57
8a49101
Merge pull request #472 from NYUCCL/fix-default-ad-url-port-443

default port should be 443

disable psiturk-heroku-config default creation of psql db

Choose a tag to compare

@deargle deargle released this 15 Mar 20:48
0452682

The currently-undocumented psiturk-heroku-config command no longer attaches a postgresql addon by default. I'm calling this just a bugfix because (1) the docs assume that it doesn't attach the psql database, and (2) that command isn't even documented anyway. Will version-feature-bump when this feature is better thought through.

Disabling because I think this will overall make the transition to v3 smoother.

Fix shell api to use require_quals and block_quals

Choose a tag to compare

@deargle deargle released this 14 Mar 06:39
7c19543

Minor fix to have the shell use require_quals and block_quals, and to have documentation point to the same

v3.0.0

Choose a tag to compare

@deargle deargle released this 13 Mar 23:36

This is a somewhat hasty release since a recent DNS change broke the ability to obtain new psiturk-org api credentials, meaning that the only way to use psiturk now is to host your own ad server. 3.0.0 has changes that make that a lot easier than 2.x, so I'm publishing this to pip so make that transition hopefully-smoother. v2.x will continue to work, as long as use_psiturk_ad_server is set to false.

🎉 Sorry for the headaches! Yay scientific progress! We will publicize this better, soon.

Patch no-aws still-can-do-non-aws-things

Choose a tag to compare

@deargle deargle released this 13 Oct 02:18

Patch to still be able to run non-aws commands without aws credentials

patch bonus amount shell arg

Choose a tag to compare

@deargle deargle released this 21 Sep 23:14
v2.3.10

bump to 2.3.10