Dress to Impress, a big fancy Neopets customization tool!
Find a file
Matchu 8a20c9be02 Uninstall resque
Yay, we've deleted all our background tasks!

We'll probably want to replace some of the basic functionality like certain caching? But we can deal with that as we run into it.

The direct motivation here was a seeming version conflict between Rails 4.2's rack dependency and latest Resque's rack dependency... but this is just nice complexity elimination regardless, we want this anyway :3
2023-08-02 12:53:56 -07:00
app Remove outfit image saving 2023-08-02 12:51:10 -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 Uninstall resque 2023-08-02 12:53:56 -07:00
db Set up development database in Vagrant 2023-07-29 11:58:24 -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 Drop NewsPosts model 2023-07-29 11:19:37 -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 Uninstall resque 2023-08-02 12:53:56 -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 Uninstall resque 2023-08-02 12:53:56 -07:00
Gemfile.lock Uninstall resque 2023-08-02 12:53:56 -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.