Cache intro

The clever caching system we've built at Greta is different to caching systems you would normally encounter. We realised that rather than hitting your server or CDN's POP for the same data multiple times on every pageload, Greta could load the data once, cache it locally in the end users' browser, and serve it from there for the requests to come. There's no faster way to serve content than from a user's own browser!

For example, if a user of your service loads a video or an image multiple times, the script will decide to cache the data, and it will be stored on the browser's own storage, so that the next time this data is required, it will be served by the cache within the blink of an eye.

The downside of caching systems is often that it limits your ability to update content when necessary, but don't worry - we've thought about this. We have two handy functions to manage Greta's cache system.

The first one allows you to set the duration, learn how to configure it here.

The other one gives you the ability to ensure that your users always have the latest content versions, useful if you for example add a new background that would be served through the same URL as the previous one. Then you can trigger a complete clearing of all users' browser cache. Pretty neat ha? This option is available on the dashboard, but if you feel more comfortable doing it with a command line it's also documented here.