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

398 lines
9.2 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
Update gems Ha, I forgot we're including all the vendored gems in the git repo. Maybe that's worth changing? But fine to leave as-is for now.
2023-07-21 18:07:36 -07:00
remote: https://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
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
GEM
Update most URLs to use HTTPS I noticed we didn't have the little lock icon in the browser, and yeah huh there's a lot of `http://` still floating around! Let's fix that!
2023-10-25 15:16:46 -07:00
remote: https://rubygems.org/
upgrade to rails 3, make item tests pass
2010-10-03 16:49:33 -07:00
specs:
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
actioncable (7.1.1)
actionpack (= 7.1.1)
activesupport (= 7.1.1)
Upgrade to Rails 5.2.8.1 Some important little upgrades but mostly straightforward! Note that there's still a known issue where item searches crash, I was hoping that this was a bug in Rails 4.2 that would be fixed on upgading to 5, but nope, oh well! Also uhh I just got a bit silly and didn't actually mean to go all the way to 5.2 in one go, I had meant to start at 5.0… but tbh the 5.1 and 5.2 changes seem small, and this seems to be working, so. Yeah ok let's roll!
2023-08-02 16:05:02 -07:00
nio4r (~> 2.0)
websocket-driver (>= 0.6.1)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
zeitwerk (~> 2.6)
actionmailbox (7.1.1)
actionpack (= 7.1.1)
activejob (= 7.1.1)
activerecord (= 7.1.1)
activestorage (= 7.1.1)
activesupport (= 7.1.1)
Upgrade to Rails 6.0.6.1 Another pretty easy one! We have the `rails app:update` changes in here too.
2023-08-02 17:27:11 -07:00
mail (>= 2.7.1)
Upgrade to Rails 7.0.6 Whew! Seems like a pretty clean one? Ran `rails app:upgrade` and stuff, and made some corrections to keyword arguments for `translate` calls. There might be more such problems elsewhere? But that's hard to search for, and we'll have to see.
2023-08-03 16:37:45 -07:00
net-imap
net-pop
net-smtp
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
actionmailer (7.1.1)
actionpack (= 7.1.1)
actionview (= 7.1.1)
activejob (= 7.1.1)
activesupport (= 7.1.1)
Upgrade to Ruby 2.2.4, Rails 4.0.13 NOTE: This doesn't boot yet! There's something changed in the `devise` API that we'll need to fix! ``` /vagrant/config/initializers/devise.rb:46:in `block in <top (required)>': undefined method `encryptor=' for Devise:Module (NoMethodError) ``` But yeah, we navigated the gem upgrades, and also I ran `rake rails:update` and hand-processed the suggestions it had for our config files.
2023-07-21 19:39:32 -07:00
mail (~> 2.5, >= 2.5.4)
Upgrade to Rails 7.0.6 Whew! Seems like a pretty clean one? Ran `rails app:upgrade` and stuff, and made some corrections to keyword arguments for `translate` calls. There might be more such problems elsewhere? But that's hard to search for, and we'll have to see.
2023-08-03 16:37:45 -07:00
net-imap
net-pop
net-smtp
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
rails-dom-testing (~> 2.2)
actionpack (7.1.1)
actionview (= 7.1.1)
activesupport (= 7.1.1)
nokogiri (>= 1.8.5)
rack (>= 2.2.4)
rack-session (>= 1.0.1)
Upgrade to Rails 5.2.8.1 Some important little upgrades but mostly straightforward! Note that there's still a known issue where item searches crash, I was hoping that this was a bug in Rails 4.2 that would be fixed on upgading to 5, but nope, oh well! Also uhh I just got a bit silly and didn't actually mean to go all the way to 5.2 in one go, I had meant to start at 5.0… but tbh the 5.1 and 5.2 changes seem small, and this seems to be working, so. Yeah ok let's roll!
2023-08-02 16:05:02 -07:00
rack-test (>= 0.6.3)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
rails-dom-testing (~> 2.2)
rails-html-sanitizer (~> 1.6)
actiontext (7.1.1)
actionpack (= 7.1.1)
activerecord (= 7.1.1)
activestorage (= 7.1.1)
activesupport (= 7.1.1)
Upgrade to Rails 7.0.6 Whew! Seems like a pretty clean one? Ran `rails app:upgrade` and stuff, and made some corrections to keyword arguments for `translate` calls. There might be more such problems elsewhere? But that's hard to search for, and we'll have to see.
2023-08-03 16:37:45 -07:00
globalid (>= 0.6.0)
Upgrade to Rails 6.0.6.1 Another pretty easy one! We have the `rails app:update` changes in here too.
2023-08-02 17:27:11 -07:00
nokogiri (>= 1.8.5)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
actionview (7.1.1)
activesupport (= 7.1.1)
Update gems to Rails 4.1 (crashes!) Lookin' good on this end, but the server isn't starting up yet, got some fixes to make!
2023-07-29 11:33:39 -07:00
builder (~> 3.1)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
erubi (~> 1.11)
rails-dom-testing (~> 2.2)
rails-html-sanitizer (~> 1.6)
activejob (7.1.1)
activesupport (= 7.1.1)
Upgrade to Rails 5.2.8.1 Some important little upgrades but mostly straightforward! Note that there's still a known issue where item searches crash, I was hoping that this was a bug in Rails 4.2 that would be fixed on upgading to 5, but nope, oh well! Also uhh I just got a bit silly and didn't actually mean to go all the way to 5.2 in one go, I had meant to start at 5.0… but tbh the 5.1 and 5.2 changes seem small, and this seems to be working, so. Yeah ok let's roll!
2023-08-02 16:05:02 -07:00
globalid (>= 0.3.6)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
activemodel (7.1.1)
activesupport (= 7.1.1)
activerecord (7.1.1)
activemodel (= 7.1.1)
activesupport (= 7.1.1)
timeout (>= 0.4.0)
activestorage (7.1.1)
actionpack (= 7.1.1)
activejob (= 7.1.1)
activerecord (= 7.1.1)
activesupport (= 7.1.1)
Upgrade to Rails 6.0.6.1 Another pretty easy one! We have the `rails app:update` changes in here too.
2023-08-02 17:27:11 -07:00
marcel (~> 1.0)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
activesupport (7.1.1)
base64
bigdecimal
Upgrade to Rails 5.2.8.1 Some important little upgrades but mostly straightforward! Note that there's still a known issue where item searches crash, I was hoping that this was a bug in Rails 4.2 that would be fixed on upgading to 5, but nope, oh well! Also uhh I just got a bit silly and didn't actually mean to go all the way to 5.2 in one go, I had meant to start at 5.0… but tbh the 5.1 and 5.2 changes seem small, and this seems to be working, so. Yeah ok let's roll!
2023-08-02 16:05:02 -07:00
concurrent-ruby (~> 1.0, >= 1.0.2)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
connection_pool (>= 2.2.5)
drb
Upgrade to Rails 6.1.7.4 This one was pretty straightforward yaay! Main thing was the change from `render file` to `render template` in a couple places, oh and a thing with complex `order()` clauses.
2023-08-02 17:55:32 -07:00
i18n (>= 1.6, < 2)
minitest (>= 5.1)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
mutex_m
Upgrade to Rails 6.1.7.4 This one was pretty straightforward yaay! Main thing was the change from `render file` to `render template` in a couple places, oh and a thing with complex `order()` clauses.
2023-08-02 17:55:32 -07:00
tzinfo (~> 2.0)
Update all our gems as far as we can Got pretty far, there's a couple still held back by Rails 6+, but yeah doing great!
2023-08-02 17:16:24 -07:00
addressable (2.8.4)
public_suffix (>= 2.0.2, < 6.0)
Move manifest backfill to `swf_assets:manifests` task Okay, I've simplified the migration to *just* add the column, and instead added a task to find assets without manifest URLs and backfill them. Performance is a lot better now, using the `async-http` library, which as I understand it supports both persistent connections when invoked like this, and maybe also HTTP/2 multiplexing?? (Though I'm not actually sure images.neopets.com does lol) I'm not sure about the number of concurrent tasks I picked here, 100 seems okay for an internet thing and for such small requests, but I worry that the CDN is gonna get annoyed or something. Well, we'll see! This task is very resumable if it turns out we get frozen out or something.
2023-11-10 16:52:50 -08:00
async (2.6.5)
console (~> 1.10)
fiber-annotation
io-event (~> 1.1)
timers (~> 4.1)
Replace falcon server with puma Been wanting this for a while in theory, gonna actually do it now! The motivation is that I want to turn up the timeout for loading pets, because the Neopets endpoints are slower today with the NC UC release - but I can already predict that under our current architecture that will be a problem, because it'll block up our request queue! Falcon uses Ruby's relatively-new async system to *not* have requests block on upstream requests, and my understanding is that this behavior is plug-and-play. Let's see how it goes!
2024-01-23 21:47:51 -08:00
async-container (0.16.12)
async
async-io
Move manifest backfill to `swf_assets:manifests` task Okay, I've simplified the migration to *just* add the column, and instead added a task to find assets without manifest URLs and backfill them. Performance is a lot better now, using the `async-http` library, which as I understand it supports both persistent connections when invoked like this, and maybe also HTTP/2 multiplexing?? (Though I'm not actually sure images.neopets.com does lol) I'm not sure about the number of concurrent tasks I picked here, 100 seems okay for an internet thing and for such small requests, but I worry that the CDN is gonna get annoyed or something. Well, we'll see! This task is very resumable if it turns out we get frozen out or something.
2023-11-10 16:52:50 -08:00
async-http (0.61.0)
async (>= 1.25)
async-io (>= 1.28)
async-pool (>= 0.2)
protocol-http (~> 0.25.0)
protocol-http1 (~> 0.16.0)
protocol-http2 (~> 0.15.0)
traces (>= 0.10.0)
Replace falcon server with puma Been wanting this for a while in theory, gonna actually do it now! The motivation is that I want to turn up the timeout for loading pets, because the Neopets endpoints are slower today with the NC UC release - but I can already predict that under our current architecture that will be a problem, because it'll block up our request queue! Falcon uses Ruby's relatively-new async system to *not* have requests block on upstream requests, and my understanding is that this behavior is plug-and-play. Let's see how it goes!
2024-01-23 21:47:51 -08:00
async-http-cache (0.4.3)
async-http (~> 0.56)
Move manifest backfill to `swf_assets:manifests` task Okay, I've simplified the migration to *just* add the column, and instead added a task to find assets without manifest URLs and backfill them. Performance is a lot better now, using the `async-http` library, which as I understand it supports both persistent connections when invoked like this, and maybe also HTTP/2 multiplexing?? (Though I'm not actually sure images.neopets.com does lol) I'm not sure about the number of concurrent tasks I picked here, 100 seems okay for an internet thing and for such small requests, but I worry that the CDN is gonna get annoyed or something. Well, we'll see! This task is very resumable if it turns out we get frozen out or something.
2023-11-10 16:52:50 -08:00
async-io (1.37.0)
async
async-pool (0.4.0)
async (>= 1.25)
Upgrade to Ruby 2.2.4, Rails 4.0.13 NOTE: This doesn't boot yet! There's something changed in the `devise` API that we'll need to fix! ``` /vagrant/config/initializers/devise.rb:46:in `block in <top (required)>': undefined method `encryptor=' for Devise:Module (NoMethodError) ``` But yeah, we navigated the gem upgrades, and also I ran `rake rails:update` and hand-processed the suggestions it had for our config files.
2023-07-21 19:39:32 -07:00
babel-source (5.8.35)
babel-transpiler (0.7.0)
babel-source (>= 4.0, < 6)
execjs (~> 2.0)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
base64 (0.1.1)
Upgrade to Ruby 2.2.4, Rails 4.0.13 NOTE: This doesn't boot yet! There's something changed in the `devise` API that we'll need to fix! ``` /vagrant/config/initializers/devise.rb:46:in `block in <top (required)>': undefined method `encryptor=' for Devise:Module (NoMethodError) ``` But yeah, we navigated the gem upgrades, and also I ran `rake rails:update` and hand-processed the suggestions it had for our config files.
2023-07-21 19:39:32 -07:00
bcrypt (3.1.19)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
bigdecimal (3.1.4)
Upgrade web-console Huh, error pages weren't actually working on this older version of web-console, but now they are! Solution found here: https://discuss.rubyonrails.org/t/question-dev-mode-500-errors-not-displayed-config-consider-all-requests-local-not-honored/78453/7
2023-08-02 16:20:50 -07:00
bindex (0.8.1)
Update all our gems as far as we can Got pretty far, there's a couple still held back by Rails 6+, but yeah doing great!
2023-08-02 17:16:24 -07:00
bootsnap (1.16.0)
Run `rails app:update` We accepted some changes as-is, but for development.rb and production.rb we read the diff and manually edited them!
2023-08-02 16:17:07 -07:00
msgpack (~> 1.2)
Replace falcon server with puma Been wanting this for a while in theory, gonna actually do it now! The motivation is that I want to turn up the timeout for loading pets, because the Neopets endpoints are slower today with the NC UC release - but I can already predict that under our current architecture that will be a problem, because it'll block up our request queue! Falcon uses Ruby's relatively-new async system to *not* have requests block on upstream requests, and my understanding is that this behavior is plug-and-play. Let's see how it goes!
2024-01-23 21:47:51 -08:00
build-environment (1.13.0)
Update gems to Rails 4.1 (crashes!) Lookin' good on this end, but the server isn't starting up yet, got some fixes to make!
2023-07-29 11:33:39 -07:00
builder (3.2.4)
Upgrade to Rails 4.2.11.3 and Ruby 2.4.10 Some tricks required here to get the dependencies to work out, but we got it!! Oh also, we move away from the rbenv in Ubuntu's package manager, because it doesn't support more recent Rubies like 2.4.10.
2023-08-02 15:18:36 -07:00
concurrent-ruby (1.2.2)
Upgrade to Ruby 2.2.4, Rails 4.0.13 NOTE: This doesn't boot yet! There's something changed in the `devise` API that we'll need to fix! ``` /vagrant/config/initializers/devise.rb:46:in `block in <top (required)>': undefined method `encryptor=' for Devise:Module (NoMethodError) ``` But yeah, we navigated the gem upgrades, and also I ran `rake rails:update` and hand-processed the suggestions it had for our config files.
2023-07-21 19:39:32 -07:00
connection_pool (2.2.5)
Move manifest backfill to `swf_assets:manifests` task Okay, I've simplified the migration to *just* add the column, and instead added a task to find assets without manifest URLs and backfill them. Performance is a lot better now, using the `async-http` library, which as I understand it supports both persistent connections when invoked like this, and maybe also HTTP/2 multiplexing?? (Though I'm not actually sure images.neopets.com does lol) I'm not sure about the number of concurrent tasks I picked here, 100 seems okay for an internet thing and for such small requests, but I worry that the CDN is gonna get annoyed or something. Well, we'll see! This task is very resumable if it turns out we get frozen out or something.
2023-11-10 16:52:50 -08:00
console (1.23.2)
fiber-annotation
fiber-local
Upgrade to Rails 4.2.11.3 and Ruby 2.4.10 Some tricks required here to get the dependencies to work out, but we got it!! Oh also, we move away from the rbenv in Ubuntu's package manager, because it doesn't support more recent Rubies like 2.4.10.
2023-08-02 15:18:36 -07:00
crass (1.0.6)
Fix gems we'd locked to old versions Now that we're on Ruby 2.6, the constraints on the latest versions of these dependencies are satisfied, so we can stop holding them back!
2023-08-02 17:09:43 -07:00
date (3.3.3)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
devise (4.9.3)
Upgrade to Ruby 2.2.4, Rails 4.0.13 NOTE: This doesn't boot yet! There's something changed in the `devise` API that we'll need to fix! ``` /vagrant/config/initializers/devise.rb:46:in `block in <top (required)>': undefined method `encryptor=' for Devise:Module (NoMethodError) ``` But yeah, we navigated the gem upgrades, and also I ran `rake rails:update` and hand-processed the suggestions it had for our config files.
2023-07-21 19:39:32 -07:00
bcrypt (~> 3.0)
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
orm_adapter (~> 0.1)
Upgrade to Rails 4.2.11.3 and Ruby 2.4.10 Some tricks required here to get the dependencies to work out, but we got it!! Oh also, we move away from the rbenv in Ubuntu's package manager, because it doesn't support more recent Rubies like 2.4.10.
2023-08-02 15:18:36 -07:00
railties (>= 4.1.0)
Upgrade to Ruby 2.2.4, Rails 4.0.13 NOTE: This doesn't boot yet! There's something changed in the `devise` API that we'll need to fix! ``` /vagrant/config/initializers/devise.rb:46:in `block in <top (required)>': undefined method `encryptor=' for Devise:Module (NoMethodError) ``` But yeah, we navigated the gem upgrades, and also I ran `rake rails:update` and hand-processed the suggestions it had for our config files.
2023-07-21 19:39:32 -07:00
responders
warden (~> 1.2.3)
Can log into OpenNeo ID accounts directly! A lot of rough edges here (e.g. no styles on the flash messages), but it's working and that's good!! I tested this by temporarily switching to the production database and logging in as matchu! Still missing a lot of big features too, like registration, password resets, settings page, etc.
2023-08-06 15:52:05 -07:00
devise-encryptable (0.2.0)
devise (>= 2.1.0)
Remove dotenv-deployment, upgrade dotenv-rails Idk exactly what's going on with dotenv-deployment, if it turns out it was critical to our deploy process then we'll change the deploy process! It's deprecated and conflicts with gem deps for `dotenv-rails`.
2023-08-02 13:41:37 -07:00
dotenv (2.8.1)
dotenv-rails (2.8.1)
dotenv (= 2.8.1)
railties (>= 3.2)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
drb (2.1.1)
ruby2_keywords
Upgrade to Rails 5.2.8.1 Some important little upgrades but mostly straightforward! Note that there's still a known issue where item searches crash, I was hoping that this was a bug in Rails 4.2 that would be fixed on upgading to 5, but nope, oh well! Also uhh I just got a bit silly and didn't actually mean to go all the way to 5.2 in one go, I had meant to start at 5.0… but tbh the 5.1 and 5.2 changes seem small, and this seems to be working, so. Yeah ok let's roll!
2023-08-02 16:05:02 -07:00
erubi (1.12.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
execjs (2.5.2)
Replace falcon server with puma Been wanting this for a while in theory, gonna actually do it now! The motivation is that I want to turn up the timeout for loading pets, because the Neopets endpoints are slower today with the NC UC release - but I can already predict that under our current architecture that will be a problem, because it'll block up our request queue! Falcon uses Ruby's relatively-new async system to *not* have requests block on upstream requests, and my understanding is that this behavior is plug-and-play. Let's see how it goes!
2024-01-23 21:47:51 -08:00
falcon (0.42.3)
async
async-container (~> 0.16.0)
async-http (~> 0.57)
async-http-cache (~> 0.4.0)
async-io (~> 1.22)
build-environment (~> 1.13)
bundler
localhost (~> 1.1)
openssl (~> 3.0)
process-metrics (~> 0.2.0)
protocol-rack (~> 0.1)
samovar (~> 2.1)
Upgrade to latest Sass and Sprockets This required a buncha fixes to how SASS scoping works! Needed to add a bunch of imports for stuff that previously would get read from the global scope by being imported *after* the constants and mixins etc. There's clearly a lot of refactor opportunity here, but I'm not gonna worry about it!!
2023-08-22 16:08:11 -07:00
ffi (1.15.5)
Move manifest backfill to `swf_assets:manifests` task Okay, I've simplified the migration to *just* add the column, and instead added a task to find assets without manifest URLs and backfill them. Performance is a lot better now, using the `async-http` library, which as I understand it supports both persistent connections when invoked like this, and maybe also HTTP/2 multiplexing?? (Though I'm not actually sure images.neopets.com does lol) I'm not sure about the number of concurrent tasks I picked here, 100 seems okay for an internet thing and for such small requests, but I worry that the CDN is gonna get annoyed or something. Well, we'll see! This task is very resumable if it turns out we get frozen out or something.
2023-11-10 16:52:50 -08:00
fiber-annotation (0.2.0)
fiber-local (1.0.0)
Security updates Resolves CVE-2023-40175 and CVE-2023-38037.
2023-10-23 19:08:56 -07:00
globalid (1.2.1)
activesupport (>= 6.1)
Upgrade haml I was hoping this would fix a character encoding bug, it didn't really? but it doesn't seem to hurt and is probably good to do
2023-07-22 12:58:15 -07:00
haml (6.1.1)
temple (>= 0.8.2)
thor
phew. rails 3.2.12, including some asset pipeline. still buggy.
2013-03-05 18:08:57 -08:00
tilt
Version the http_accept_languages gem idk why we were pulling from git before, probably to get a feature that wasn't pushed to rubygems yet? But now the latest rubygems version matches the latest repo commit (both back in 2017 lol), so let's do that for greater stability and clarity!
2023-08-02 13:24:56 -07:00
http_accept_language (2.1.1)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
httparty (0.21.0)
mini_mime (>= 1.0.0)
multi_xml (>= 0.5.2)
Upgrade to Rails 5.2.8.1 Some important little upgrades but mostly straightforward! Note that there's still a known issue where item searches crash, I was hoping that this was a bug in Rails 4.2 that would be fixed on upgading to 5, but nope, oh well! Also uhh I just got a bit silly and didn't actually mean to go all the way to 5.2 in one go, I had meant to start at 5.0… but tbh the 5.1 and 5.2 changes seem small, and this seems to be working, so. Yeah ok let's roll!
2023-08-02 16:05:02 -07:00
i18n (1.14.1)
Upgrade to Rails 3.2.22.5 I'm just giving the app a very quick scan on critical pages, it's possible I'm missing some issues on paths that are harder to test rn like openneo_id auth, but I'll check in on that later I think?
2023-07-21 18:33:04 -07:00
concurrent-ruby (~> 1.0)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
io-console (0.6.0)
Move manifest backfill to `swf_assets:manifests` task Okay, I've simplified the migration to *just* add the column, and instead added a task to find assets without manifest URLs and backfill them. Performance is a lot better now, using the `async-http` library, which as I understand it supports both persistent connections when invoked like this, and maybe also HTTP/2 multiplexing?? (Though I'm not actually sure images.neopets.com does lol) I'm not sure about the number of concurrent tasks I picked here, 100 seems okay for an internet thing and for such small requests, but I worry that the CDN is gonna get annoyed or something. Well, we'll see! This task is very resumable if it turns out we get frozen out or something.
2023-11-10 16:52:50 -08:00
io-event (1.3.3)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
irb (1.8.3)
rdoc
reline (>= 0.3.8)
jsbundling-rails (1.2.1)
Bundle wardrobe-2020 into the app We add jsbuilding-rails to get esbuild running in the app, and then we copy-paste the files we need from impress-2020 into here! I stopped at the point where it was building successfully, but it's not running correctly: it's not sure about `process.env` in `next`, and I think the right next step is to delete the NextJS deps altogether and use React Router instead.
2023-08-10 15:56:36 -07:00
railties (>= 6.0.0)
Update all our gems as far as we can Got pretty far, there's a couple still held back by Rails 6+, but yeah doing great!
2023-08-02 17:16:24 -07:00
launchy (2.5.2)
addressable (~> 2.8)
letter_opener (1.8.1)
launchy (>= 2.2, < 3)
Replace falcon server with puma Been wanting this for a while in theory, gonna actually do it now! The motivation is that I want to turn up the timeout for loading pets, because the Neopets endpoints are slower today with the NC UC release - but I can already predict that under our current architecture that will be a problem, because it'll block up our request queue! Falcon uses Ruby's relatively-new async system to *not* have requests block on upstream requests, and my understanding is that this behavior is plug-and-play. Let's see how it goes!
2024-01-23 21:47:51 -08:00
localhost (1.1.10)
Fix gems we'd locked to old versions Now that we're on Ruby 2.6, the constraints on the latest versions of these dependencies are satisfied, so we can stop holding them back!
2023-08-02 17:09:43 -07:00
loofah (2.21.3)
Upgrade to Rails 4.2.11.3 and Ruby 2.4.10 Some tricks required here to get the dependencies to work out, but we got it!! Oh also, we move away from the rbenv in Ubuntu's package manager, because it doesn't support more recent Rubies like 2.4.10.
2023-08-02 15:18:36 -07:00
crass (~> 1.0.2)
Fix gems we'd locked to old versions Now that we're on Ruby 2.6, the constraints on the latest versions of these dependencies are satisfied, so we can stop holding them back!
2023-08-02 17:09:43 -07:00
nokogiri (>= 1.12.0)
mail (2.8.1)
Upgrade to Ruby 2.2.4, Rails 4.0.13 NOTE: This doesn't boot yet! There's something changed in the `devise` API that we'll need to fix! ``` /vagrant/config/initializers/devise.rb:46:in `block in <top (required)>': undefined method `encryptor=' for Devise:Module (NoMethodError) ``` But yeah, we navigated the gem upgrades, and also I ran `rake rails:update` and hand-processed the suggestions it had for our config files.
2023-07-21 19:39:32 -07:00
mini_mime (>= 0.1.1)
Fix gems we'd locked to old versions Now that we're on Ruby 2.6, the constraints on the latest versions of these dependencies are satisfied, so we can stop holding them back!
2023-08-02 17:09:43 -07:00
net-imap
net-pop
net-smtp
Replace falcon server with puma Been wanting this for a while in theory, gonna actually do it now! The motivation is that I want to turn up the timeout for loading pets, because the Neopets endpoints are slower today with the NC UC release - but I can already predict that under our current architecture that will be a problem, because it'll block up our request queue! Falcon uses Ruby's relatively-new async system to *not* have requests block on upstream requests, and my understanding is that this behavior is plug-and-play. Let's see how it goes!
2024-01-23 21:47:51 -08:00
mapping (1.1.1)
Upgrade to Rails 5.2.8.1 Some important little upgrades but mostly straightforward! Note that there's still a known issue where item searches crash, I was hoping that this was a bug in Rails 4.2 that would be fixed on upgading to 5, but nope, oh well! Also uhh I just got a bit silly and didn't actually mean to go all the way to 5.2 in one go, I had meant to start at 5.0… but tbh the 5.1 and 5.2 changes seem small, and this seems to be working, so. Yeah ok let's roll!
2023-08-02 16:05:02 -07:00
marcel (1.0.2)
Add mini profiler to each page It shows up in development always, and if you're logged in as Me Specifically in production! I'm using this to poke at memory usage for pages that seem suspicious. I don't know why our app reliably grows so large in RAM, but my hunch is that maybe there are some pages that just use a truly large amount to begin with - and I've learned Ruby doesn't release memory back after it's GC'd, it just grows the process and keeps the free space to itself in its own heap! So I'm just eyeing pages that I know *can* have a lot going on, and seeing what I find!
2023-10-27 19:38:49 -07:00
memory_profiler (1.0.1)
Security updates Resolves CVE-2023-40175 and CVE-2023-38037.
2023-10-23 19:08:56 -07:00
mini_mime (1.1.5)
Fix gems we'd locked to old versions Now that we're on Ruby 2.6, the constraints on the latest versions of these dependencies are satisfied, so we can stop holding them back!
2023-08-02 17:09:43 -07:00
mini_portile2 (2.8.4)
minitest (5.19.0)
Update all our gems as far as we can Got pretty far, there's a couple still held back by Rails 6+, but yeah doing great!
2023-08-02 17:16:24 -07:00
msgpack (1.7.2)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
multi_xml (0.6.0)
mutex_m (0.1.2)
Upgrade to Rails 5.2.8.1 Some important little upgrades but mostly straightforward! Note that there's still a known issue where item searches crash, I was hoping that this was a bug in Rails 4.2 that would be fixed on upgading to 5, but nope, oh well! Also uhh I just got a bit silly and didn't actually mean to go all the way to 5.2 in one go, I had meant to start at 5.0… but tbh the 5.1 and 5.2 changes seem small, and this seems to be working, so. Yeah ok let's roll!
2023-08-02 16:05:02 -07:00
mysql2 (0.5.5)
Security updates Resolves CVE-2023-40175 and CVE-2023-38037.
2023-10-23 19:08:56 -07:00
net-imap (0.4.2)
Fix gems we'd locked to old versions Now that we're on Ruby 2.6, the constraints on the latest versions of these dependencies are satisfied, so we can stop holding them back!
2023-08-02 17:09:43 -07:00
date
net-protocol
net-pop (0.1.2)
net-protocol
net-protocol (0.2.1)
timeout
Security updates Resolves CVE-2023-40175 and CVE-2023-38037.
2023-10-23 19:08:56 -07:00
net-smtp (0.4.0)
Fix gems we'd locked to old versions Now that we're on Ruby 2.6, the constraints on the latest versions of these dependencies are satisfied, so we can stop holding them back!
2023-08-02 17:09:43 -07:00
net-protocol
Upgrade to Rails 5.2.8.1 Some important little upgrades but mostly straightforward! Note that there's still a known issue where item searches crash, I was hoping that this was a bug in Rails 4.2 that would be fixed on upgading to 5, but nope, oh well! Also uhh I just got a bit silly and didn't actually mean to go all the way to 5.2 in one go, I had meant to start at 5.0… but tbh the 5.1 and 5.2 changes seem small, and this seems to be working, so. Yeah ok let's roll!
2023-08-02 16:05:02 -07:00
nio4r (2.5.9)
Upgrade to Rails 7.0.6 Whew! Seems like a pretty clean one? Ran `rails app:upgrade` and stuff, and made some corrections to keyword arguments for `translate` calls. There might be more such problems elsewhere? But that's hard to search for, and we'll have to see.
2023-08-03 16:37:45 -07:00
nokogiri (1.15.3)
mini_portile2 (~> 2.8.2)
Fix gems we'd locked to old versions Now that we're on Ruby 2.6, the constraints on the latest versions of these dependencies are satisfied, so we can stop holding them back!
2023-08-02 17:09:43 -07:00
racc (~> 1.4)
Replace falcon server with puma Been wanting this for a while in theory, gonna actually do it now! The motivation is that I want to turn up the timeout for loading pets, because the Neopets endpoints are slower today with the NC UC release - but I can already predict that under our current architecture that will be a problem, because it'll block up our request queue! Falcon uses Ruby's relatively-new async system to *not* have requests block on upstream requests, and my understanding is that this behavior is plug-and-play. Let's see how it goes!
2024-01-23 21:47:51 -08:00
openssl (3.2.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
orm_adapter (0.5.0)
Update all our gems as far as we can Got pretty far, there's a couple still held back by Rails 6+, but yeah doing great!
2023-08-02 17:16:24 -07:00
parallel (1.23.0)
Replace falcon server with puma Been wanting this for a while in theory, gonna actually do it now! The motivation is that I want to turn up the timeout for loading pets, because the Neopets endpoints are slower today with the NC UC release - but I can already predict that under our current architecture that will be a problem, because it'll block up our request queue! Falcon uses Ruby's relatively-new async system to *not* have requests block on upstream requests, and my understanding is that this behavior is plug-and-play. Let's see how it goes!
2024-01-23 21:47:51 -08:00
process-metrics (0.2.1)
console (~> 1.8)
samovar (~> 2.1)
Move manifest backfill to `swf_assets:manifests` task Okay, I've simplified the migration to *just* add the column, and instead added a task to find assets without manifest URLs and backfill them. Performance is a lot better now, using the `async-http` library, which as I understand it supports both persistent connections when invoked like this, and maybe also HTTP/2 multiplexing?? (Though I'm not actually sure images.neopets.com does lol) I'm not sure about the number of concurrent tasks I picked here, 100 seems okay for an internet thing and for such small requests, but I worry that the CDN is gonna get annoyed or something. Well, we'll see! This task is very resumable if it turns out we get frozen out or something.
2023-11-10 16:52:50 -08:00
protocol-hpack (1.4.2)
protocol-http (0.25.0)
protocol-http1 (0.16.0)
protocol-http (~> 0.22)
protocol-http2 (0.15.1)
protocol-hpack (~> 1.4)
protocol-http (~> 0.18)
Replace falcon server with puma Been wanting this for a while in theory, gonna actually do it now! The motivation is that I want to turn up the timeout for loading pets, because the Neopets endpoints are slower today with the NC UC release - but I can already predict that under our current architecture that will be a problem, because it'll block up our request queue! Falcon uses Ruby's relatively-new async system to *not* have requests block on upstream requests, and my understanding is that this behavior is plug-and-play. Let's see how it goes!
2024-01-23 21:47:51 -08:00
protocol-rack (0.4.1)
protocol-http (~> 0.23)
rack (>= 1.0)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
psych (5.1.1.1)
stringio
Update all our gems as far as we can Got pretty far, there's a couple still held back by Rails 6+, but yeah doing great!
2023-08-02 17:16:24 -07:00
public_suffix (5.0.3)
Fix gems we'd locked to old versions Now that we're on Ruby 2.6, the constraints on the latest versions of these dependencies are satisfied, so we can stop holding them back!
2023-08-02 17:09:43 -07:00
racc (1.7.1)
Upgrade to Rails 5.2.8.1 Some important little upgrades but mostly straightforward! Note that there's still a known issue where item searches crash, I was hoping that this was a bug in Rails 4.2 that would be fixed on upgading to 5, but nope, oh well! Also uhh I just got a bit silly and didn't actually mean to go all the way to 5.2 in one go, I had meant to start at 5.0… but tbh the 5.1 and 5.2 changes seem small, and this seems to be working, so. Yeah ok let's roll!
2023-08-02 16:05:02 -07:00
rack (2.2.8)
Update all our gems as far as we can Got pretty far, there's a couple still held back by Rails 6+, but yeah doing great!
2023-08-02 17:16:24 -07:00
rack-attack (6.7.0)
rack (>= 1.0, < 4)
Add mini profiler to each page It shows up in development always, and if you're logged in as Me Specifically in production! I'm using this to poke at memory usage for pages that seem suspicious. I don't know why our app reliably grows so large in RAM, but my hunch is that maybe there are some pages that just use a truly large amount to begin with - and I've learned Ruby doesn't release memory back after it's GC'd, it just grows the process and keeps the free space to itself in its own heap! So I'm just eyeing pages that I know *can* have a lot going on, and seeing what I find!
2023-10-27 19:38:49 -07:00
rack-mini-profiler (3.1.1)
rack (>= 1.2.0)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
rack-session (1.0.1)
rack (< 3)
Upgrade to Rails 5.2.8.1 Some important little upgrades but mostly straightforward! Note that there's still a known issue where item searches crash, I was hoping that this was a bug in Rails 4.2 that would be fixed on upgading to 5, but nope, oh well! Also uhh I just got a bit silly and didn't actually mean to go all the way to 5.2 in one go, I had meant to start at 5.0… but tbh the 5.1 and 5.2 changes seem small, and this seems to be working, so. Yeah ok let's roll!
2023-08-02 16:05:02 -07:00
rack-test (2.1.0)
rack (>= 1.3)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
rackup (1.0.0)
rack (< 3)
webrick
rails (7.1.1)
actioncable (= 7.1.1)
actionmailbox (= 7.1.1)
actionmailer (= 7.1.1)
actionpack (= 7.1.1)
actiontext (= 7.1.1)
actionview (= 7.1.1)
activejob (= 7.1.1)
activemodel (= 7.1.1)
activerecord (= 7.1.1)
activestorage (= 7.1.1)
activesupport (= 7.1.1)
Upgrade to Rails 6.1.7.4 This one was pretty straightforward yaay! Main thing was the change from `render file` to `render template` in a couple places, oh and a thing with complex `order()` clauses.
2023-08-02 17:55:32 -07:00
bundler (>= 1.15.0)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
railties (= 7.1.1)
Upgrade to Rails 7.0.6 Whew! Seems like a pretty clean one? Ran `rails app:upgrade` and stuff, and made some corrections to keyword arguments for `translate` calls. There might be more such problems elsewhere? But that's hard to search for, and we'll have to see.
2023-08-03 16:37:45 -07:00
rails-dom-testing (2.2.0)
Upgrade to Rails 5.2.8.1 Some important little upgrades but mostly straightforward! Note that there's still a known issue where item searches crash, I was hoping that this was a bug in Rails 4.2 that would be fixed on upgading to 5, but nope, oh well! Also uhh I just got a bit silly and didn't actually mean to go all the way to 5.2 in one go, I had meant to start at 5.0… but tbh the 5.1 and 5.2 changes seem small, and this seems to be working, so. Yeah ok let's roll!
2023-08-02 16:05:02 -07:00
activesupport (>= 5.0.0)
minitest
nokogiri (>= 1.6)
Upgrade to Rails 7.0.6 Whew! Seems like a pretty clean one? Ran `rails app:upgrade` and stuff, and made some corrections to keyword arguments for `translate` calls. There might be more such problems elsewhere? But that's hard to search for, and we'll have to see.
2023-08-03 16:37:45 -07:00
rails-html-sanitizer (1.6.0)
loofah (~> 2.21)
nokogiri (~> 1.14)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
rails-i18n (7.0.8)
Upgrade to Rails 5.2.8.1 Some important little upgrades but mostly straightforward! Note that there's still a known issue where item searches crash, I was hoping that this was a bug in Rails 4.2 that would be fixed on upgading to 5, but nope, oh well! Also uhh I just got a bit silly and didn't actually mean to go all the way to 5.2 in one go, I had meant to start at 5.0… but tbh the 5.1 and 5.2 changes seem small, and this seems to be working, so. Yeah ok let's roll!
2023-08-02 16:05:02 -07:00
i18n (>= 0.7, < 2)
Upgrade to Rails 6.0.6.1 Another pretty easy one! We have the `rails app:update` changes in here too.
2023-08-02 17:27:11 -07:00
railties (>= 6.0.0, < 8)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
railties (7.1.1)
actionpack (= 7.1.1)
activesupport (= 7.1.1)
irb
rackup (>= 1.0.0)
Upgrade to Rails 6.1.7.4 This one was pretty straightforward yaay! Main thing was the change from `render file` to `render template` in a couple places, oh and a thing with complex `order()` clauses.
2023-08-02 17:55:32 -07:00
rake (>= 12.2)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
thor (~> 1.0, >= 1.2.2)
zeitwerk (~> 2.6)
Upgrade to Ruby 2.2.4, Rails 4.0.13 NOTE: This doesn't boot yet! There's something changed in the `devise` API that we'll need to fix! ``` /vagrant/config/initializers/devise.rb:46:in `block in <top (required)>': undefined method `encryptor=' for Devise:Module (NoMethodError) ``` But yeah, we navigated the gem upgrades, and also I ran `rake rails:update` and hand-processed the suggestions it had for our config files.
2023-07-21 19:39:32 -07:00
rake (13.0.6)
Update all our gems as far as we can Got pretty far, there's a couple still held back by Rails 6+, but yeah doing great!
2023-08-02 17:16:24 -07:00
rdiscount (2.2.7.1)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
rdoc (6.5.0)
psych (>= 4.0.0)
Upgrade to Ruby 2.2.4, Rails 4.0.13 NOTE: This doesn't boot yet! There's something changed in the `devise` API that we'll need to fix! ``` /vagrant/config/initializers/devise.rb:46:in `block in <top (required)>': undefined method `encryptor=' for Devise:Module (NoMethodError) ``` But yeah, we navigated the gem upgrades, and also I ran `rake rails:update` and hand-processed the suggestions it had for our config files.
2023-07-21 19:39:32 -07:00
react-rails (2.7.1)
babel-transpiler (>= 0.7.0)
connection_pool
basic modeling buttons no behavior yet, nor are they filtered
2014-01-03 13:11:02 -08:00
execjs
Upgrade to Ruby 2.2.4, Rails 4.0.13 NOTE: This doesn't boot yet! There's something changed in the `devise` API that we'll need to fix! ``` /vagrant/config/initializers/devise.rb:46:in `block in <top (required)>': undefined method `encryptor=' for Devise:Module (NoMethodError) ``` But yeah, we navigated the gem upgrades, and also I ran `rake rails:update` and hand-processed the suggestions it had for our config files.
2023-07-21 19:39:32 -07:00
railties (>= 3.2)
tilt
Upgrade to Rails 5.2.8.1 Some important little upgrades but mostly straightforward! Note that there's still a known issue where item searches crash, I was hoping that this was a bug in Rails 4.2 that would be fixed on upgading to 5, but nope, oh well! Also uhh I just got a bit silly and didn't actually mean to go all the way to 5.2 in one go, I had meant to start at 5.0… but tbh the 5.1 and 5.2 changes seem small, and this seems to be working, so. Yeah ok let's roll!
2023-08-02 16:05:02 -07:00
record_tag_helper (1.0.1)
actionview (>= 5)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
reline (0.3.9)
io-console (~> 0.5)
responders (3.1.1)
Upgrade to Rails 6.0.6.1 Another pretty easy one! We have the `rails app:update` changes in here too.
2023-08-02 17:27:11 -07:00
actionpack (>= 5.2)
railties (>= 5.2)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
ruby2_keywords (0.0.5)
Replace falcon server with puma Been wanting this for a while in theory, gonna actually do it now! The motivation is that I want to turn up the timeout for loading pets, because the Neopets endpoints are slower today with the NC UC release - but I can already predict that under our current architecture that will be a problem, because it'll block up our request queue! Falcon uses Ruby's relatively-new async system to *not* have requests block on upstream requests, and my understanding is that this behavior is plug-and-play. Let's see how it goes!
2024-01-23 21:47:51 -08:00
samovar (2.2.0)
console (~> 1.0)
mapping (~> 1.0)
Update all our gems as far as we can Got pretty far, there's a couple still held back by Rails 6+, but yeah doing great!
2023-08-02 17:16:24 -07:00
sanitize (6.0.2)
crass (~> 1.0.2)
nokogiri (>= 1.12.0)
Upgrade to latest Sass and Sprockets This required a buncha fixes to how SASS scoping works! Needed to add a bunch of imports for stuff that previously would get read from the global scope by being imported *after* the constants and mixins etc. There's clearly a lot of refactor opportunity here, but I'm not gonna worry about it!!
2023-08-22 16:08:11 -07:00
sass-rails (6.0.0)
sassc-rails (~> 2.1, >= 2.1.1)
sassc (2.4.0)
ffi (~> 1.9)
sassc-rails (2.1.2)
railties (>= 4.0.0)
sassc (>= 2.0)
sprockets (> 3.0)
sprockets-rails
tilt
Add Sentry to Rails Now we're tracking both JS and Rails errors, phew!
2023-11-06 12:37:40 -08:00
sentry-rails (5.12.0)
railties (>= 5.0)
sentry-ruby (~> 5.12.0)
sentry-ruby (5.12.0)
concurrent-ruby (~> 1.0, >= 1.0.2)
Upgrade to latest Sass and Sprockets This required a buncha fixes to how SASS scoping works! Needed to add a bunch of imports for stuff that previously would get read from the global scope by being imported *after* the constants and mixins etc. There's clearly a lot of refactor opportunity here, but I'm not gonna worry about it!!
2023-08-22 16:08:11 -07:00
sprockets (4.2.0)
Update gems to Rails 4.1 (crashes!) Lookin' good on this end, but the server isn't starting up yet, got some fixes to make!
2023-07-29 11:33:39 -07:00
concurrent-ruby (~> 1.0)
Upgrade to latest Sass and Sprockets This required a buncha fixes to how SASS scoping works! Needed to add a bunch of imports for stuff that previously would get read from the global scope by being imported *after* the constants and mixins etc. There's clearly a lot of refactor opportunity here, but I'm not gonna worry about it!!
2023-08-22 16:08:11 -07:00
rack (>= 2.2.4, < 4)
Upgrade to Rails 6.0.6.1 Another pretty easy one! We have the `rails app:update` changes in here too.
2023-08-02 17:27:11 -07:00
sprockets-rails (3.4.2)
actionpack (>= 5.2)
activesupport (>= 5.2)
Upgrade to Rails 4.2.11.3 and Ruby 2.4.10 Some tricks required here to get the dependencies to work out, but we got it!! Oh also, we move away from the rbenv in Ubuntu's package manager, because it doesn't support more recent Rubies like 2.4.10.
2023-08-02 15:18:36 -07:00
sprockets (>= 3.0.0)
Save last trade activity time onto User In impress-2020, we do a big slow query to figure out which users have been active in trades recently. Now, we cache that timestamp on the User model. This won't have any immediate effect; it's to clear the way for Classic DTI to receive the better trade ratios feature people like from 2020. I also added some unit testing infra because I finally wanted it! for all the ways you can trigger this timestamp lol Note too that this is a bit of an unusually complex migration, but my hope is that the batching and query structure and such helps it run surprisingly fast! 🤞
2024-01-19 00:00:46 -08:00
sqlite3 (1.7.0)
mini_portile2 (~> 2.8.0)
Add mini profiler to each page It shows up in development always, and if you're logged in as Me Specifically in production! I'm using this to poke at memory usage for pages that seem suspicious. I don't know why our app reliably grows so large in RAM, but my hunch is that maybe there are some pages that just use a truly large amount to begin with - and I've learned Ruby doesn't release memory back after it's GC'd, it just grows the process and keeps the free space to itself in its own heap! So I'm just eyeing pages that I know *can* have a lot going on, and seeing what I find!
2023-10-27 19:38:49 -07:00
stackprof (0.2.25)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
stringio (3.0.8)
Upgrade haml I was hoping this would fix a character encoding bug, it didn't really? but it doesn't seem to hurt and is probably good to do
2023-07-22 12:58:15 -07:00
temple (0.8.2)
Precompile assets when deploying new version I did some refactoring while here too, of pulling the deploy scripts out of `package.json` and into `bin`, to be a bit more canonically Rails-y. (idk how canonical the colon thing is but, probably fine??)
2023-08-19 18:51:46 -07:00
terser (1.1.17)
execjs (>= 0.3.0, < 3)
Upgrade to Ruby 2.2.4, Rails 4.0.13 NOTE: This doesn't boot yet! There's something changed in the `devise` API that we'll need to fix! ``` /vagrant/config/initializers/devise.rb:46:in `block in <top (required)>': undefined method `encryptor=' for Devise:Module (NoMethodError) ``` But yeah, we navigated the gem upgrades, and also I ran `rake rails:update` and hand-processed the suggestions it had for our config files.
2023-07-21 19:39:32 -07:00
thor (1.2.2)
Move manifest backfill to `swf_assets:manifests` task Okay, I've simplified the migration to *just* add the column, and instead added a task to find assets without manifest URLs and backfill them. Performance is a lot better now, using the `async-http` library, which as I understand it supports both persistent connections when invoked like this, and maybe also HTTP/2 multiplexing?? (Though I'm not actually sure images.neopets.com does lol) I'm not sure about the number of concurrent tasks I picked here, 100 seems okay for an internet thing and for such small requests, but I worry that the CDN is gonna get annoyed or something. Well, we'll see! This task is very resumable if it turns out we get frozen out or something.
2023-11-10 16:52:50 -08:00
thread-local (1.1.0)
Update gems to Rails 4.1 (crashes!) Lookin' good on this end, but the server isn't starting up yet, got some fixes to make!
2023-07-29 11:33:39 -07:00
tilt (2.2.0)
Fix gems we'd locked to old versions Now that we're on Ruby 2.6, the constraints on the latest versions of these dependencies are satisfied, so we can stop holding them back!
2023-08-02 17:09:43 -07:00
timeout (0.4.0)
Move manifest backfill to `swf_assets:manifests` task Okay, I've simplified the migration to *just* add the column, and instead added a task to find assets without manifest URLs and backfill them. Performance is a lot better now, using the `async-http` library, which as I understand it supports both persistent connections when invoked like this, and maybe also HTTP/2 multiplexing?? (Though I'm not actually sure images.neopets.com does lol) I'm not sure about the number of concurrent tasks I picked here, 100 seems okay for an internet thing and for such small requests, but I worry that the CDN is gonna get annoyed or something. Well, we'll see! This task is very resumable if it turns out we get frozen out or something.
2023-11-10 16:52:50 -08:00
timers (4.3.5)
traces (0.11.1)
Upgrade to Rails 6.1.7.4 This one was pretty straightforward yaay! Main thing was the change from `render file` to `render template` in a couple places, oh and a thing with complex `order()` clauses.
2023-08-02 17:55:32 -07:00
tzinfo (2.0.6)
concurrent-ruby (~> 1.0)
Upgrade to Ruby 2.2.4, Rails 4.0.13 NOTE: This doesn't boot yet! There's something changed in the `devise` API that we'll need to fix! ``` /vagrant/config/initializers/devise.rb:46:in `block in <top (required)>': undefined method `encryptor=' for Devise:Module (NoMethodError) ``` But yeah, we navigated the gem upgrades, and also I ran `rake rails:update` and hand-processed the suggestions it had for our config files.
2023-07-21 19:39:32 -07:00
warden (1.2.7)
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)
Security updates Resolves CVE-2023-40175 and CVE-2023-38037.
2023-10-23 19:08:56 -07:00
web-console (4.2.1)
Add web console support for Vagrant users
2023-08-02 17:36:32 -07:00
actionview (>= 6.0.0)
activemodel (>= 6.0.0)
Upgrade web-console Huh, error pages weren't actually working on this older version of web-console, but now they are! Solution found here: https://discuss.rubyonrails.org/t/question-dev-mode-500-errors-not-displayed-config-consider-all-requests-local-not-honored/78453/7
2023-08-02 16:20:50 -07:00
bindex (>= 0.4.0)
Add web console support for Vagrant users
2023-08-02 17:36:32 -07:00
railties (>= 6.0.0)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
webrick (1.8.1)
Upgrade to Rails 5.2.8.1 Some important little upgrades but mostly straightforward! Note that there's still a known issue where item searches crash, I was hoping that this was a bug in Rails 4.2 that would be fixed on upgading to 5, but nope, oh well! Also uhh I just got a bit silly and didn't actually mean to go all the way to 5.2 in one go, I had meant to start at 5.0… but tbh the 5.1 and 5.2 changes seem small, and this seems to be working, so. Yeah ok let's roll!
2023-08-02 16:05:02 -07:00
websocket-driver (0.7.6)
websocket-extensions (>= 0.1.0)
websocket-extensions (0.1.5)
will_paginate (4.0.0)
Upgrade to Rails 6.0.6.1 Another pretty easy one! We have the `rails app:update` changes in here too.
2023-08-02 17:27:11 -07:00
zeitwerk (2.6.11)
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!
Add Owls values to the item page Eyy it's time!! Long-requested, finally here lol
2023-11-03 16:20:02 -07:00
addressable (~> 2.8)
Move manifest backfill to `swf_assets:manifests` task Okay, I've simplified the migration to *just* add the column, and instead added a task to find assets without manifest URLs and backfill them. Performance is a lot better now, using the `async-http` library, which as I understand it supports both persistent connections when invoked like this, and maybe also HTTP/2 multiplexing?? (Though I'm not actually sure images.neopets.com does lol) I'm not sure about the number of concurrent tasks I picked here, 100 seems okay for an internet thing and for such small requests, but I worry that the CDN is gonna get annoyed or something. Well, we'll see! This task is very resumable if it turns out we get frozen out or something.
2023-11-10 16:52:50 -08:00
async (~> 2.6)
async-http (~> 0.61.0)
Update all our gems as far as we can Got pretty far, there's a couple still held back by Rails 6+, but yeah doing great!
2023-08-02 17:16:24 -07:00
bootsnap (~> 1.16)
Upgrade to Rails 4.2.11.3 and Ruby 2.4.10 Some tricks required here to get the dependencies to work out, but we got it!! Oh also, we move away from the rbenv in Ubuntu's package manager, because it doesn't support more recent Rubies like 2.4.10.
2023-08-02 15:18:36 -07:00
devise (~> 4.9, >= 4.9.2)
Can log into OpenNeo ID accounts directly! A lot of rough edges here (e.g. no styles on the flash messages), but it's working and that's good!! I tested this by temporarily switching to the production database and logging in as matchu! Still missing a lot of big features too, like registration, password resets, settings page, etc.
2023-08-06 15:52:05 -07:00
devise-encryptable (~> 0.2.0)
Remove dotenv-deployment, upgrade dotenv-rails Idk exactly what's going on with dotenv-deployment, if it turns out it was critical to our deploy process then we'll change the deploy process! It's deprecated and conflicts with gem deps for `dotenv-rails`.
2023-08-02 13:41:37 -07:00
dotenv-rails (~> 2.8, >= 2.8.1)
Replace falcon server with puma Been wanting this for a while in theory, gonna actually do it now! The motivation is that I want to turn up the timeout for loading pets, because the Neopets endpoints are slower today with the NC UC release - but I can already predict that under our current architecture that will be a problem, because it'll block up our request queue! Falcon uses Ruby's relatively-new async system to *not* have requests block on upstream requests, and my understanding is that this behavior is plug-and-play. Let's see how it goes!
2024-01-23 21:47:51 -08:00
falcon (~> 0.42.3)
Upgrade haml I was hoping this would fix a character encoding bug, it didn't really? but it doesn't seem to hurt and is probably good to do
2023-07-22 12:58:15 -07:00
haml (~> 6.1, >= 6.1.1)
Version the http_accept_languages gem idk why we were pulling from git before, probably to get a feature that wasn't pushed to rubygems yet? But now the latest rubygems version matches the latest repo commit (both back in 2017 lol), so let's do that for greater stability and clarity!
2023-08-02 13:24:56 -07:00
http_accept_language (~> 2.1, >= 2.1.1)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
httparty (~> 0.21.0)
Bundle wardrobe-2020 into the app We add jsbuilding-rails to get esbuild running in the app, and then we copy-paste the files we need from impress-2020 into here! I stopped at the point where it was building successfully, but it's not running correctly: it's not sure about `process.env` in `next`, and I think the right next step is to delete the NextJS deps altogether and use React Router instead.
2023-08-10 15:56:36 -07:00
jsbundling-rails (~> 1.1)
Update all our gems as far as we can Got pretty far, there's a couple still held back by Rails 6+, but yeah doing great!
2023-08-02 17:16:24 -07:00
letter_opener (~> 1.8, >= 1.8.1)
Add mini profiler to each page It shows up in development always, and if you're logged in as Me Specifically in production! I'm using this to poke at memory usage for pages that seem suspicious. I don't know why our app reliably grows so large in RAM, but my hunch is that maybe there are some pages that just use a truly large amount to begin with - and I've learned Ruby doesn't release memory back after it's GC'd, it just grows the process and keeps the free space to itself in its own heap! So I'm just eyeing pages that I know *can* have a lot going on, and seeing what I find!
2023-10-27 19:38:49 -07:00
memory_profiler (~> 1.0)
Upgrade to Rails 5.2.8.1 Some important little upgrades but mostly straightforward! Note that there's still a known issue where item searches crash, I was hoping that this was a bug in Rails 4.2 that would be fixed on upgading to 5, but nope, oh well! Also uhh I just got a bit silly and didn't actually mean to go all the way to 5.2 in one go, I had meant to start at 5.0… but tbh the 5.1 and 5.2 changes seem small, and this seems to be working, so. Yeah ok let's roll!
2023-08-02 16:05:02 -07:00
mysql2 (~> 0.5.5)
Upgrade to webrick 1.8 Literally don't know why this wasn't 1.8 when I first installed it? Whatever!
2023-08-03 16:43:37 -07:00
nokogiri (~> 1.15, >= 1.15.3)
Update all our gems as far as we can Got pretty far, there's a couple still held back by Rails 6+, but yeah doing great!
2023-08-02 17:16:24 -07:00
parallel (~> 1.23)
rack-attack (~> 6.7)
Add mini profiler to each page It shows up in development always, and if you're logged in as Me Specifically in production! I'm using this to poke at memory usage for pages that seem suspicious. I don't know why our app reliably grows so large in RAM, but my hunch is that maybe there are some pages that just use a truly large amount to begin with - and I've learned Ruby doesn't release memory back after it's GC'd, it just grows the process and keeps the free space to itself in its own heap! So I'm just eyeing pages that I know *can* have a lot going on, and seeing what I find!
2023-10-27 19:38:49 -07:00
rack-mini-profiler (~> 3.1)
Upgrade to Rails 7.1.1 The usual stuff! Installed the new gem and its new deps, ran `bin/rails app:update` and did my best to manually merge the dev/prod config files with the new canonical defaults, deleted some migrations I don't think are relevant to us, and yeah! Also, Rails 7.1 seems to need `libyaml-dev` installed, so I added that to the `deploy/setup.yml` playbook! One thing to note is that, while I was here, I turned on some settings relating to our use of SSL that technically weren't on before. This should be fine and helpful? But if stuff breaks, well, check those!
2023-10-25 15:05:31 -07:00
rails (~> 7.1, >= 7.1.1)
Upgrade to Rails 6.0.6.1 Another pretty easy one! We have the `rails app:update` changes in here too.
2023-08-02 17:27:11 -07:00
rails-i18n (~> 7.0, >= 7.0.7)
Update all our gems as far as we can Got pretty far, there's a couple still held back by Rails 6+, but yeah doing great!
2023-08-02 17:16:24 -07:00
rdiscount (~> 2.2, >= 2.2.7.1)
Upgrade to Ruby 2.2.4, Rails 4.0.13 NOTE: This doesn't boot yet! There's something changed in the `devise` API that we'll need to fix! ``` /vagrant/config/initializers/devise.rb:46:in `block in <top (required)>': undefined method `encryptor=' for Devise:Module (NoMethodError) ``` But yeah, we navigated the gem upgrades, and also I ran `rake rails:update` and hand-processed the suggestions it had for our config files.
2023-07-21 19:39:32 -07:00
react-rails (~> 2.7, >= 2.7.1)
Update all our gems as far as we can Got pretty far, there's a couple still held back by Rails 6+, but yeah doing great!
2023-08-02 17:16:24 -07:00
record_tag_helper (~> 1.0, >= 1.0.1)
sanitize (~> 6.0, >= 6.0.2)
Upgrade to latest Sass and Sprockets This required a buncha fixes to how SASS scoping works! Needed to add a bunch of imports for stuff that previously would get read from the global scope by being imported *after* the constants and mixins etc. There's clearly a lot of refactor opportunity here, but I'm not gonna worry about it!!
2023-08-22 16:08:11 -07:00
sass-rails (~> 6.0)
Add Sentry to Rails Now we're tracking both JS and Rails errors, phew!
2023-11-06 12:37:40 -08:00
sentry-rails (~> 5.12)
sentry-ruby (~> 5.12)
Upgrade to latest Sass and Sprockets This required a buncha fixes to how SASS scoping works! Needed to add a bunch of imports for stuff that previously would get read from the global scope by being imported *after* the constants and mixins etc. There's clearly a lot of refactor opportunity here, but I'm not gonna worry about it!!
2023-08-22 16:08:11 -07:00
sprockets (~> 4.2)
Save last trade activity time onto User In impress-2020, we do a big slow query to figure out which users have been active in trades recently. Now, we cache that timestamp on the User model. This won't have any immediate effect; it's to clear the way for Classic DTI to receive the better trade ratios feature people like from 2020. I also added some unit testing infra because I finally wanted it! for all the ways you can trigger this timestamp lol Note too that this is a bit of an unusually complex migration, but my hope is that the batching and query structure and such helps it run surprisingly fast! 🤞
2024-01-19 00:00:46 -08:00
sqlite3 (~> 1.7)
Add mini profiler to each page It shows up in development always, and if you're logged in as Me Specifically in production! I'm using this to poke at memory usage for pages that seem suspicious. I don't know why our app reliably grows so large in RAM, but my hunch is that maybe there are some pages that just use a truly large amount to begin with - and I've learned Ruby doesn't release memory back after it's GC'd, it just grows the process and keeps the free space to itself in its own heap! So I'm just eyeing pages that I know *can* have a lot going on, and seeing what I find!
2023-10-27 19:38:49 -07:00
stackprof (~> 0.2.25)
Precompile assets when deploying new version I did some refactoring while here too, of pulling the deploy scripts out of `package.json` and into `bin`, to be a bit more canonically Rails-y. (idk how canonical the colon thing is but, probably fine??)
2023-08-19 18:51:46 -07:00
terser (~> 1.1, >= 1.1.17)
Move manifest backfill to `swf_assets:manifests` task Okay, I've simplified the migration to *just* add the column, and instead added a task to find assets without manifest URLs and backfill them. Performance is a lot better now, using the `async-http` library, which as I understand it supports both persistent connections when invoked like this, and maybe also HTTP/2 multiplexing?? (Though I'm not actually sure images.neopets.com does lol) I'm not sure about the number of concurrent tasks I picked here, 100 seems okay for an internet thing and for such small requests, but I worry that the CDN is gonna get annoyed or something. Well, we'll see! This task is very resumable if it turns out we get frozen out or something.
2023-11-10 16:52:50 -08:00
thread-local (~> 1.1)
Add web console support for Vagrant users
2023-08-02 17:36:32 -07:00
web-console (~> 4.2)
Upgrade to Rails 5.2.8.1 Some important little upgrades but mostly straightforward! Note that there's still a known issue where item searches crash, I was hoping that this was a bug in Rails 4.2 that would be fixed on upgading to 5, but nope, oh well! Also uhh I just got a bit silly and didn't actually mean to go all the way to 5.2 in one go, I had meant to start at 5.0… but tbh the 5.1 and 5.2 changes seem small, and this seems to be working, so. Yeah ok let's roll!
2023-08-02 16:05:02 -07:00
will_paginate (~> 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
Upgrade to Ruby 2.2.4, Rails 4.0.13 NOTE: This doesn't boot yet! There's something changed in the `devise` API that we'll need to fix! ``` /vagrant/config/initializers/devise.rb:46:in `block in <top (required)>': undefined method `encryptor=' for Devise:Module (NoMethodError) ``` But yeah, we navigated the gem upgrades, and also I ran `rake rails:update` and hand-processed the suggestions it had for our config files.
2023-07-21 19:39:32 -07:00
RUBY VERSION
Upgrade to Ruby 3.1.4 Easy peasy!
2023-08-04 16:38:42 -07:00
ruby 3.1.4p223
Upgrade to Ruby 2.2.4, Rails 4.0.13 NOTE: This doesn't boot yet! There's something changed in the `devise` API that we'll need to fix! ``` /vagrant/config/initializers/devise.rb:46:in `block in <top (required)>': undefined method `encryptor=' for Devise:Module (NoMethodError) ``` But yeah, we navigated the gem upgrades, and also I ran `rake rails:update` and hand-processed the suggestions it had for our config files.
2023-07-21 19:39:32 -07:00
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
Bundle wardrobe-2020 into the app We add jsbuilding-rails to get esbuild running in the app, and then we copy-paste the files we need from impress-2020 into here! I stopped at the point where it was building successfully, but it's not running correctly: it's not sure about `process.env` in `next`, and I think the right next step is to delete the NextJS deps altogether and use React Router instead.
2023-08-10 15:56:36 -07:00
2.3.26
Copy permalink