Instructor Notes
This is a placeholder file. Please add content here.
Making a toy dataset
Separating code and configuration
Using standard file locations
Source code control
Adding a license
Upload to WorkflowHub
Accounts on dev.workflowhub.eu
In this part, we are asking learners to interact with a website which we do not directly control.
There are pitfalls here, so we need some prior setup as well as contingencies should anything go wrong. In particular, the current workflowhub.eu system requires administrator approval to create a new team and this could take a day or so (or longer if staff in Manchester are absent). A team must be active in order to upload any content at all.
Assuming this material is ever taught by someone other than Tim Booth, you the tutor will need to create an account, and get a team approved prior to the course. On the day you may create a second account so you can follow the same directions as the participants. For my part I have:
- Main account (team owner): tbooth
- Team for use in course: Submission Tutorial
- Secondary account (to demo as a learner): tbooth2_2
For the learners, you probably want to have them register for WorkflowHub the day before this episode, even though signup is quick and automated. Using a password is fine, but given they also need a GitHub account they are best using GitHub authentication.
They can request membership of the course team and this can very quickly be approved on the dashboard of the team owner.
In the event that that website becomes unavailable, there are screenshots below so we can at least see the process.