fix: revert proxy url changes

[fred-bf]

close #4795

issue mentioned here would appear again: #1738

Summary by CodeRabbit

• Chores
  • Updated Docker configuration to change the HOSTNAME environment variable to "0.0.0.0" for improved accessibility.
  • Simplified the CMD instruction by removing redundant --host 0.0.0.0 argument.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nextchat	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 26, 2024 9:40am

[coderabbitai]

Warning

Review failed

The pull request is closed.

Walkthrough

The recent changes in the Dockerfile address a bug where deploying version 2.12.3 of the chatgpt-next-web with the PROXY_URL was causing access issues. This was resolved by altering the HOSTNAME environment variable from 127.0.0.1 to 0.0.0.0 and removing the --host 0.0.0.0 argument from the proxychains command.

Changes

File	Change Summary
Dockerfile	Updated HOSTNAME from 127.0.0.1 to 0.0.0.0 and modified proxychains CMD instruction by removing --host 0.0.0.0 argument.

Assessment against linked issues

Objective	Addressed	Explanation
2.12.3 should run with the PROXY_URL parameter (#4795)	✅

In a land of code and dreams,
The host was fixed, or so it seems,
From 127 to 0.0.0.0,
Now through proxies, data flows,
Bugs were squashed, connections thrive,
Version 2.12.3, now come alive. 🎉

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @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.

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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[bygsn]

@fred-bf Hello,

I am the submitter of PR #4902 (Export sync config). I noticed that my PR encountered some issues during the checks, especially the Vercel deployment preview requiring authorization. I have a few questions:

1. I see the prompt "Authorization required to deploy". Is this normal? As an external contributor, what do I need to do to resolve this issue?

2. Apart from this authorization issue, do you see any other aspects of my PR that need modification or improvement?

3. As a new contributor, are there any specific points I should pay attention to when submitting PRs?

I greatly appreciate your time and guidance. If you need me to make any changes or provide more information, please let me know, and I will address it promptly.

Thank you again for your help!