Availability of named resources (for new hosting on Netlify)

[tdmalone]

This issue is to discuss supporting named resources (eg. /pokemon/bulbasaur) when we move to Netlify.

See also #373 for work on fixing named resources on our current hosting.

[sargunv]

Context: the final blocker is the build timeout on Netlify due to too many files (after adding named resources). Potential solutions include:

• Shard the netlify sites by endpoint. This requires a modification to the build script to whitelist or blacklist endpoints to build
• Generate all approx 5000 rewrite rules needed to support named resources at build time

[tdmalone]

Thanks @sargunv!

And I've e-mailed Netlify to ask if it's possible to either increasing the build time, or whether there's a particular redirect limit (I couldn't find either of these answers in their documentation).

[Naramsim]

https://pokeapi.co/api/v2/item/old-rod/

[Naramsim]

maybe I shouldn't have closed the issue...

[sargunv]

You got the wrong one :) It's #373

[sargunv]

https://pokeapi.netlify.com/api/v2/pokemon/magikarp/encounters/

Looks like all we needed to do is disable post processing (we weren't using that anyway). So, it works!

[tdmalone]

Ohh niiice, awesome find @sargunv!!

[sargunv]

Unfortunately we have one more blocker for moving to Netlify: PokeAPI/api-data#11

[sargunv]

I spoke too soon. Not sure why that build succeeded, but the next one failed again.