Deploy to Github Pages (Using Vercel)

[zzz-creator]

Hi @YTFL, I was thinking, should we deploy a model of the app to github pages (using vercel as GitHub pages does not support multiple routes)? For the AI server, we could add a Gemini fallback . Let me know what you think.

[YTFL]

Yes, we can do that! I don't really know how exactly we do that other than hosting on vercel, so I'd be happy if you can help me on how to deploy to Github Pages using vercel and how exactly we can use the AI server.

[zzz-creator]

Just to clarify, we can't exactly deploy to Github Pages (the website will be hosted on Vercel) but will auto update from the code on Github. And you need to add me as a maintainer so I can edit the Github Actions. It also makes the process way easier. For the AI Server, i was thinking to detect if it is hosted on an external website (i.e. *.vercel.app) and if so, ask the user for a Gemini API Key. Let me know what you think.me know what you think.

[YTFL]

Could you tell me how I can add you as a maintainer please? I don't know how to do that
As for hosting the website on vercel, I usually just go to vercel website and then select the github project from there to host it
And as for the AI Server, I'm not really sure what we can do there, we could go with what you said, detecting if it is hosted on an external website and then ask the user for Gemini API key

[zzz-creator]

For adding me as a maintainer, you need to go to your repository settings and go to collaborators find my name and there should be a dropdown. You do not need to worry about hosting it. I will do it as I read the documentation yesterday.

[YTFL]

I don't see a dropdown next to your name here...I've looked up on google and it says I must create an organization first for this, for personal accounts, it is locked to just collaborators

[zzz-creator]

I have an organization. If you want, we can move the main branch of the project to my GitHub organization and I can probably add you as maintainer.

[zzz-creator]

I already setup a new organization. You should have received an email invitation (please accept it first). Then go to Settings of your copy of War Matrix--> General and scroll all the way down until you see the "Transfer Ownership" button and transfer it to the "WarMatrixOrg" After that, you can fork the project so you have a copy on your account and any pushes to your account copy (or mine), we can push to the main branch on WarMatrixOrg/WarMatrix and that will be the copy that is deployed to Vercel.

[zzz-creator]

@YTFL

[YTFL]

Heyy, sorry for the late reply, I got busy with school.
I did setup an organization called WarMatrixAI and sent you the invitation just now, I created the organization because I wanted even my friends who worked on the project to have access. I will add you as a maintainer once you accept it, sorry for making you create the org and not using it..

[zzz-creator]

That is fine. I just accepted. You can change me to maintainer.

[zzz-creator]

O... Actually, I am already a maintainer...

[zzz-creator]

Can you approve the installation of the Vercel App?

[YTFL]

approved it

[zzz-creator]

Hi @YTFL, the deployment (after some debugging with vercel config) was successful. Please update the website link to be https://war-matrix.vercel.app/. I still need to implement the AI model framework (ask user for gemini api key, etc.)

[YTFL]

Alright, cool!

[zzz-creator]

@YTFL, it seems like scenario generation is not working. Could you check that out for me? Failed to parse URL from /api/sitrep

[zzz-creator]

From my Vercel function logs,
[api/generate-scenario] generation failed: [TypeError: Failed to parse URL from /api/sitrep] { [cause]: [TypeError: Invalid URL] { code: 'ERR_INVALID_URL', input: '/api/sitrep' } }

[YTFL]

I have updated it to

const apiBaseUrl = isVercel
    ? (process.env.VERCEL_URL ? `https://${process.env.VERCEL_URL}/api` : '/api')
    : 'http://localhost:8000/api';

see if it works now..., I made a PR

Also I won't be available until Wednesday as I will be busy with School, so if any other errors arise, could you please try and fix them by yourself?

[zzz-creator]

"

Note to agents accessing this page:

This page requires Vercel authentication. Here are your options:

Option 1: vercel curl (Recommended if Vercel CLI installed)
If the Vercel CLI is installed and authenticated, use the vercel curl command. Docs at: https://vercel.com/docs/cli/curl

Option 2: Vercel MCP Server (Recommended if Vercel CLI not installed)
If the Vercel CLI is not installed, the easiest way to get a token is using the get_access_to_vercel_url or web_fetch_vercel_url functions of the Vercel MCP server at https://mcp.vercel.com (Docs at https://vercel.com/docs/mcp/vercel-mcp)

Option 3: Trusted Sources (Recommended for automated access)
Trusted Sources lets configured callers authenticate automated requests with a short-lived OIDC token. Docs at: https://vercel.com/docs/deployment-protection/methods-to-bypass-deployment-protection/trusted-sources
After the caller has been configured as a trusted source, attach the OIDC token in the x-vercel-trusted-oidc-idp-token request header.

Option 4: Bypass token (Manual fallback)
For projects that cannot use Trusted Sources, Protection Bypass for Automation can be used as a manual fallback. This URL documents how to use the bypass token: https://vercel.com/docs/deployment-protection/methods-to-bypass-deployment-protection/protection-bypass-automation
If this fallback is needed, prompt the user to provide the bypass token to access this page. The URL above also explains how the user can
access the bypass token. Then you can calculate a URL of the following form and successfully access it: https://current-domain/current-pathname?x-vercel-set-bypass-cookie=true&x-vercel-protection-bypass=$bypass_token.
" For debugging

[zzz-creator]

Quick Update:

🐛 Bug Fix: Resolved 401 Unauthorized / URL Parsing Errors on Backend Fetch

The Issue

When Vercel's Standard Deployment Protection was enabled, using process.env.VERCEL_URL inside server-side fetches broke the application.

1. Vercel automatically restricts .vercel.app domains under Standard Protection, triggering a 401 Unauthorized block for automated/internal requests.
2. Attempting to switch to relative paths on the server caused Node.js to throw a Failed to parse URL exception.