forked from OpenNeo/impress
Dress to Impress, a big fancy Neopets customization tool!
Matchu
b885ff6ac0
Okay so… I'm worried about this because of Rails whole single-threaded situation, which doesn't really let it handle blocking on external network requests very well. Ultimately I think we're gonna have to do a clever thing but idk quite what? I should look into whether like, puma + the new async stuff can enable Rails to be more tolerable about this, and handle a few requests at once, instead of having to have the Neopia server doing it. (Right now, the Neopia server isn't really doing its job quite right, because it depends on the Rails app being *local* to send stuff to it.) But for now, let's just extend the timeout, cuz it's basically always getting hit in production—because there's currently no other way to do modeling, oops lol |
||
---|---|---|
.vscode | ||
app | ||
autotest | ||
bin | ||
config | ||
db | ||
deploy | ||
doc | ||
lib | ||
public | ||
script | ||
spec | ||
test | ||
tmp | ||
vendor | ||
.gitignore | ||
.ruby-version | ||
config.ru | ||
Gemfile | ||
Gemfile.lock | ||
LICENSE.md | ||
package.json | ||
Procfile.dev | ||
Rakefile | ||
README | ||
yarn.lock |
An extension of Dress to Impress (PHP) that runs on Ruby on Rails. I wanted to use Rails initially for Impress, but hoped that using PHP would allow me to attract more developers. Looks like that wasn't the case, so I just went with what I loved and made the items database in Rails. Future Impress sections will likely find themselves in this project, rather than the PHP project.