Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use built-in Heroku support over our custom support. #7

Open
cgc opened this issue May 6, 2021 · 1 comment
Open

Use built-in Heroku support over our custom support. #7

cgc opened this issue May 6, 2021 · 1 comment

Comments

@cgc
Copy link
Contributor

cgc commented May 6, 2021

The complicated startup solution that I wrote last year should actually be superseded by psiTurk's builtin support for Heroku. I think the only change we'd need to add to the README is heroku config:set ON_CLOUD=1 (though b/c we use an older psiTurk version, it may require ON_HEROKU), though I'd want to read the docs and read the script more closely to ensure that's the case. We wouldn't want to directly run those things since they create new files (like Procfile and requirements).

@fredcallaway
Copy link
Owner

This is a case where "if it ain't broke, don't fix it" overrules "there should be one and only one right way to do it" (for me). But if you want to implement and test this, go ahead!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants