Dress to Impress, a big fancy Neopets customization tool!
Emi Matchu
ffcfce2eb8
I'm starting to work with the OpenID Connect stuff in NeoPass, and the library I'm using for discovery doesn't seem to want to do it over a plain `http://` connection. (I dug into the source files, and it just actually is hardcoded to only work with HTTPS, as far as I can tell?) So, I've added logic to `neopass-server` to try to make an HTTPS certificate with the `mkcert` utility (if installed), which is a tool that installs a root certificate authority on your local machine, then helps you create certificates via that authority that will work only on your local machine. I think I'll also be able to remove the "main" server in front of the backing server, because the library I'm using now will be able to "discover" the auth and token endpoints, so it won't matter that our local one uses different URLs than live NeoPass does? We'll find out! I also remove `neopass-server` from the `Procfile`, because I think it's a bit rude to have it auto-try to run `mkcert`. We could like, make the process just a no-op in that case? But I think I'd prefer to just run `neopass-server` by hand when I want it, for simplicity. |
||
|---|---|---|
| .devcontainer | ||
| .husky | ||
| app | ||
| bin | ||
| config | ||
| db | ||
| deploy | ||
| lib | ||
| public | ||
| test | ||
| vendor | ||
| .eslintrc.json | ||
| .gitignore | ||
| .ruby-version | ||
| .yarnrc.yml | ||
| config.ru | ||
| falcon.rb | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE.md | ||
| package.json | ||
| Procfile.dev | ||
| Rakefile | ||
| README.md | ||
| yarn.lock | ||
Dress to Impress
Oh! We've been revitalizing the Rails app! Fun!
There'll be more to say about it here soon :3