feat: add more scripts in the makefile

[alichherawalla]

Ticket Link

---

Related Links

---

Description

---

Steps to Reproduce / Test

---

Request

---

Response

---

Summary by CodeRabbit

• New Features

  • Introduced a new environment variable ENV_INJECTION to enhance configuration flexibility.
  • Expanded makefile with new targets for comprehensive project management, including testing, local setup, pre-commit hooks, dependencies, and ECS operations.

• Documentation

  • Updated the README.MD with improved formatting, clearer instructions, and refined script names for better usability.

• Refactor

  • Modified Dockerfile syntax for consistency in build stage declaration.

• Chores

  • Enhanced the local setup script to include server run command for streamlined local development.

[coderabbitai]

Walkthrough

The recent updates encompass a variety of enhancements across the project, focusing on improving development workflows, code readability, and deployment processes. These changes introduce a new environment variable, refine the Dockerfile syntax, restructure the README for better comprehension, and expand the makefile with additional targets for comprehensive project management. Additionally, a script has been updated to facilitate local server execution, streamlining the setup for development environments.

Changes

Files	Change Summaries
.env.docker	Added a new environment variable ENV_INJECTION set to false.
Dockerfile	Changed the declaration of the build stage from FROM golang:1.22-alpine3.19 as builder to FROM golang:1.22-alpine3.19 AS builder.
README.MD	Updates include reformatting text, adjusting script names, updating installation instructions, and clarifying notes for enhanced clarity and consistency.
makefile	Added targets for tests, local environment setup, pre-commit hooks, dependencies, ECS setup, update, and deployment.
scripts/.../setup-local.sh	Added a command to run the server, facilitating easier local development setup.

🐇✨
In the land of code and byte,
Changes come both day and night.
With each commit, we aim to enhance,
Readability, workflow, and advance.
From Docker's depths to README's light,
We hop with joy, our code takes flight.
🚀🌟

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.

[coderabbitai]

Actionable comments posted: 0

Actionable comments outside the diff hunks (1)

scripts/setup-local.sh (1)

Line range hint 2-3: Replace source with . for POSIX compliance.

- set -a && source .env.base && set +a
- set -a && source .env.local && set +a
+ set -a && . .env.base && set +a
+ set -a && . .env.local && set +a

Review Status

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between ba94b8a and 87d3d32.

Files selected for processing (5)

• .env.docker (1 hunks)
• Dockerfile (1 hunks)
• README.MD (9 hunks)
• makefile (1 hunks)
• scripts/setup-local.sh (1 hunks)

Files skipped from review due to trivial changes (3)

• .env.docker
• Dockerfile
• README.MD

Additional comments not posted (2)

scripts/setup-local.sh (1)

16-16: LGTM! The addition of the server run command is a logical step after setting up the environment, migrations, and seeding data.

makefile (1)

18-40: LGTM! The addition of new targets for testing, local setup, pre-commit setup, dependency management, and ECS operations enhances the makefile's functionality and streamlines the development and deployment workflow.