The 2020 Next.js rewrite, now being merged into impress!
Find a file
Matchu bd8ccf19d7 Remove monit from our deployment
Okay well, we added monit to solve a problem that I coincidentally solved within an hour of getting monit working lol!

This also enables us to remove the pm2 pid file, which we were only using to allow monit to track the pm2 app.
2021-11-03 16:48:38 -07:00
.github/workflows Fix GitHub Action for Sentry, attempt 6 2021-01-16 11:27:26 -08:00
.husky Add a pre-commit lint hook 2021-05-04 18:50:47 -07:00
.vscode update chakra imports 2020-12-25 09:08:33 -08:00
api Fix /api/outfitImage for Vercel 2021-11-02 01:40:20 -07:00
cypress Warn user of unsaved outfit changes 2021-05-04 16:31:48 -07:00
deploy Remove monit from our deployment 2021-11-03 16:48:38 -07:00
pages Fix /api/outfitImage for Vercel 2021-11-02 01:40:20 -07:00
public [WIP] Run cra-to-next codemod to be on Nextjs 2021-11-01 21:49:23 -07:00
scripts Use the first Auth0 connection instead of prompt 2021-10-02 01:01:29 -07:00
src [WIP] Add lint exceptions for <img> tags 2021-11-02 00:55:21 -07:00
.eslintrc.json [WIP] Fix eslint for Next.js 2021-11-01 22:07:46 -07:00
.gitignore [WIP] Run cra-to-next codemod to be on Nextjs 2021-11-01 21:49:23 -07:00
cypress.json Basic outfit state Cypress tests 2021-04-16 04:27:19 -07:00
LICENSE.md Add LICENSE.md 2021-01-21 05:55:57 -08:00
lint-staged.config.js [WIP] Fix eslint for Next.js 2021-11-01 22:07:46 -07:00
next-env.d.ts [WIP] Run cra-to-next codemod to be on Nextjs 2021-11-01 21:49:23 -07:00
next.config.js Fix /api/outfitImage for Vercel 2021-11-02 01:40:20 -07:00
package.json Fix pm2 monitoring 2021-11-03 16:46:35 -07:00
README.md update README to mention Rails app is gone 2020-09-04 04:09:01 -07:00
tsconfig.json [WIP] Run cra-to-next codemod to be on Nextjs 2021-11-01 21:49:23 -07:00
vercel.json Fix /api/outfitImage for Vercel 2021-11-02 01:40:20 -07:00
yarn.lock Install Sharp for production 2021-11-02 01:00:52 -07:00

Dress to Impress beach logo

Dress to Impress 2020

This is a rewrite of the Neopets customization app, Dress to Impress!

It's a React app, built with create-react-app, running on Vercel, JAMstack-style.

The motivating goals of the rewrite are:

  • Mobile friendly, to match Neopets's move to mobile.
  • Simple modern tech, to be more maintainable over time and decrease hosting costs.

If you want to contribute, please reach out to Matchu! This repository is almost shareable, but the main limitation is that we currently run even our development server against the production database, and those credentials are private. But we can change that if there's interest!

Architecture sketch

First, there's the core app, in this repository.

  • React app: Runs on Vercel's CDN. Code in src/app.
  • API functions: Run on Vercel's Serverless Functions. Code in api and src/server.

Then, there's our various data storage components.

  • MySQL database: Runs on our Linode VPS, colocated with the old app.
  • Amazon S3: Stores PNGs of pet/item appearance layers, converted from the Neopets SWFs. (Once Neopets releases HTML5-compatible assets for all their items, we can hopefully remove this!)

Finally, there's our third-party integrations.

  • Auth0: For authentication. Data imported from our old OpenNeo ID auth database.
  • Honeycomb: For observability & performance insights on the backend.
  • Discord: For logging Support users' actions to a private Discord server.
  • Neopets: We load pet data from them! And plenty of assets!

Notable old components not currently included in Impress 2020:

  • Elasticsearch: Used for lightning-fast item search queries. So far, we're finding the MySQL queries to be fast enough in practice. Might consider using some kind of fulltext query engine if that doesn't scale with more users!
  • Resque: Used to schedule background tasks for modeling and outfit thumbnails.
  • Outfit thumbnail generation: Used for outfit thumbnails in the app. I'm wondering if there's a way to get away with not doing this, like just rendering the layers... but I suppose if we want a good social share experience, then we'll probably want this. Maybe we can generate them on the fly as API requests, instead of adding a data storage component?
  • Memcache: Used to cache common HTML and JSON snippets. Not yet needing anything similar in Impress 2020!
  • The entire old Rails app! No references to it in here, aside from some temporary URL links to features that aren't implemented here yet.