Ci works with an API key right? Why don't we make the production API key read only?

…

On 13 Mar 2018 09:31, "Matthias Feurer" ***@***.***> wrote: After @ArlindKadra <https://github.com/arlindkadra> figured this out I had a brief look at how we could tackle this. All this is based on the premise that we have examples and tutorials in CI to make sure that they keep on working (which rules out the option to comment out code in the tutorial). 1. Work only on the test server. This appears to be pretty boring as there aren't a lot of results for tasks. 2. Only do the uploads to the test server, however, we would not get them if we download all previous results from the live server. 3. Split up the tutorial page into several smaller tutorials in which analysis of runs and upload of runs are separate scripts. Then we could redirect the uploads to the test server without making the other example boring. @joaquinvanschoren <https://github.com/joaquinvanschoren> what do you think about the last solution? You would need to use separate notebooks for presentation then. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#392 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACL7-ppwiIisv7LyX4SpxHngaCw3uT_nks5td8oagaJpZM4R9YUu> .

Uh oh!

CI runs on production server #392

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions