Repository files navigation

This assumes that your cached endpoint is using Varnish and has thexkey module enabled.You can take a look at our customvarnish-post repository that comes with all required configuration for the cached endpoint.

npm install# Install dependenciescp example.env .env# Copy environment variables file# Open your editor, and fill the environment variables in the `.env` filenpm run start# Start the script

IfS3_ENABLED is set totrue, the first time you run the script you might see an error message saying that the last timestamp file does not exist. This is expected, and the script will create the file automatically at the end of the first run, and will update that file every time it runs.You will not see this error message again after the first run.

You might also get a similar error about a simple date workaround file. This is also expected, and the script will create the file automatically at the end of the first run, and will update that file every time it runs.

Using S3 allows us to trick a bit for the cases wheredateModified returned by the SPARQL query is adate and not adateTime.The trick makes sure that the cache is invalidated for this entry only the first time, and the day after thedateModified date.Without this trick, the cache would be invalidated every time the script runs until the day after its value.

This project is licensed under the MIT License - see theLICENSE file for details.