earcanal
earcanal
The recommended approach for saving data server-side is to [build your tasks into a Docker container](https://expfactory.github.io/expfactory/generate#detailed-start). There's a bit of a learning curve if you haven't used Docker before, but...
1. You can specify the task order for you participants using `--headless` and `--experiments` (see [Start a Headless Experiment Container](https://expfactory.github.io/expfactory/usage). Regarding your later question about participant numbers, I think you'll...
If you want a single container/URL containing all tasks for (all conditions within) a study then you have to include them all when you `start` the container.
So that's why you need to be able to skip tasks using variables.
Your second bullet ff. is how I do things currently. I've updated the RFE to make it clearer I'm suggesting _server side_ implementation. Making this a "core" feature would avoid...
Yes please :)
Not urgent. Enjoy travel!
Sorry to hear that. I meant don't work too hard!!
This is a step in the right direction, as it allows you to modify `index.html` and associated js in a running container. However, `--no-cache` only *partially* resolves testing obstacles, as...
+1 for this workaround