diff --git a/pages/onedrive-vercel-index-oauth/step-1.tsx b/pages/onedrive-vercel-index-oauth/step-1.tsx index 08a1f39..831097e 100644 --- a/pages/onedrive-vercel-index-oauth/step-1.tsx +++ b/pages/onedrive-vercel-index-oauth/step-1.tsx @@ -1,4 +1,5 @@ import Head from 'next/head' +import Image from 'next/image' import { useRouter } from 'next/router' import siteConfig from '../../config/site.json' @@ -8,7 +9,6 @@ import Footer from '../../components/Footer' import { FontAwesomeIcon } from '@fortawesome/react-fontawesome' export default function OAuthStep1() { - const redis_url = process.env.REDIS_URL const router = useRouter() return ( @@ -22,30 +22,37 @@ export default function OAuthStep1() {
-

Welcome to your new onedrive-vercel-index 🎉

+
+ fabulous fireworks +
+

Welcome to your new onedrive-vercel-index 🎉

+ +

Step 1/3: Preparations

+ +

+ If you have not specified a REDIS_URL + inside your Vercel env variable, go initialise one at{' '} + + Upstash + + . Docs:{' '} + + Vercel Integration - Upstash + + . +

Authorisation is required as no valid{' '} access_token or{' '} refresh_token is - present on this deployed instance. -

- -

Step 1/3: Preparations

- -

- Check the following configurations (especially client_id and{' '} - client_secret (obfuscated)) and see if they match the official - ones specified in the documentation of{' '} - - onedrive-vercel-index - {' '} - before proceeding with authorising this application with your own Microsoft account. + present on this deployed instance. Check the following configurations before proceeding with authorising + onedrive-vercel-index with your own Microsoft account.

@@ -103,15 +110,11 @@ export default function OAuthStep1() {
-

+

If you see anything - missing or incorrect, you need to reconfigure /config/api.json{' '} + missing or incorrect, you need to reconfigure /config/api.json{' '} and redeploy this instance.

-

- ️ If you are previewing - this locally, you would need to reauthorise yourself when you eventually deploy the site on Vercel. -