1
0
Fork 0
forked from OpenNeo/impress
Dress to Impress, a big fancy Neopets customization tool!
Find a file
Matchu e11cfbf016 Remove OutfitImageUploader and Carrierwave
Ok right, missed this in the outfit image stuff deletion, get rid of the code and library we were using to push those images up to S3!
2023-08-02 13:07:29 -07:00
app Remove OutfitImageUploader and Carrierwave 2023-08-02 13:07:29 -07:00
autotest rspec:install 2010-05-14 18:17:10 -04:00
bin Upgrade to Ruby 2.2.4, Rails 4.0.13 2023-07-21 19:39:32 -07:00
config Remove OutfitImageUploader and Carrierwave 2023-08-02 13:07:29 -07:00
db Delete WardrobeTip model 2023-08-02 13:05:30 -07:00
doc rails 3 2010-05-14 18:12:31 -04:00
lib Uninstall resque 2023-08-02 12:53:56 -07: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 Delete WardrobeTip model 2023-08-02 13:05:30 -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 Remove OutfitImageUploader and Carrierwave 2023-08-02 13:07:29 -07:00
.gitignore Add Vagrantfile for installing Ruby 1.9.3 2023-07-21 17:44:49 -07:00
.ruby-version Upgrade to Ruby 2.2.4, Rails 4.0.13 2023-07-21 19:39:32 -07: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 Remove OutfitImageUploader and Carrierwave 2023-08-02 13:07:29 -07:00
Gemfile.lock Remove OutfitImageUploader and Carrierwave 2023-08-02 13:07:29 -07:00
LICENSE copy LICENSE from impress repo 2010-07-07 02:34:17 -04:00
Rakefile Uninstall resque 2023-08-02 12:53:56 -07:00
README replace standard rails readme :P 2010-07-07 02:31:47 -04:00
Vagrantfile Set up development database in Vagrant 2023-07-29 11:58:24 -07: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.