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

237 lines
5.5 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
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: 69151c3ebb3e4ecf2bb9b6e2fab2022dc34f8541
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
specs:
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.4)
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
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: ce50f322ce08d43a4a747cf333ea576765d764c4
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
specs:
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
em-http-request (1.0.1)
addressable (>= 2.2.3)
cookiejar
em-socksify
eventmachine (>= 1.0.0.beta.4)
http_parser.rb (>= 0.5.3)
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
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: c7209a58f9eb92e1dc81fb141297f9f257c2fdcb
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
specs:
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
em-synchrony (1.0.0)
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
GIT
remote: git://github.com/oldmoe/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: 3dbaa7c00ff0bb75ad9538cdef176c72de35d231
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
specs:
mysqlplus (0.1.1)
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
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: ed82db7659f624d6c3ca244e4127dad270a484c7
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
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
GEM
remote: http://rubygems.org/
specs:
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
POpen4 (0.1.4)
Platform (>= 0.4.0)
open4
Platform (0.4.0)
cron via whenever for mall spider
2010-11-27 15:59:35 -08:00
aaronh-chronic (0.3.9)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
abstract (1.0.0)
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
actionmailer (3.0.5)
actionpack (= 3.0.5)
security update: rails -> 3.0.4
2011-02-08 17:15:06 -08:00
mail (~> 2.2.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
actionpack (3.0.5)
activemodel (= 3.0.5)
activesupport (= 3.0.5)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
builder (~> 2.1.2)
erubis (~> 2.6.6)
rails 3.0.3, negating arel condition is not(c) instead of c.not now
2010-11-16 14:26:06 -08:00
i18n (~> 0.4)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
rack (~> 1.2.1)
rails 3.0.3, negating arel condition is not(c) instead of c.not now
2010-11-16 14:26:06 -08:00
rack-mount (~> 0.6.13)
security update: rails -> 3.0.4
2011-02-08 17:15:06 -08:00
rack-test (~> 0.5.7)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
tzinfo (~> 0.3.23)
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
activemodel (3.0.5)
activesupport (= 3.0.5)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
builder (~> 2.1.2)
rails 3.0.3, negating arel condition is not(c) instead of c.not now
2010-11-16 14:26:06 -08:00
i18n (~> 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
activerecord (3.0.5)
activemodel (= 3.0.5)
activesupport (= 3.0.5)
rails 3.0.3, negating arel condition is not(c) instead of c.not now
2010-11-16 14:26:06 -08:00
arel (~> 2.0.2)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
tzinfo (~> 0.3.23)
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
activeresource (3.0.5)
activemodel (= 3.0.5)
activesupport (= 3.0.5)
activesupport (3.0.5)
addressable (2.2.6)
arel (2.0.10)
bundle update
2011-02-05 19:51:19 -08:00
bcrypt-ruby (2.1.4)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
builder (2.1.2)
utf-8 support in both ruby 1.9 and 1.8
2011-06-04 15:40:15 -07:00
character-encodings (0.4.1)
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
closure-compiler (1.1.4)
bundle update
2011-02-05 19:51:19 -08:00
compass (0.10.6)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
haml (>= 3.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
cookiejar (0.3.0)
devise (1.1.9)
devise implemented, but not remembering
2011-01-26 10:40:15 -08:00
bcrypt-ruby (~> 2.1.2)
warden (~> 1.0.2)
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
diff-lcs (1.1.3)
em-socksify (0.1.0)
eventmachine
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
erubis (2.6.6)
abstract (>= 1.0.0)
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
factory_girl (2.3.2)
activesupport
factory_girl_rails (1.4.0)
factory_girl (~> 2.3.0)
bundle update
2011-02-05 19:51:19 -08:00
railties (>= 3.0.0)
haml (3.0.25)
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
hoptoad_notifier (2.4.11)
include hoptoad
2010-11-14 13:06:31 -08:00
activesupport
builder
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
http_parser.rb (0.5.3)
i18n (0.6.0)
bundle update
2011-02-05 19:51:19 -08:00
jammit (0.5.4)
a functioning wardrobe
2010-10-10 19:18:42 -07:00
closure-compiler (>= 0.1.0)
yui-compressor (>= 0.9.1)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
json (1.4.6)
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
mail (2.2.19)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
activesupport (>= 2.3.6)
bundle update
2011-02-05 19:51:19 -08:00
i18n (>= 0.4.0)
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)
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
mime-types (1.17.2)
msgpack (0.4.6)
downgrade mysql2, oops
2012-01-12 18:31:50 -08:00
mysql2 (0.2.6)
closet page, closet hanger
2011-07-12 16:37:16 -07:00
nokogiri (1.5.0)
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
open4 (1.3.0)
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
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 (0.3.3)
rack (1.2.5)
rack-fiber_pool (0.9.2)
rack-mount (0.6.14)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
rack (>= 1.0.0)
bundle update
2011-02-05 19:51:19 -08:00
rack-test (0.5.7)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
rack (>= 1.0)
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
rails (3.0.5)
actionmailer (= 3.0.5)
actionpack (= 3.0.5)
activerecord (= 3.0.5)
activeresource (= 3.0.5)
activesupport (= 3.0.5)
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)
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
railties (= 3.0.5)
railties (3.0.5)
actionpack (= 3.0.5)
activesupport (= 3.0.5)
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)
thor (~> 0.14.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
rake (0.9.2.2)
bundle update
2011-02-05 19:51:19 -08:00
rdiscount (1.6.8)
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
redis (2.2.2)
redis-namespace (1.1.0)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
redis (< 3.0.0)
resque (1.15.0)
json (~> 1.4.6)
redis-namespace (>= 0.10.0)
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)
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
resque-scheduler (2.0.0.e)
use resque-retry to reschedule failed jobs
2011-06-21 08:22:45 -07:00
redis (>= 2.0.1)
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
resque (>= 1.15.0)
use resque-retry to reschedule failed jobs
2011-06-21 08:22:45 -07:00
rufus-scheduler
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
right_aws (2.1.0)
right_http_connection (>= 1.2.5)
right_http_connection (1.3.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)
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
rufus-scheduler (2.0.16)
use resque-retry to reschedule failed jobs
2011-06-21 08:22:45 -07:00
tzinfo (>= 0.3.23)
closet lists, round one
2011-07-29 07:52:04 -07:00
sanitize (2.0.3)
nokogiri (< 1.6, >= 1.4.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
sinatra (1.2.8)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
rack (~> 1.1)
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
tilt (>= 1.2.2, < 2.0)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
swf_converter (0.0.3)
bundle update
2011-02-05 19:51:19 -08:00
thor (0.14.6)
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
tilt (1.3.3)
treetop (1.4.10)
polyglot
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
polyglot (>= 0.3.1)
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
tzinfo (0.3.31)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
vegas (0.1.8)
rack (>= 1.0.0)
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
warden (1.0.6)
rack (>= 1.0)
whenever (0.6.8)
cron via whenever for mall spider
2010-11-27 15:59:35 -08:00
aaronh-chronic (>= 0.3.9)
activesupport (>= 2.3.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
will_paginate (3.0.2)
yui-compressor (0.9.6)
POpen4 (>= 0.1.4)
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
utf-8 support in both ruby 1.9 and 1.8
2011-06-04 15:40:15 -07:00
character-encodings (~> 0.4.1)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
compass (~> 0.10.1)
devise implemented, but not remembering
2011-01-26 10:40:15 -08:00
devise (~> 1.1.5)
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)
haml (~> 3.0.18)
include hoptoad
2010-11-14 13:06:31 -08:00
hoptoad_notifier
a functioning wardrobe
2010-10-10 19:18:42 -07:00
jammit (~> 0.5.3)
cache item show pages as a first try :)
2010-12-08 17:15:46 -08:00
memcache-client (~> 1.8.5)
auth works - yaaay
2010-10-18 14:58:45 -07:00
msgpack (~> 0.4.3)
downgrade mysql2, oops
2012-01-12 18:31:50 -08:00
mysql2 (< 0.3)
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
mysqlplus!
closet page, closet hanger
2011-07-12 16:37:16 -07:00
nokogiri (~> 1.5.0)
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)
support concurrent requests. now demands thin and nginx, but hey. it works
2010-10-10 15:46:58 -07:00
rack-fiber_pool
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
rails (= 3.0.5)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
rdiscount (~> 1.6.5)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
resque (~> 1.15.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)
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)
closet lists, round one
2011-07-29 07:52:04 -07:00
sanitize (~> 2.0.3)
moving toward s3 image storage
2011-05-20 16:19:14 -07:00
swf_converter (~> 0.0.3)
cron via whenever for mall spider
2010-11-27 15:59:35 -08:00
whenever (~> 0.6.2)
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
will_paginate (~> 3.0.pre2)
Copy permalink