Skip to content
This repository has been archived by the owner on Sep 25, 2019. It is now read-only.

Remove Redis and configure Edge caching #104

Closed
Splaktar opened this issue Mar 11, 2017 · 2 comments
Closed

Remove Redis and configure Edge caching #104

Splaktar opened this issue Mar 11, 2017 · 2 comments
Assignees
Milestone

Comments

@Splaktar
Copy link
Contributor

Redis is too much of a problem. If we can get onto GAE Flex via #100, then we can just use managed Memcache instead. But for now, we don't actually need this level of caching and should just use Google's Edge caching via headers.

Here's an example of how to setup Edge caching in Express with TypeScript

routes/index.ts:

import * as express from 'express';

const MAX_AGE = 3600; // 1 hr

function addCache(request: express.Request, response: express.Response, next: express.NextFunction) {
  response.header('Cache-Control', `public, max-age=${MAX_AGE}`);
  response.header('Pragma', 'Public');
  next();
}
@Splaktar Splaktar added this to the v0.3.0 milestone Mar 11, 2017
@Splaktar
Copy link
Contributor Author

After #107 gets merged to remove the SEO prerendering that was being put in Redis, I think that we can do this.

@Splaktar
Copy link
Contributor Author

#107 has been merged. This work should be able to be started.

Splaktar added a commit to Splaktar/hub that referenced this issue Mar 17, 2017
@Splaktar Splaktar self-assigned this Mar 17, 2017
Splaktar added a commit that referenced this issue Mar 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant