Dress to Impress, a big fancy Neopets customization tool!
Matchu
307f559226
Uhhh I think I must have made a mistake here where like… I must have left this in the service file for a while then accidentally deleted it from the Ansible playbook but not the live server? I had tested with this, then tested again without it and thought it wasn't necessary, but it turns out to have been necessary I guess? Ok! This instructs Rails's ExecJS library to not bother looking for Node or something similar, because the app doesn't actually need to run any JS, even though the `react-rails` library (?) seems to be pretty eager about the possibility that we'll need to server-side-render stuff. (We should consider whether we want to though tbh? But… idk that would be a pretty different arch than what we've done with `jsbundling-rails` so like. idk whatever) |
||
|---|---|---|
| app | ||
| autotest | ||
| bin | ||
| config | ||
| db | ||
| deploy | ||
| doc | ||
| lib | ||
| public | ||
| script | ||
| spec | ||
| test | ||
| tmp | ||
| vendor | ||
| .gitignore | ||
| .ruby-version | ||
| Capfile | ||
| config.ru | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE.md | ||
| package.json | ||
| Procfile.dev | ||
| Rakefile | ||
| README | ||
| Vagrantfile | ||
| 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.