use .env for prod and staging

[mjadach-iv]

• use .env for prod and staging
• Prod is main branch
• Staging is staging branch
• added readme for the frontend

Summary by CodeRabbit

• Chores

  • Updated deployment trigger branch from prod to main.
  • Changed branch trigger from main to staging for the deployment workflow.
  • Added /frontend/.env to .gitignore.
  • Updated scripts in package.json for backend and frontend development.

• Documentation

  • Added instructions in README.md for running backend and frontend locally.
  • Introduced environment variables in frontend/.env.example for configuration.

• Refactor

  • Updated serverurl declaration in frontend/src/App.js to use an environment variable.
  • Modified initialization of uHTTP in frontend/src/Portfolio.js to use environment variables dynamically.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
mytokentracker-xyz	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 28, 2024 11:54am

[esterlus]

nice improvement

[coderabbitai]

Walkthrough

Walkthrough

The recent updates focus on refining deployment workflows, enhancing environment variable usage, and streamlining project scripts. These changes aim to improve deployment flexibility, configuration management, and development efficiency.

Changes

File	Summary
.github/workflows/deploy-prod.yml .github/workflows/deploy-stage.yml	Updated deployment trigger branches.
.gitignore	Added /frontend/.env to the ignore list.
README.md	Expanded instructions for local setup and environment variables.
frontend/.env.example	Introduced environment variables for backend configuration in the example file.
frontend/src/App.js frontend/src/Portfolio.js	Enhanced usage of environment variables for dynamic configuration in frontend components.
package.json	Refactored scripts for frontend and backend development tasks.

---

Note

Pull Request Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://coderabbit.ai

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 full the 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.