OpenNeo/impress
OpenNeo/impress
1
0
Fork 1
Code Pull requests Activity
impress/Gemfile.lock

392 lines
8.9 KiB
Text
Raw Normal View History

support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
GIT
remote: git://github.com/eventmachine/eventmachine.git
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
revision: 45db519d1f24a965c0da3751f0850ff3c099d5a2
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
specs:
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
eventmachine (1.0.7)
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
infer locale from params, then cookies, then Accept-Language header
2013-01-11 09:07:11 -08:00
GIT
remote: git://github.com/iain/http_accept_language.git
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
revision: 38890b400e3c7bdd348a386f4460632eb42fc7a8
infer locale from params, then cookies, then Accept-Language header
2013-01-11 09:07:11 -08:00
specs:
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
http_accept_language (2.0.5)
infer locale from params, then cookies, then Accept-Language header
2013-01-11 09:07:11 -08:00
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
GIT
remote: git://github.com/igrigorik/em-http-request.git
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
revision: 2b894a29f112b451195d5be2e72176288c8ded6e
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
specs:
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
em-http-request (1.1.2)
addressable (>= 2.3.4)
cookiejar (<= 0.3.0)
em-socksify (>= 0.3)
eventmachine (>= 1.0.3)
http_parser.rb (>= 0.6.0)
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
GIT
remote: git://github.com/igrigorik/em-mysqlplus.git
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
revision: 11d6e1123654b948c1d0a8c9d9077e82420b2846
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
specs:
em-mysqlplus (0.1.5)
eventmachine (>= 0.12.9)
GIT
remote: git://github.com/igrigorik/em-synchrony.git
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
revision: ab7db1c1e7b67a132d742ee640224055c97bba6e
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
specs:
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
em-synchrony (1.0.4)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
eventmachine (>= 1.0.0.beta.1)
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
oops: use public git uri for flex gem
2013-01-26 21:48:59 -08:00
GIT
remote: git://github.com/matchu/flex.git
move item cache sweeping and flex syncing to background tasks
2013-12-08 22:12:05 -08:00
revision: 6d7e3fd6e2845ae978545be67b912323888d1ebb
oops: use public git uri for flex gem
2013-01-26 21:48:59 -08:00
specs:
flex (0.4.1)
multi_json (~> 1.3.4)
progressbar (~> 0.11.0)
prompter (~> 0.1.5)
cut down on pets#load queries
2013-01-28 00:10:25 -08:00
GIT
remote: git://github.com/matchu/globalize3.git
waaay speed up Pet#translate_items A few key changes: * Don't reload the whole pet 8 times!! Sooo many bad things happen, including redundant lookups of everything else and too many item saves and reindexes. Instead, fetch the item data, apply it to the items, and then save the items (once each!) * Updated my branch of globalize3 to be even better at avoiding redundant queries when saving. Woo. * Last realization: wrapping all the item saves in a single transaction works wonders. COMMIT seems to have high overhead, so doing only one took it from 50ms * 10 or whatever to 60ms. Good stuff.
2013-01-28 13:18:11 -08:00
revision: e23277864270131bbee29033f8a3abfb74ffe1f8
cut down on pets#load queries
2013-01-28 00:10:25 -08:00
specs:
globalize3 (0.3.0)
activemodel (>= 3.0.0)
activerecord (>= 3.0.0)
paper_trail (~> 2)
use Neopets::User for username-based closet imports
2012-05-21 09:48:19 -07:00
GIT
remote: git://github.com/matchu/neopets.git
pet states know their localized description
2013-01-31 17:11:15 -08:00
revision: 5d13a720b616ba57fbbd54541f3e5daf02b3fedc
use Neopets::User for username-based closet imports
2012-05-21 09:48:19 -07:00
specs:
pet states know their localized description
2013-01-31 17:11:15 -08:00
neopets (0.2.0)
use Neopets::User for username-based closet imports
2012-05-21 09:48:19 -07:00
nokogiri (~> 1.5.2)
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
GIT
remote: git://github.com/oldmoe/mysqlplus.git
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
revision: 354837499c0c83ddc7dcc0decff2056e36ed4403
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
specs:
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
mysqlplus (0.1.3)
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
move to unstable rocketamf so that it builds hashes from registries, not arrays
2011-01-13 14:22:07 -08:00
GIT
update rocketamf repo
2011-07-31 20:20:04 -07:00
remote: git://github.com/rubyamf/rocketamf.git
fix null zone ID bug TNT has started serving half-removed Corridor of Chance effects: it has the asset ID and URL and all, but the zone ID is blank. RocketAMF has patched the empty key bug, and now we ignore assets associated with empty keys.
2013-05-23 18:48:19 -07:00
revision: 796f591d002b5cf47df436dbcbd6f2ab00e869ed
move to unstable rocketamf so that it builds hashes from registries, not arrays
2011-01-13 14:22:07 -08:00
specs:
update rocketamf repo
2011-07-31 20:20:04 -07:00
RocketAMF (1.0.0)
move to unstable rocketamf so that it builds hashes from registries, not arrays
2011-01-13 14:22:07 -08:00
charge and record donations
2014-09-09 19:06:38 -07:00
GIT
remote: https://github.com/stripe/stripe-ruby
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
revision: 8c6dc1a838db0d39d9083431f6a4a8287f25d814
charge and record donations
2014-09-09 19:06:38 -07:00
specs:
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
stripe (1.23.0)
charge and record donations
2014-09-09 19:06:38 -07:00
json (~> 1.8.1)
rest-client (~> 1.4)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
GEM
remote: http://rubygems.org/
specs:
update to rails 3.2.18
2014-05-06 17:39:57 -07:00
actionmailer (3.2.18)
actionpack (= 3.2.18)
update to rails 3.2.16 for security
2013-12-03 12:48:03 -08:00
mail (~> 2.5.4)
update to rails 3.2.18
2014-05-06 17:39:57 -07:00
actionpack (3.2.18)
activemodel (= 3.2.18)
activesupport (= 3.2.18)
rails 3.1 upgrade - still buggy
2013-03-05 13:10:25 -08:00
builder (~> 3.0.0)
erubis (~> 2.7.0)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
journey (~> 1.0.4)
rack (~> 1.4.5)
rails 3.1 upgrade - still buggy
2013-03-05 13:10:25 -08:00
rack-cache (~> 1.2)
rack-test (~> 0.6.1)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
sprockets (~> 2.2.1)
update to rails 3.2.18
2014-05-06 17:39:57 -07:00
activemodel (3.2.18)
activesupport (= 3.2.18)
rails 3.1 upgrade - still buggy
2013-03-05 13:10:25 -08:00
builder (~> 3.0.0)
update to rails 3.2.18
2014-05-06 17:39:57 -07:00
activerecord (3.2.18)
activemodel (= 3.2.18)
activesupport (= 3.2.18)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
arel (~> 3.0.2)
rails 3.1 upgrade - still buggy
2013-03-05 13:10:25 -08:00
tzinfo (~> 0.3.29)
update to rails 3.2.18
2014-05-06 17:39:57 -07:00
activeresource (3.2.18)
activemodel (= 3.2.18)
activesupport (= 3.2.18)
activesupport (3.2.18)
update to rails 3.2.16 for security
2013-12-03 12:48:03 -08:00
i18n (~> 0.6, >= 0.6.4)
rails 3.1 upgrade - still buggy
2013-03-05 13:10:25 -08:00
multi_json (~> 1.0)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
addressable (2.3.8)
airbrake (3.1.17)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
builder
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
multi_json
update to rails 3.2.16 for security
2013-12-03 12:48:03 -08:00
arel (3.0.3)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
bcrypt (3.1.10)
bcrypt-ruby (3.1.5)
bcrypt (>= 3.1.3)
rails 3.1 upgrade - still buggy
2013-03-05 13:10:25 -08:00
builder (3.0.4)
nvm, downgrade whenever
2015-07-17 15:26:31 -07:00
capistrano (2.15.5)
highline
net-scp (>= 1.0.0)
net-sftp (>= 2.0.0)
net-ssh (>= 2.0.14)
net-ssh-gateway (>= 1.1.0)
security update: rails 3.2.13
2013-03-18 11:25:49 -07:00
carrierwave (0.8.0)
activemodel (>= 3.2.0)
activesupport (>= 3.2.0)
utf-8 support in both ruby 1.9 and 1.8
2011-06-04 15:40:15 -07:00
character-encodings (0.4.1)
fix cron job scheduler
2012-07-24 09:05:34 -07:00
chronic (0.6.7)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
chunky_png (1.3.4)
compass (0.12.7)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
chunky_png (~> 1.2)
fssm (>= 0.2.7)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
sass (~> 3.2.19)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
compass-rails (1.0.3)
compass (>= 0.12.2, < 0.14)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
cookiejar (0.3.0)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
devise (2.2.8)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
bcrypt-ruby (~> 3.0)
orm_adapter (~> 0.1)
railties (~> 3.1)
warden (~> 1.2.1)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
diff-lcs (1.2.5)
dotenv (2.0.1)
charge and record donations
2014-09-09 19:06:38 -07:00
dotenv-deployment (0.0.2)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
dotenv-rails (2.0.1)
dotenv (= 2.0.1)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
dye (0.1.4)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
em-socksify (0.3.0)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
eventmachine (>= 1.0.0.beta.4)
rails 3.1 upgrade - still buggy
2013-03-05 13:10:25 -08:00
erubis (2.7.0)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
excon (0.45.4)
execjs (2.5.2)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
factory_girl (2.6.4)
activesupport (>= 2.3.9)
factory_girl_rails (1.7.0)
factory_girl (~> 2.6.0)
bundle update
2011-02-05 19:51:19 -08:00
railties (>= 3.0.0)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
fog (1.8.0)
outfit thumbnails initial commit
2012-03-15 15:00:29 -07:00
builder
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
excon (~> 0.14)
outfit thumbnails initial commit
2012-03-15 15:00:29 -07:00
formatador (~> 0.2.0)
mime-types
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
multi_json (~> 1.0)
outfit thumbnails initial commit
2012-03-15 15:00:29 -07:00
net-scp (~> 1.0.4)
net-ssh (>= 2.1.3)
nokogiri (~> 1.5.0)
ruby-hmac
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
formatador (0.2.5)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
fssm (0.2.10)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
haml (4.0.6)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
tilt
nvm, downgrade whenever
2015-07-17 15:26:31 -07:00
highline (1.7.2)
update to rails 3.2.16 for security
2013-12-03 12:48:03 -08:00
hike (1.2.3)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
http_parser.rb (0.6.0)
i18n (0.7.0)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
journey (1.0.4)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
json (1.8.3)
launchy (2.4.3)
donation mailer
2014-09-10 12:32:54 -07:00
addressable (~> 2.3)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
letter_opener (1.4.1)
donation mailer
2014-09-10 12:32:54 -07:00
launchy (~> 2.2)
update to rails 3.2.16 for security
2013-12-03 12:48:03 -08:00
mail (2.5.4)
rails 3.0.3, negating arel condition is not(c) instead of c.not now
2010-11-16 14:26:06 -08:00
mime-types (~> 1.16)
treetop (~> 1.4.8)
cache item show pages as a first try :)
2010-12-08 17:15:46 -08:00
memcache-client (1.8.5)
update to rails 3.2.16 for security
2013-12-03 12:48:03 -08:00
mime-types (1.25.1)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
mini_magick (3.8.1)
outfit thumbnails initial commit
2012-03-15 15:00:29 -07:00
subexec (~> 0.2.1)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
msgpack (0.5.12)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
multi_json (1.3.7)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
mysql2 (0.3.18)
outfit thumbnails initial commit
2012-03-15 15:00:29 -07:00
net-scp (1.0.4)
net-ssh (>= 1.99.1)
nvm, downgrade whenever
2015-07-17 15:26:31 -07:00
net-sftp (2.1.2)
net-ssh (>= 2.6.5)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
net-ssh (2.9.2)
nvm, downgrade whenever
2015-07-17 15:26:31 -07:00
net-ssh-gateway (1.2.0)
net-ssh (>= 2.6.5)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
newrelic_rpm (3.12.1.298)
nokogiri (1.5.11)
bump version on openneo auth signatory to ensure we load the correct version
2010-11-28 17:49:34 -08:00
openneo-auth-signatory (0.1.0)
auth works - yaaay
2010-10-18 14:58:45 -07:00
ruby-hmac
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
orm_adapter (0.5.0)
paper_trail (2.7.2)
apply globalize3 to items
2013-01-11 14:20:06 -08:00
activerecord (~> 3.0)
railties (~> 3.0)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
parallel (0.5.21)
track passenger pids for easier monitoring (why do they take so much memory?!)
2013-11-30 17:47:02 -08:00
passenger_monit (0.1.1)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
patron (0.4.20)
polyglot (0.3.5)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
progressbar (0.11.0)
move item cache sweeping and flex syncing to background tasks
2013-12-08 22:12:05 -08:00
prompter (0.1.6)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
dye (>= 0.1.1)
yard (>= 0.6.3)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
rack (1.4.7)
rack-attack (2.2.1)
throttle pet loads per ip
2013-07-02 14:10:01 -07:00
rack
rails 3.1 upgrade - still buggy
2013-03-05 13:10:25 -08:00
rack-cache (1.2)
rack (>= 0.4)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
rack-fiber_pool (0.9.3)
rack-protection (1.5.3)
rails 3.1 upgrade - still buggy
2013-03-05 13:10:25 -08:00
rack
update to rails 3.2.18
2014-05-06 17:39:57 -07:00
rack-ssl (1.3.4)
rails 3.1 upgrade - still buggy
2013-03-05 13:10:25 -08:00
rack
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
rack-test (0.6.3)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
rack (>= 1.0)
update to rails 3.2.18
2014-05-06 17:39:57 -07:00
rails (3.2.18)
actionmailer (= 3.2.18)
actionpack (= 3.2.18)
activerecord (= 3.2.18)
activeresource (= 3.2.18)
activesupport (= 3.2.18)
rails 3.0.3, negating arel condition is not(c) instead of c.not now
2010-11-16 14:26:06 -08:00
bundler (~> 1.0)
update to rails 3.2.18
2014-05-06 17:39:57 -07:00
railties (= 3.2.18)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
rails-i18n (3.0.1)
add rails-i18n for standard rails api translations
2013-01-30 18:57:32 -08:00
i18n (~> 0.5)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
rails (>= 3.0.0, < 4.0.0)
update to rails 3.2.18
2014-05-06 17:39:57 -07:00
railties (3.2.18)
actionpack (= 3.2.18)
activesupport (= 3.2.18)
rails 3.1 upgrade - still buggy
2013-03-05 13:10:25 -08:00
rack-ssl (~> 1.3.2)
rails 3.0.3, negating arel condition is not(c) instead of c.not now
2010-11-16 14:26:06 -08:00
rake (>= 0.8.7)
upgrade to rails 3.0.18 - only patch upgrades, no API changes
2013-01-02 19:44:24 -08:00
rdoc (~> 3.4)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
thor (>= 0.14.6, < 2.0)
Bump rake from 10.4.2 to 13.0.1 Bumps [rake](https://github.com/ruby/rake) from 10.4.2 to 13.0.1. - [Release notes](https://github.com/ruby/rake/releases) - [Changelog](https://github.com/ruby/rake/blob/master/History.rdoc) - [Commits](https://github.com/ruby/rake/compare/v10.4.2...v13.0.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-02-29 00:50:38 -08:00
rake (13.0.1)
bundle update
2011-02-05 19:51:19 -08:00
rdiscount (1.6.8)
rails 3.1 upgrade - still buggy
2013-03-05 13:10:25 -08:00
rdoc (3.12.2)
upgrade to rails 3.0.18 - only patch upgrades, no API changes
2013-01-02 19:44:24 -08:00
json (~> 1.4)
basic modeling buttons no behavior yet, nor are they filtered
2014-01-03 13:11:02 -08:00
react-rails (0.8.0.0)
execjs
rails (>= 3.1)
react-source (= 0.8.0)
react-source (0.8.0)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
redis (3.2.1)
redis-namespace (1.5.2)
redis (~> 3.0, >= 3.0.4)
resque (1.23.1)
update resque to see if maybe it fixes the stupid problems
2013-01-28 01:48:53 -08:00
multi_json (~> 1.0)
redis-namespace (~> 1.0)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
sinatra (>= 0.9.2)
vegas (~> 0.1.2)
use resque-retry to reschedule failed jobs
2011-06-21 08:22:45 -07:00
resque-retry (0.1.0)
resque (>= 1.8.0)
resque-scheduler (>= 1.8.0)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
resque-scheduler (2.0.1)
use resque-retry to reschedule failed jobs
2011-06-21 08:22:45 -07:00
redis (>= 2.0.1)
rails 3.1 upgrade - still buggy
2013-03-05 13:10:25 -08:00
resque (>= 1.20.0)
use resque-retry to reschedule failed jobs
2011-06-21 08:22:45 -07:00
rufus-scheduler
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
rest-client (1.6.9)
mime-types (~> 1.16)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
right_aws (2.1.0)
right_http_connection (>= 1.2.5)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
right_http_connection (1.5.0)
bundle update
2011-02-05 19:51:19 -08:00
rspec (2.0.1)
rspec-core (~> 2.0.1)
rspec-expectations (~> 2.0.1)
rspec-mocks (~> 2.0.1)
rspec-core (2.0.1)
rspec-expectations (2.0.1)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
diff-lcs (>= 1.1.2)
bundle update
2011-02-05 19:51:19 -08:00
rspec-mocks (2.0.1)
rspec-core (~> 2.0.1)
rspec-expectations (~> 2.0.1)
rspec-rails (2.0.1)
rspec (~> 2.0.0)
auth works - yaaay
2010-10-18 14:58:45 -07:00
ruby-hmac (0.4.0)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
rufus-scheduler (3.1.3)
nvm, downgrade whenever
2015-07-17 15:26:31 -07:00
rvm-capistrano (1.5.6)
capistrano (~> 2.15.4)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
sanitize (2.0.6)
nokogiri (>= 1.4.4)
sass (3.2.19)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
sass-rails (3.2.6)
railties (~> 3.2.0)
sass (>= 3.1.10)
tilt (~> 1.3)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
sinatra (1.4.6)
rack (~> 1.4)
rack-protection (~> 1.4)
tilt (>= 1.3, < 3)
sprockets (2.2.3)
rails 3.1 upgrade - still buggy
2013-03-05 13:10:25 -08:00
hike (~> 1.2)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
multi_json (~> 1.0)
rails 3.1 upgrade - still buggy
2013-03-05 13:10:25 -08:00
rack (~> 1.0)
tilt (~> 1.1, != 1.3.0)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
subexec (0.2.3)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
swf_converter (0.0.3)
update to rails 3.2.18
2014-05-06 17:39:57 -07:00
thor (0.19.1)
update to rails 3.2.16 for security
2013-12-03 12:48:03 -08:00
tilt (1.4.1)
treetop (1.4.15)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
polyglot
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
polyglot (>= 0.3.1)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
tzinfo (0.3.44)
uglifier (2.7.1)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
execjs (>= 0.3.0)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
json (>= 1.8.0)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
vegas (0.1.11)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
rack (>= 1.0.0)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
warden (1.2.3)
give SWFs real, unique ID numbers Lots of scary bugs were being caused by the fact that the possibly-duplicate Neopets ID was being treated as an SWF's real primary key, meaning that a save meant for object swf number 123 could be saved to biology swf number 123. Which is awful. This update gives SWFs their own unique internal ID numbers. All external lookups still use the remote ID and the type, meaning that the client side remains totally unchanged (phew). However, all database relationships with SWFs use the new ID numbers, making everything cleaner. Yay. There are probably a few places where it would be appropriate to optimize certain lookups that still depend on remote ID and type. Whatever. Today's goal was to remove crazy glitches that have been floating around like mad. And I think that goal has been met.
2012-01-12 15:17:59 -08:00
rack (>= 1.0)
fix cron job scheduler
2012-07-24 09:05:34 -07:00
whenever (0.7.3)
cron via whenever for mall spider
2010-11-27 15:59:35 -08:00
activesupport (>= 2.3.4)
fix cron job scheduler
2012-07-24 09:05:34 -07:00
chronic (~> 0.6.3)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
will_paginate (3.0.7)
yard (0.8.7.6)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
PLATFORMS
ruby
DEPENDENCIES
move to unstable rocketamf so that it builds hashes from registries, not arrays
2011-01-13 14:22:07 -08:00
RocketAMF!
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
addressable
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
airbrake (~> 3.1.8)
nvm, downgrade whenever
2015-07-17 15:26:31 -07:00
capistrano (~> 2.15.5)
security update: rails 3.2.13
2013-03-18 11:25:49 -07:00
carrierwave (~> 0.8.0)
utf-8 support in both ruby 1.9 and 1.8
2011-06-04 15:40:15 -07:00
character-encodings (~> 0.4.1)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
compass-rails (~> 1.0.3)
devise (~> 2.2.3)
lol false alarm, dotenv-deployment is back for starting resque workers
2014-09-11 20:12:38 -07:00
dotenv-deployment
charge and record donations
2014-09-09 19:06:38 -07:00
dotenv-rails
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
em-http-request!
em-mysqlplus!
em-synchrony!
eventmachine!
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
factory_girl_rails (~> 1.0)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
flex!
fog (~> 1.8.0)
cut down on pets#load queries
2013-01-28 00:10:25 -08:00
globalize3!
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
haml (~> 4.0.0)
infer locale from params, then cookies, then Accept-Language header
2013-01-11 09:07:11 -08:00
http_accept_language!
charge and record donations
2014-09-09 19:06:38 -07:00
json (~> 1.8.1)
donation mailer
2014-09-10 12:32:54 -07:00
letter_opener
cache item show pages as a first try :)
2010-12-08 17:15:46 -08:00
memcache-client (~> 1.8.5)
outfit thumbnails initial commit
2012-03-15 15:00:29 -07:00
mini_magick (~> 3.4)
ruby 2.0.0 compatibility... hopefully.
2013-02-24 22:14:45 -08:00
msgpack (~> 0.5.3)
rails 3.1 upgrade - still buggy
2013-03-05 13:10:25 -08:00
mysql2 (>= 0.3.11)
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
mysqlplus!
pet states know their localized description
2013-01-31 17:11:15 -08:00
neopets (~> 0.2.0)!
new relic
2012-04-08 14:37:32 -07:00
newrelic_rpm
use Neopets::User for username-based closet imports
2012-05-21 09:48:19 -07:00
nokogiri (~> 1.5.2)
bump version on openneo auth signatory to ensure we load the correct version
2010-11-28 17:49:34 -08:00
openneo-auth-signatory (~> 0.1.0)
optimize outfit image generation - 4x speed boost on my box Use the ImageMagick flatten command to generate the output all at once instead of compositing each layer individually, and download the layers in parallel. On my box, saving roopal27 five times took a total of 30 seconds before, whereas now it takes 7 seconds. I expect it to be even better on the production box, where latency is even lower.
2012-07-27 20:07:20 -07:00
parallel (~> 0.5.17)
track passenger pids for easier monitoring (why do they take so much memory?!)
2013-11-30 17:47:02 -08:00
passenger_monit (~> 0.1.1)
globalized search first draft Confirmed features: * Output (retrieval, sorting, etc.) * Name (positive and negative, but new behavior) * Flags (positive and negative) Planned features: * users:owns, user:wants Known issues: * Sets are broken * Don't render properly * Shouldn't actually be done as joined sets, anyway, since we actually want (set1_zone1 OR set1_zone2) AND (set2_zone1 OR set2_zone2), which will require breaking it into multiple terms queries. * Name has regressed: ignores phrases, doesn't require *all* words. While we're breaking sets into multiple queries, maybe we'll do something similar for name. In fact, we really kinda have to if we're gonna keep sorting by name, since "straw hat" returns all hats. Eww.
2013-01-18 21:23:37 -08:00
patron (~> 0.4.18)
throttle pet loads per ip
2013-07-02 14:10:01 -07:00
rack-attack (~> 2.2.0)
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
rack-fiber_pool
update to rails 3.2.18
2014-05-06 17:39:57 -07:00
rails (= 3.2.18)
add rails-i18n for standard rails api translations
2013-01-30 18:57:32 -08:00
rails-i18n
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
rdiscount (~> 1.6.5)
basic modeling buttons no behavior yet, nor are they filtered
2014-01-03 13:11:02 -08:00
react-rails (~> 0.8.0.0)
update resque to see if maybe it fixes the stupid problems
2013-01-28 01:48:53 -08:00
resque (~> 1.23.0)
use resque-retry to reschedule failed jobs
2011-06-21 08:22:45 -07:00
resque-retry (~> 0.1.0)
use dev version of resque-scheduler so we can use its pidfile option
2011-06-21 08:54:32 -07:00
resque-scheduler (~> 2.0.0.d)
translate species/color
2013-01-26 08:34:48 -08:00
rest-client (~> 1.6.7)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
right_aws (~> 2.1.0)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
rspec-rails (~> 2.0.0.beta.22)
nvm, downgrade whenever
2015-07-17 15:26:31 -07:00
rvm-capistrano (~> 1.5.6)
closet lists, round one
2011-07-29 07:52:04 -07:00
sanitize (~> 2.0.3)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
sass-rails (~> 3.2.6)
charge and record donations
2014-09-09 19:06:38 -07:00
stripe!
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
swf_converter (~> 0.0.3)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
uglifier (>= 1.0.3)
fix cron job scheduler
2012-07-24 09:05:34 -07:00
whenever (~> 0.7.3)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
will_paginate (~> 3.0.pre2)
improve app infrastructure to make a dev environment easier to reproduce This commit will require a few changes to the deployment process: * store AWS credentials in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars * store OpenNeo Auth credentials in OPENNEO_AUTH_APP, OPENNEO_AUTH_SERVER, and OPENNEO_AUTH_SECRET env vars STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY are now required, too; better have a good .env. You can always put in dummy values if you have no credentials, though; they only get called up if there's a transaction. SECRET_TOKEN is now an env var, too, but the production deploy process currently replaces config/initializers/secret_token.rb anyway; this might be the way to go later, though.
2015-07-16 14:44:52 -07:00
BUNDLED WITH
1.10.5
Copy permalink