encukou
commented
4 years ago Note that some tasks also have downloadable files: tests or "skeletons" with blanks to fill in.
Open messa opened 5 years ago
encukou
commented
4 years ago Note that some tasks also have downloadable files: tests or "skeletons" with blanks to fill in.
Right now images for tasks (mostly diagrams) are in the static folder (
frontend/static/tasks). That's not very scalable. Images should be closer to task data, for example right indata/2018_pyladies_praha_autumn/homeworks.Things to think about:
Leverage git LFS somehow? Probably should not be needed - the images are small (in file size) so far.
Right now the images are just screenshots of the original homework handout PDFs. But in future the images will be generated from some kind of original file (sometimes even source code). Maybe some Makefile would be enough for handling this? Should be the resulting images commited to git? (I think yes.)
All course data, including task data and images, should be archived after the course ends and new courses should have their own fresh copy. If there will be any larger images this could be a problem in the future - git can handle copied files easily (AFAIK), but when checked out on dev machine (or even production server) it must not take gigabytes.