admin_pages_dev: Modified Laravel Configurations

[Riyad-Murad]

Summary by Sourcery

CI:

• Use EC2_HOST_PRODUCTION instead of EC2_HOST_STAGING for APP_URL in the production Docker deployment workflow

[sourcery-ai]

Reviewer's Guide

Updated the GitHub Actions production deployment workflow to generate the APP_URL using the production EC2 host secret instead of the staging host.

File-Level Changes

Change	Details	Files
Swapped out the staging host for the production host when echoing APP_URL	Replaced EC2_HOST_STAGING with EC2_HOST_PRODUCTION in the APP_URL echo command Adjusted .env.example generation to reflect the production URL	.github/workflows/stacksDockerDeployProduction.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @Riyad-Murad - I've reviewed your changes - here's some feedback:

• Use >> instead of > when echoing APP_URL so you don’t overwrite the previously written APP_KEY line
• Parameterize the port (8000) or default to port 80 for production URLs to avoid hard-coding port numbers
• Consider switching to HTTPS for APP_URL in production to ensure secure connections

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

suggestion: Streamline .env file creation with a heredoc

Use a heredoc instead of multiple echo calls to avoid overwriting and write all variables in one block. For example:

cat <<EOF > .env.example
APP_KEY=${{ secrets.LARAVEL_APP_KEY }}
APP_URL=http://${{ secrets.EC2_HOST_PRODUCTION }}:8000
DB_CONNECTION=mysql
DB_HOST=${{ secrets.LARAVEL_DATABASE_HOST }}
DB_PORT=${{ secrets.LARAVEL_DATABASE_PORT_NUMBER }}
EOF