Separated laravel app to its own folder

[JhumanJ]

Summary by CodeRabbit

• New Features

  • Introduced a new .gitignore file for the API directory to maintain a clean repository.
  • Added utility functions for URL construction and pricing feature management.
  • Enhanced email configuration settings for improved email communications.

• Improvements

  • Streamlined Docker setup instructions in the README for clarity.
  • Updated CI workflow configuration to ensure commands are executed in the correct context for deployment and environment preparation.

• Bug Fixes

  • Removed unnecessary environment files from the ignore list, potentially improving the build and deployment process.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes encompass updates to the GitHub Actions workflow for a Laravel project, modifications to configuration files, and adjustments in the README instructions. Key updates include a new .gitignore file for the api directory, the introduction of utility functions in helpers.php, refined email configurations, and streamlined setup instructions for Docker. Additionally, formatting improvements have been made for consistency and readability across various files.

Changes

File(s)	Change Summary
.github/workflows/laravel.yml	Adjusted branch name formatting, set explicit working directory for steps, updated environment preparation and deployment steps.
.gitignore	Removed several environment files and directories from the ignore list, indicating a reorganization of ignored files.
README.md	Updated setup instructions for Docker, removed copying of environment files, added command for creating a Docker Compose override file.
api/.env.docker	Added specific email configuration values for MAIL_USERNAME, MAIL_FROM_ADDRESS, and MAIL_FROM_NAME.
api/.gitignore	Created a new .gitignore file specifying files and directories to be ignored in the api directory.
api/app/helpers.php	Introduced utility functions: front_url for constructing URLs and pricing_enabled for checking pricing feature activation.
api/config/filesystems.php	Minor formatting change in the concatenation of the env('APP_URL') setting in the 'url' key of the 'public' configuration array.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Docker
    participant App

    User->>Docker: Start setup
    Docker->>App: Create docker-compose.override.yml
    App-->>Docker: File created
    User->>App: Configure environment
    App-->>User: Ready to use

Loading

🐇 "In the land of code so bright,
Changes hop with pure delight.
New helpers join the playful dance,
With Docker's charm, we take a chance.
Ignore the clutter, let it be,
A cleaner path for all to see!" 🐰✨

---

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