You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Step 3 of the Nuxt SSR example i the function createAdminClient() the process​.env.APPWRITE_ENDPOINT and the process​.env.APPWRITE_ENDPOINT might have the PUBLIC_ prefix, resulting:
const client = new Client()
.setEndpoint(process​.env.PUBLIC_APPWRITE_ENDPOINT!)
.setProject(process​.env.PUBLIC_APPWRITE_PROJECT_ID!)
.setKey(process​.env.APPWRITE_KEY!);
Also, maybe it's better to use the useRuntimeConfig() as in the createSessionClient(event) function.
In the .env file the variable PUBLIC_APPWRITE_PROJECT is missing the ID to match the examples mentioned before:
As this both routes results in the same route, maybe its more clear to put them in the same route as /server/api/allApwriteEndpoints or /server/api/appwrite/allAppwriteEndpoints
In the Setp 7, the server/routes/api/oauth2.get.js example code, the commented name file is wrong, the method mentioned is post and shoud be get.
In the Step 6, the file pages/account.vue is giving the following error: useEvent is not defined
đź‘€ Have you spent some time to check if this issue has been raised before?
đź’ Description
createAdminClient()
theprocess​.env.APPWRITE_ENDPOINT
and theprocess​.env.APPWRITE_ENDPOINT
might have the PUBLIC_ prefix, resulting:Also, maybe it's better to use the
useRuntimeConfig()
as in thecreateSessionClient(event)
function.PUBLIC_APPWRITE_PROJECT
is missing the ID to match the examples mentioned before:As this both routes results in the same route, maybe its more clear to put them in the same route as /server/api/allApwriteEndpoints or /server/api/appwrite/allAppwriteEndpoints
In the Setp 7, the server/routes/api/oauth2.get.js example code, the commented name file is wrong, the method mentioned is post and shoud be get.
In the Step 6, the file pages/account.vue is giving the following error: useEvent is not defined
đź‘€ Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: