Include etag/timestamp/hash for courses

pyvec / naucse

A server for open course material

Other

2 stars 9 forks source link

Include etag/timestamp/hash for courses #28

Closed encukou closed 4 years ago

encukou commented 4 years ago

From https://github.com/messa/pyladies-courseware/issues/165:

Currently course structure and lesson contents (list of materials...) are retrieved from course API (i.e. naucse API) only when the backend service is starting. So users don't see any changes to the API data source made after that. Would it be possible to add some "build timestamp" value so it could be easily detected that something changed without having to HEAD many files instead?

hroncok commented 4 years ago

Random thought:

If this is needed for each run separately, we could use the HEAD commit hash of the fork.

If this is needed as one global hash, we cannot use the HEAD commit hash of the main repo, because the forks might have changed while the main repo have not changed.

encukou commented 4 years ago

I think a separate tag for each run/course will be better.