Move course YAMLs into a folder?

[kwinkunks]

Seems like they will probably get out of hand at some point.

[mtb-za]

I think that this makes a lot of sense. This could also be something that is flexible? If you are only building one course, it might not make too much sense to have another level of organisation? Certainly for our use-cases we should have them in a subfolder though.

[mtb-za]

Been doing some testing, and you can just do something like kosu build courses/my_course.yaml and it seems to work with no issues. This would come down to if we want a pattern like that for users, or if we want it to be able to just use kosu build my_course.yaml. You might be able to just add it to the control file?

The .kosu.yaml needs to be changed to point at the new location for kosu build --all to work, logically enough.

The other downside is that you get a courses folder inside the build folder, and the zip files are placed inside the courses folder. I do not have strong feelings on this, but it is worth documenting that it does work at least.

[kwinkunks]

That's good to know, thanks. I think if we do it, then course_dir should be an option in .kosu.yaml, and should be '.' by default. Then it's clear where things should be and we can keep it tidy so there's no extra dir in the build directory, for example.

Aside: I suppose one could use folders to nest courses arbitrarily... so we at Agile might have a folder of machine learning classes, for example. I think that could be useful, although we'd then need some sort of name-appending syntax like machine-learning--geocomp-mlto avoid creating courses with the same name, which seems like it could get nasty to read and confusing to manage. Maybe the multi-folder thing is a bad idea... Let's park that thought until we actually need it.

[mtb-za]

That seems like a reasonably quick change. I will look at what I can do to make that happen.

[kwinkunks]

Take a look at what other paths should be parameters too - eg the names of some of the other directories, especially prod.