Dress to Impress, a big fancy Neopets customization tool!
Find a file
Emi Dunn-Rankin 4446209ec4
Merge pull request #4 from openneo:proxy-for-https-images
Sigh, fix HTTPS for images AGAIN with a proxy now
2022-08-02 21:18:11 -07:00
.sass-cache phew. rails 3.2.12, including some asset pipeline. still buggy. 2013-03-05 20:08:57 -06:00
app Sigh, fix HTTPS for images AGAIN with a proxy now 2022-08-02 21:17:52 -07:00
autotest rspec:install 2010-05-14 18:17:10 -04:00
config Use Fastly to cache our PNG assets from S3 2021-05-12 22:50:05 -07:00
db Add db field to override special color 2018-05-09 14:10:20 -07:00
doc rails 3 2010-05-14 18:12:31 -04:00
lib prefer scraped rainbow pool images over pet images 2015-09-05 18:48:41 +00:00
public ignore public/uploads 2015-07-27 13:24:58 -04:00
script rails 3 2010-05-14 18:12:31 -04:00
spec news posts read from the database, with a campaign-supplement classname option :) 2015-09-26 20:37:03 -07:00
test core of pet loading, still needs get image hash, download assets 2010-10-07 10:46:23 -04:00
tmp utf-8 support in both ruby 1.9 and 1.8 2011-06-04 18:40:15 -04:00
vendor nvm, downgrade whenever 2015-07-17 18:26:31 -04:00
.gitignore move some deploy stuff from files into env 2015-07-17 17:47:58 -04:00
bundle rails 3.1 upgrade - still buggy 2013-03-05 15:10:25 -06:00
Capfile move some deploy stuff from files into env 2015-07-17 17:47:58 -04:00
config.ru move async behavior to development_async environment 2010-10-11 18:28:39 -04:00
Gemfile Upgrade Parallel 2022-07-23 21:46:13 -07:00
Gemfile.lock nvm, downgrade whenever 2015-07-17 18:26:31 -04:00
isntall rails 3.1 upgrade - still buggy 2013-03-05 15:10:25 -06:00
LICENSE copy LICENSE from impress repo 2010-07-07 02:34:17 -04:00
Rakefile update Rakefile and tasks to match new version of rake 2013-01-02 23:40:37 -05:00
README replace standard rails readme :P 2010-07-07 02:31:47 -04:00

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.