-
Notifications
You must be signed in to change notification settings - Fork 12
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
CLI to deploy to JATOS via its API #23
Labels
enhancement
New feature or request
Comments
Interesting idea. Maybe proxying a provided JATOS experiment (URL), except for the assets there? Open to contributions! |
Yea, I haven't given enough thought to how this would work in practice, but here's a similar issue I raised over on JATOS. |
Hi, I made a post in the issue raised over at JATOS. I don't want to cross-post here, so please read it there and hopefully comment: JATOS/JATOS#257 (comment). |
bjoluc
changed the title
Emulate a JATOS environment?
CLI to deploy to JATOS via its API
Apr 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm not sure what it would take to do this (but I think I'm willing to pitch in as-needed)... but I've grown rather annoyed with the import/export loop to test with JATOS. 😅
Do you know if there might be a way to interact with JATOS during a development build? The simplest solution would be to point to something like...
locahost:9000/assets/javascripts/jatos.js
, but that won't actually emulate a true JATOS environment (a la interacting withjatos.batchSession
and equivalents).The text was updated successfully, but these errors were encountered: