fix: preserve /api/ prefix in proxy_pass

[Feikovandijk]

The API registers all routes with /api/ prefix (e.g. /api/csrf-token, /api/games, /api/user). The trailing slash on proxy_pass was stripping the prefix, causing all API routes to return 404.

[gemini-code-assist]

Summary of Changes

Hello @Feikovandijk, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses an issue where API routes were returning 404 errors due to an incorrect Nginx proxy_pass configuration. By removing a superfluous trailing slash, the Nginx proxy will now correctly forward requests, including the /api/ prefix, to the backend, ensuring all API endpoints function as expected.

Highlights

• Nginx Configuration Fix: Corrected the proxy_pass directive in the Nginx configuration to ensure the /api/ prefix is preserved when forwarding requests to the backend, resolving 404 errors for API routes.

Changelog

• user-dashboard/default.conf.template
  • Removed the trailing slash from the proxy_pass directive for the /api/ location block.

Activity

• No human activity has been recorded on this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly fixes a bug in the nginx proxy configuration that was stripping the /api/ prefix from backend requests. The change is correct. I've also added a suggestion to improve the robustness of the API routing by handling requests made to /api without a trailing slash, which are currently not matched by the proxy configuration.