Skip to content
This repository has been archived by the owner on Nov 14, 2018. It is now read-only.

Here's a first pass at using shielded #16

Closed
wants to merge 20 commits into from
Closed

Conversation

chadwhitacre
Copy link
Contributor

Addresses #15 as well as (hopefully) https://github.com/olivierlacan/shields/issues/15.

@chadwhitacre
Copy link
Contributor Author

  • rewrite classes for colors available in shielded
  • write post_compile to install shielded into our dyno slug
  • redeploy at http://origin.badgr.co/ (no HTTPS)
  • shielded is very slow (~2s per img). This would be a great place for a Redis cache keyed to the shielded call.
  • We should cache our calls to backend services, per the caching headers they set. Went with a configurable timeout for this that is global to all services, rather than looking at cache headers per-service.
  • put MaxCDN in front of this, on https://badgr.co/ and http://badgr.co/ ($39/mo for EdgeSSL vs. $20/mo for Heroku SSL)

@chadwhitacre
Copy link
Contributor Author

screen shot 2013-07-30 at 6 23 57 pm

@chadwhitacre
Copy link
Contributor Author

screen shot 2013-07-30 at 7 08 14 pm

@chadwhitacre
Copy link
Contributor Author

Woo-hoo! :D

http://origin.badgr.co/

@chadwhitacre
Copy link
Contributor Author

Caching shielded calls in redis. Working great! Need to cache HTTP calls to backends and then put a CDN in front of ourselves. Then we're down to finishing touches, I think, before we really start promoting this (tinker with homepage, implement another service or four).

This service will make an HTTP call to ourself (the new /random.txt
path) if the value is "random."
This is more descriptive
Add a 2 second sleep and trim the value.
This refreshes transforms asynchronously after the first one. Stale
buttons for stale projects, fresh buttons for fresh projects.
Prevent the long tail from bloating our Redis.
@chadwhitacre
Copy link
Contributor Author

  • tweak favicon.ico for non-flatness
  • make whatever changes to the homepage we're going to make
  • clean up the code contribution story (default_local.env, at least)
  • move python deps to a submodule
  • reset the repo with a force push to clear out heavy accumulated cruft
  • circle in @olivierlacan @ackerdev et al. to coordinate launch promotion

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
1 participant