fix: local dev cannot proxy online and update dev docs

[hexqi]

English | 简体中文

PR

修复本地开发转到接口到线上报错问题
更新前后端启动文档

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• Built its own designer, fully self-validated

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

Background and solution

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• New Features

  • Added an authenticated development option so login can be enabled during local development for testing.

• Chores

  • Updated project scripts and build config to support the new authenticated development workflow.

• Documentation

  • Rewrote and reorganized the development getting-started guide with step-by-step backend setup.
  • Fixed typos in the server deployment instructions.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Added a dev script that enables authenticated dev runs via VITE_AUTH, exposed VITE_AUTH in the design-core Vite config, and updated design-core registry to enable login when VITE_AUTH is true or when not in a development environment. Also editorial/docs fixes and typos.

Changes

Cohort / File(s)	Summary
NPM Scripts Configuration designer-demo/package.json, package.json	Added dev:withAuth scripts: designer-demo runs cross-env VITE_AUTH=true vite; root script chains pnpm run setup then runs the designer-demo dev:withAuth.
Design-core env & auth logic packages/design-core/vite.config.js, packages/design-core/registry.js	Exposed import.meta.env.VITE_AUTH in Vite define; added useAuth = import.meta.env.VITE_AUTH === 'true' and changed enableLogin to `useAuth
Docs / Guides docs/development-getting-started/debugging-of-java-backend.md, docs/solutions/server-deployment-solution-java.md	Large editorial restructure and added backend DB/setup steps in debugging guide; fixed two suto → sudo typos in server-deployment doc.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 I nibbled env keys in the night,
VITE_AUTH glowing soft and bright.
Devs can run with login on,
Hops of joy from dusk to dawn,
A tiny rabbit cheers, delight! 🥕✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects the main changes: it addresses the local dev authentication/proxy issue and documentation updates across multiple files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@docs/development-getting-started/debugging-of-java-backend.md`:
- Line 27: Update each Markdown image that currently uses empty alt text (e.g.,
the line "![](./imgs/java-debugging-image36.png)") to include a short
descriptive alt string inside the brackets (for every occurrence such as
"./imgs/java-debugging-image36.png" and the other images referenced at the noted
locations), so change the alt text to a concise description like "Java debugger
UI showing breakpoints" for that image and similar brief descriptions for the
others to satisfy accessibility/lint rules.
- Line 38: Replace the bolded line "**在按照上述操作后的新建的数据库名称上右键选择“运行 SQL
文件”->在文件项选择下面两个 SQL 文件导入运行**" with a proper Markdown heading (for example prefix
with "##### ") so it becomes a section title instead of bold emphasis; update
the same text to "##### 在按照上述操作后的新建的数据库名称上右键选择“运行 SQL 文件”->在文件项选择下面两个 SQL
文件导入运行" in docs/development-getting-started/debugging-of-java-backend.md.