Closed wpmonty closed 3 years ago
bump @Oktalize
@wpmonty I was looking through the code again and I forgot about this API. Wouldn't this cause issues since next export
disables API routes?
@wpmonty I was looking through the code again and I forgot about this API. Wouldn't this cause issues since
next export
disables API routes?
Good call; I wonder how Fleek recommends handling APIs - maybe ship them off to AWS lambda lol
@wpmonty I was looking through the code again and I forgot about this API. Wouldn't this cause issues since
next export
disables API routes?Good call; I wonder how Fleek recommends handling APIs - maybe ship them off to AWS lambda lol
AWS lambda, or maybe even Akash? This is definitely one the areas that needs improvement for Web3. I am thinking that most of the reasons Fleek doesn't do it because they need maximum compatibility with IPFS. But then again I know there are databases with IPFS that could be leveraged somehow, it's just something I know nothing about.
Until we resolve the fundamental issue of APIs with Fleek, there is no reason to merge in next export
This drops in
next export
so Fleek can pick it up for creating pure static site.