Michael Milton

Subtasks for my own reference: - [x] Add the `schema` column to `SampleDataType` - [x] Integrate React Admin with MegaQC - [x] Write PR for `ra-jsonapi-client` to fix `count` behaviour:...

I'm using the dockerhub container, and that is working fine, my issue is communicating with the web application from outside the container, in order to upload MultiQC results. I don't...

Actually it can't be anything on the MultiQC side, because I don't intend to run MultiQC again, I just want to upload some existing MultiQC results to a custom server...

Okay, that seems to be the case. You need to configure multiQC before you can use `megaqc upload`.

Hmm, that's a strange error. I am able to upload the file without issue: ``` This is MegaQC v0.1.dev1 * Environment: test * Database type: sqlite * Database path: sqlite:////home/michael/Programming/MegaQC/megaqc.db...

Are you running megaqc simultaneously (which you need to do)? Can you start it in debug mode so we get a full traceback? ```bash export FLASK_DEBUG=1 megaqc run ``` Then...

Hmm so it possibly is succeeding. It's just returning HTML as noted above. I'll have a look into why tomorrow. Can you check if it's visible in the samples page...

I believe he's referring to the config page within MegaQC, e.g. http://localhost:3000/users/multiqc_config. You need to have config that looks a bit like this: ``` megaqc_url: http://localhost:3000/api/upload_data megaqc_access_token: 0UAbE4kR3PkAJHHQeBFXtosQh0k0i9WM3f7y7W92yZ4msR0NafoJCr8LoQVnTOYEHlrhJpFKMjysibl2 ```

Oh, I see the problem. As Phil said, it's submitting to the wrong URL (the homepage), but because MegaQC ignores the POST parameters it just treats it as a normal...

Are you using the crate from crates.io? Those docs relate to the github master branch, which has many more features than the last published crate.