forked from OpenNeo/impress
Dress to Impress, a big fancy Neopets customization tool!
Matt Dunn-Rankin
b31a22d4a1
As part of our project to get off S3 and dramatically reduce costs, we're gonna start serving outfit images that Impress 2020 generates, fronted by Vercel's CDN cache! This should hopefully be just as fast in practice, without requiring an S3 storage cost. (Outfits whose thumbnails are pretty much unused will be evicted from the cache, or never stored in the first place—and regenerated back into the cache on-demand if needed.) One important note is that the image at the URL will no longer be guaranteed to auto-update to reflect the changes to the outfit, because we're including `updated_at` in the URL for caching. (It also isn't guaranteed to _not_ auto-update, though 😅) Our hope is that people aren't using it for that use case so much! If so, though, we have some ways we could build live URLs without putting too much pressure on image generation, e.g. redirects 🤔 This change does _not_ disable actual outfit generation, because I want to keep that running until we see these new URLs succeed for folks. Gonna wait a bit and see if we get bug reports on them! Then, if all goes well, we'll stop enqueueing outfit image jobs altogether, and maybe wind down some of the infrastructure accordingly. |
||
---|---|---|
.sass-cache | ||
app | ||
autotest | ||
config | ||
db | ||
doc | ||
lib | ||
public | ||
script | ||
spec | ||
test | ||
tmp | ||
vendor | ||
.gitignore | ||
bundle | ||
Capfile | ||
config.ru | ||
Gemfile | ||
Gemfile.lock | ||
isntall | ||
LICENSE | ||
Rakefile | ||
README |
An extension of Dress to Impress (PHP) that runs on Ruby on Rails. I wanted to use Rails initially for Impress, but hoped that using PHP would allow me to attract more developers. Looks like that wasn't the case, so I just went with what I loved and made the items database in Rails. Future Impress sections will likely find themselves in this project, rather than the PHP project.