As part of support for permalinks, we now use Vercel KV to store seed data. The key for that data is used to in the seed route. This is really cool, but we would also like to support generating seeds locally without the need for the KV.
Some potential solutions:
- Fully serialize all seed data and put that on the route. This was the initial version of permalinks, but they are too long and make sharing seed URLs ugly.
- Store generated seed data in
index.db instead of Vercel KV.
- Generate our old style seed routes which use the shorter encoding of just the parameters as opposed to all the item/boss/area locations. We might need to add a few more things to the URL like
race and spoiler, but those could potentially be search params.
The README needs to be updated to describe whatever solution we choose, and it also needs to explain about how to setup Vercel KV for the site.
As part of support for permalinks, we now use Vercel KV to store seed data. The key for that data is used to in the seed route. This is really cool, but we would also like to support generating seeds locally without the need for the KV.
Some potential solutions:
index.dbinstead of Vercel KV.raceandspoiler, but those could potentially be search params.The README needs to be updated to describe whatever solution we choose, and it also needs to explain about how to setup Vercel KV for the site.