Update netlify.toml

[alexander-mart]

Summary by CodeRabbit

• Chores
  • Updated site configuration to proxy all requests to /api/* to an external API endpoint.

[netlify]

✅ Deploy Preview for dtp-stat ready!

Name	Link
🔨 Latest commit	cb2db7c
🔍 Latest deploy log	https://app.netlify.com/projects/dtp-stat/deploys/6877fcad6386d600088f1c04
😎 Deploy Preview	https://deploy-preview-119--dtp-stat.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Walkthrough

A new redirect rule has been introduced in the Netlify configuration to proxy all requests from the /api/* path to an external API endpoint, ensuring the path suffix is preserved. The rule uses a forced status code 200 to override existing routes or files.

Changes

File(s)	Change Summary
netlify.toml	Added a redirect rule to proxy /api/* requests to https://cms.dtp-stat.ru/api/:splat with forced status 200.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Netlify
    participant ExternalAPI as cms.dtp-stat.ru

    User->>Netlify: Request /api/some-path
    Netlify->>ExternalAPI: Proxy /api/some-path to https://cms.dtp-stat.ru/api/some-path
    ExternalAPI-->>Netlify: Response
    Netlify-->>User: Response (status 200)

Loading

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch alexander-mart-patch-2

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

netlify.toml (1)

17-18: Expose only what you must – consider rate-limiting / CORS / auth in front of the CMS

Proxying raw requests to an external CMS may leak internal endpoints or invite abuse (e.g. automated scraping, DoS).
Confirm that the upstream API enforces authentication / rate limits, or add response-header rules (e.g. Cache-Control, Access-Control-Allow-Origin) to mitigate risk.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c12f684 and cb2db7c.

📒 Files selected for processing (1)

• netlify.toml (1 hunks)

🔇 Additional comments (1)

netlify.toml (1)

14-18: Forced rewrite will short-circuit all Netlify/Next.js API routes – verify this is intentional

force = true combined with status = 200 turns the rule into a rewrite that unconditionally grabs every request matching /api/* before the Next.js plugin gets a chance to serve its own /api serverless functions.
If your Next.js project already contains API routes (or you plan to add any later) they will never execute – everything goes straight to https://cms.dtp-stat.ru.

Please double-check that this behaviour is desired; removing force = true (or narrowing the from pattern, e.g. /cms-api/*) keeps the external proxy while still allowing first-party endpoints to coexist.