Where is that?
The thing is, it's on localhost, so caching shouldn't be really that big of an issue.. right?
And it's really weird because sometimes I see all documents, but when I refresh again, it's just one
Even purging cache doesn't help
<:2HAhaa:746401772779601930>
Or maybe it did..? I don't know, I'll publish it on a domain and see what happens
Where does your Appwrite instance running?
If on a server and the server is behind Cloudflare then it could be the edge cache generally but Cloudflare never cache sensitive data if the app running on the server (in this case Appwrite) properly setup the headers
What if you use curl?
(With โverbose)
postman is correct, i'll see about caching tomorrow with cf
the custom domain probs has no caching rules
If it's right using postman for both domains, then maybe it's a problem with the edge runtime and/or nextjs
yeah
I hate nextjs ๐คฃ
And what is that you love? ๐
why is that? ^^
You can disable caching and every additional proxy features with the development mode
thats not smart? just make a cache config rule in cf
lol
SSR always makes things more complicated. Nextjs does a ton of magic stuff that leads to weird behavior (honestly, it's probably because I don't know enough about it).
Did you know nextjs automatically caches too? https://nextjs.org/docs/app/building-your-application/data-fetching/fetching-caching-and-revalidating
Yeah that would be definitely more smart but itโs faster ๐
yeah, not on dev tho
Anyway if you self host Appwrite then why is important to use an extra server layer with SSR?
Recommended threads
- Local appwrite run functions --user-id n...
Hi, I'm running into an issue when testing Appwrite functions locally with user impersonation. I'm using a self-hosted Appwrite instance and running functions ...
- Selfhosted Github App installation
I've followed this guide: https://appwrite.io/docs/advanced/self-hosting/configuration/version-control to connect GitHub to my self-hosted Appwrite instance (1....
- User ID case sensitivity
I see that through REST (and SDK as well), getting a user is not case sensitive. And even though documentation does not clearly state that it is, the wording "V...