From 825fb4cbfe43313840618c3ea815b6acc522d440 Mon Sep 17 00:00:00 2001 From: Jun-te Kim Date: Mon, 8 Dec 2025 09:28:01 +0000 Subject: [PATCH] save local changes --- README.md | 5 ++++- src/app/page.tsx | 4 ---- 2 files changed, 4 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 89a2707a..57b3fb4f 100644 --- a/README.md +++ b/README.md @@ -130,4 +130,7 @@ In our terraform stack, we have a module called `s3_presignable_bucket` which co We will generate a pre-signed url and then make a post request to that endpoint to store that data to s3. Part of that process is the creation of an AWS IAM role which contains the permission set to access the bucket, `rerofit-plan-inputs-`. The name of this IAM role is `s3_presign_role_` and for our NextJS application, as it's hosted outside of AWS (for the moment), we need to generate a set of access credentials to give the application access to this bucket. The access key and secret key are automatically generated and stored in AWS secrets manager under `dev/presign_frontend/access_key` and `dev/presign_frontend/secret_key` and need to be set in the environment for the pre-sign api to store csv data to aws. -# +Quick wins: + +- [] Sign in butotn in microsoft disappear! +- [] Frequently asked questions page diff --git a/src/app/page.tsx b/src/app/page.tsx index 3de27a2a..887a65cd 100644 --- a/src/app/page.tsx +++ b/src/app/page.tsx @@ -1,7 +1,6 @@ import { getServerSession } from "next-auth/next"; import { AuthOptions } from "./api/auth/[...nextauth]/authOptions"; import GoogleSignInButton from "./components/signin/GoogleSignInButton"; -import MicrosoftSignInButton from "./components/signin/MicrosoftSignInButton"; import EmailSignInButton from "./components/signin/EmailSignInButton"; import { redirect } from "next/navigation"; import Image from "next/image"; @@ -51,9 +50,6 @@ export default async function Home(props: {
Sign in with a Social Account
-
- -