Moderator
hm maybe inside the astro file it thinks it's a server and not a user?
Votes
0
Replies
24
Participants
Unknown
Messages
25
Moderator
hm maybe inside the astro file it thinks it's a server and not a user?
Probably
Moderator
wouldn't that return a permission error though
Moderator
instead of the collection ID error
Or it gets/tried to be executed where the astro file is saved instead
Moderator
yeah I mean the why could be a few things but the other confusing thing
Moderator
is that when I call it on the dashboard I use a persistentMap storage with Nanostores
Moderator
which should locally store it, but that's empty too
I think not
Moderator
hm
Moderator
yeah
Moderator
that's it
Moderator
so should I use the server SDK?
Nope
From what I see here: https://github.com/appwrite/demos-for-astro they're managing it by having a separate typescript file to handle appwrite related stuff
Sincerely I don't have knowledge on how Astro works, since web development isn't my main specialization, plus every 5 seconds, a new JS framework is released 😆
Moderator
honestly Astro is great
To debug, you can try looking at the network requests to see what's going on and if the various cookies and headers are correct
Probably not but I also don't know Astro
If a user doesn't have access to something, they'll get a 404. This is to hide the fact that the document even exists
Moderator
okay so
Moderator
What I think I should do
Moderator
is look at the headers Astro sends and has
Moderator
and probably make an integration for Astro + Appwrite huh
maybe. i dunno anything about astro