Commit graph

74 commits

Author SHA1 Message Date
e60ae13399 lol false alarm, dotenv-deployment is back for starting resque workers 2014-09-11 22:12:38 -05:00
ba5ca2b463 drop dotenv-deployment; env vars now in nginx config, instead :P 2014-09-11 21:58:23 -05:00
bf9916d83b hum dee dum, dotenv-deployment 2014-09-11 21:20:17 -05:00
f11f6374da donation mailer 2014-09-10 14:32:54 -05:00
595b1c2fc5 charge and record donations 2014-09-09 21:11:55 -05:00
a8641a654c update to rails 3.2.18 2014-05-06 20:39:57 -04:00
fd106d7dba basic modeling buttons
no behavior yet, nor are they filtered
2014-01-10 16:25:03 -05:00
728ff60c5f move item cache sweeping and flex syncing to background tasks 2013-12-09 00:12:05 -06:00
5ba01b5672 update to rails 3.2.16 for security 2013-12-03 14:48:03 -06:00
3bf5680476 track passenger pids for easier monitoring (why do they take so much memory?!) 2013-11-30 20:47:02 -05:00
d767953ef3 use addressable 2.3.5 for ruby 2.0 compatibility 2013-07-09 20:06:43 -07:00
abe35c6fd9 throttle pet loads per ip 2013-07-02 14:10:01 -07:00
2501cb5667 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
d7c027718d security update: rails 3.2.13 2013-03-18 13:25:49 -05:00
c7237d7d44 fix a bunch of precompiled-asset-missing errors 2013-03-05 22:26:14 -06:00
5e55423dca now that we're on rails 3.2, mount resque at /resque - just for
meeeeee :)

`User#admin?` is now defined as `name == 'matchu'`. I feel kinda
bad about hardcoding that, but I also don't care enough right
now :P
2013-03-05 21:09:08 -06:00
cf5191d33c phew. rails 3.2.12, including some asset pipeline. still buggy. 2013-03-05 20:08:57 -06:00
250f425509 rails 3.1 upgrade - still buggy 2013-03-05 15:10:25 -06:00
f547a75c40 ruby 2.0.0 compatibility... hopefully. 2013-02-25 01:14:45 -05:00
a568ea53cf json 1.7.7 security update 2013-02-11 13:03:59 -06:00
5985e234da pet states know their localized description 2013-01-31 19:11:15 -06:00
d390e61f5b add rails-i18n for standard rails api translations 2013-01-30 20:57:32 -06:00
8d24304ff5 security update: rails 3.0.20 2013-01-28 15:34:44 -06:00
eab14e31fd 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 15:18:11 -06:00
0e5978d92d update resque to see if maybe it fixes the stupid problems 2013-01-28 03:48:53 -06:00
a39110884d cut down on pets#load queries 2013-01-28 02:10:25 -06:00
c2ae3da11c oops: use public git uri for flex gem 2013-01-26 23:48:59 -06:00
9c37e894f7 translate species/color 2013-01-26 10:34:48 -06:00
6e09b8bc10 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-24 18:24:35 -06:00
d79c225c1e apply globalize3 to items 2013-01-24 18:24:34 -06:00
d96c54f3cc infer locale from params, then cookies, then Accept-Language header 2013-01-24 18:23:21 -06:00
df5c7fe3d4 security upgrade to rails 3.0.19 2013-01-08 20:39:44 -06:00
86b58a0a35 upgrade to rails 3.0.18 - only patch upgrades, no API changes 2013-01-02 22:44:24 -05:00
45524c3d69 newrelic_rpm security upgrade 2012-12-06 14:13:04 -06:00
4a69772cd2 remove N+1 queries on current user outfits page 2012-08-09 18:32:33 -04:00
38a9e620c4 Merge branch 'outfit_thumbnails' 2012-07-31 11:21:28 -04:00
42827362b6 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 23:07:20 -04:00
0633f6012a fix cron job scheduler 2012-07-24 12:05:34 -04:00
220aca9311 outfit thumbnails initial commit 2012-07-16 16:45:26 -04:00
1fb17909b1 update gemfile (mainly for neopets 0.0.2) 2012-06-05 13:41:25 -04:00
c2c6a800f2 track pet state gender/mood 2012-05-23 20:00:38 -04:00
4e7e98beca use Neopets::User for username-based closet imports 2012-05-21 12:48:19 -04:00
64054d412e new relic 2012-04-08 16:37:32 -05:00
f8c8b04929 downgrade mysql2, oops 2012-01-12 20:31:50 -06:00
696b2aedaf 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 17:17:59 -06:00
2be573423f update rocketamf repo 2011-07-31 23:20:04 -04:00
358840076c closet lists, round one 2011-07-29 10:52:04 -04:00
1c84a4bef9 closet page, closet hanger 2011-07-14 13:56:20 -04:00
74482dbf75 use dev version of resque-scheduler so we can use its pidfile option 2011-06-21 11:54:32 -04:00
43f373fc36 use resque-retry to reschedule failed jobs 2011-06-21 11:22:45 -04:00