Gitignore Configuration for Ddev

/.ddev/*
!/.ddev/config.yml

### Explanation:
– `/.ddev/*` → Ignores all files and subdirectories inside `.ddev`
– `!/.ddev/config.yml` → Excludes `config.yml` from being ignored, allowing it to be tracked in Git

This setup ensures that only `config.yml` is committed while other files in `.ddev` (like database dumps, logs, and other local config files) remain untracked.

on:
push:
branches:
– master # Trigger on push to master branch

jobs:
deploy:
runs-on: ubuntu-latest
steps:
– name: Checkout code
uses: actions/checkout@v2

– name: Set up SSH
env:
PEM_FILE: ${{ secrets.PEM_FILE }} # Store your PEM file content in GitHub secrets
run: |
echo "$PEM_FILE" > key.pem
chmod 600 key.pem

– name: Ensure proper permissions on EC2
env:
EC2_USER: ${{ secrets.EC2_USER }} # Store your EC2 username in GitHub secrets
EC2_HOST: ${{ secrets.EC2_HOST }} # Store your EC2 host in GitHub secrets
run: |
# Ensure that the correct permissions are set on the EC2 instance
ssh -i key.pem -o StrictHostKeyChecking=no $EC2_USER@$EC2_HOST "sudo chown -R $EC2_USER:$EC2_USER /var/www/shareyourthoughts && sudo chmod -R 775 /var/www/shareyourthoughts"

– name: Delete public/build folder from EC2
env:
EC2_USER: ${{ secrets.EC2_USER }} # Store your EC2 username in GitHub secrets
EC2_HOST: ${{ secrets.EC2_HOST }} # Store your EC2 host in GitHub secrets
run: |
ssh -i key.pem -o StrictHostKeyChecking=no $EC2_USER@$EC2_HOST "rm -rf /var/www/shareyourthoughts/public/build"

– name: Deploy to EC2
env:
EC2_USER: ${{ secrets.EC2_USER }} # Store your EC2 username in GitHub secrets
EC2_HOST: ${{ secrets.EC2_HOST }} # Store your EC2 host in GitHub secrets
run: |
# Run rsync with updated timestamps only for changed files, excluding storage if needed
rsync -avz –exclude 'storage/*' -e "ssh -i key.pem -o StrictHostKeyChecking=no" ./ $EC2_USER@$EC2_HOST:/var/www/shareyourthoughts

– name: Change ownership to www-data
env:
EC2_USER: ${{ secrets.EC2_USER }} # Store your EC2 username in GitHub secrets
EC2_HOST: ${{ secrets.EC2_HOST }} # Store your EC2 host in GitHub secrets
run: |
# Change ownership to www-data:www-data
ssh -i key.pem -o StrictHostKeyChecking=no $EC2_USER@$EC2_HOST "sudo chown -R www-data:www-data /var/www/shareyourthoughts"
rm key.pem # Clean up the PEM file after the final deployment
also run composer update to install any new library on server if at local

### Updated Workflow:

name: Deploy to EC2

on:
  push:
    branches:
      - master  # Trigger on push to master branch

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - name: Set up SSH
        env:
          PEM_FILE: ${{ secrets.PEM_FILE }}  # Store your PEM file content in GitHub secrets
        run: |
          echo "$PEM_FILE" > key.pem
          chmod 600 key.pem

      - name: Ensure proper permissions on EC2
        env:
          EC2_USER: ${{ secrets.EC2_USER }}  
          EC2_HOST: ${{ secrets.EC2_HOST }}  
        run: |
          ssh -i key.pem -o StrictHostKeyChecking=no $EC2_USER@$EC2_HOST "sudo chown -R $EC2_USER:$EC2_USER /var/www/shareyourthoughts && sudo chmod -R 775 /var/www/shareyourthoughts"
          
      - name: Delete public/build folder from EC2
        env:
          EC2_USER: ${{ secrets.EC2_USER }}  
          EC2_HOST: ${{ secrets.EC2_HOST }}  
        run: |
          ssh -i key.pem -o StrictHostKeyChecking=no $EC2_USER@$EC2_HOST "rm -rf /var/www/shareyourthoughts/public/build"
      
      - name: Deploy to EC2
        env:
          EC2_USER: ${{ secrets.EC2_USER }}  
          EC2_HOST: ${{ secrets.EC2_HOST }}  
        run: |
          rsync -avz --exclude 'storage/*' -e "ssh -i key.pem -o StrictHostKeyChecking=no" ./ $EC2_USER@$EC2_HOST:/var/www/shareyourthoughts

      - name: Install Composer dependencies
        env:
          EC2_USER: ${{ secrets.EC2_USER }}  
          EC2_HOST: ${{ secrets.EC2_HOST }}  
        run: |
          ssh -i key.pem -o StrictHostKeyChecking=no $EC2_USER@$EC2_HOST "
          cd /var/www/shareyourthoughts && 
          composer install --no-dev --optimize-autoloader &&
          composer update --no-dev --optimize-autoloader"

      - name: Change ownership to www-data
        env:
          EC2_USER: ${{ secrets.EC2_USER }}  
          EC2_HOST: ${{ secrets.EC2_HOST }}  
        run: |
          ssh -i key.pem -o StrictHostKeyChecking=no $EC2_USER@$EC2_HOST "sudo chown -R www-data:www-data /var/www/shareyourthoughts"
          rm key.pem  # Clean up the PEM file after deployment

### Added Changes:
1. **Added a step to run `composer install` and `composer update` on the EC2 instance.**
– `composer install –no-dev –optimize-autoloader` ensures dependencies are installed efficiently.
– `composer update –no-dev –optimize-autoloader` updates any new dependencies if required.

This will ensure that your Laravel app always has the latest dependencies deployed on EC2. 🚀

### Updated Code:

'github' => [
    'client_id' => env('GITHUB_CLIENT_ID', 'Ov23liAp5Lc6XG4i18MU'),
    'client_secret' => env('GITHUB_CLIENT_SECRET', '48f59eed25e88216a483344a4ca0917960f873ab'),
    'redirect' => env('GITHUB_REDIRECT_URI', env('APP_URL') . '/github-callback'),
],

### Explanation:
– If `GITHUB_REDIRECT_URI` is **not set** in the `.env` file, it will **fallback** to `APP_URL/github-callback`.
– This ensures that your app dynamically uses the correct base URL depending on the environment (local, staging, production).

### Next Steps:
– Run `php artisan config:clear` to refresh the configuration cache.
– Ensure `APP_URL` is correctly set in your `.env` file.

Let me know if you need further adjustments! 🚀

—

### ✅ **1. Ensure the `.gitignore` Rule is Correct**
Your `.gitignore` has this:

/.ddev/*
!/.ddev/config.yml

✔ This should work, allowing `.ddev/config.yml` while ignoring everything else in `.ddev`.

—

### ✅ **2. Force Git to Track the File**
Since `.gitignore` was ignoring `.ddev/config.yml` before, Git might not be tracking it. Run these commands to fix it:

git add -f .ddev/config.yml
git commit -m "Force add .ddev/config.yml"
git push origin master

—

### ✅ **3. Check if the File is Already Ignored**
Run:

git check-ignore -v .ddev/config.yml

– If it prints a line, that means it's still being ignored.
– If so, check if there’s another rule in `.gitignore` or `.git/info/exclude` that’s blocking it.

—

### ✅ **4. Ensure `.gitignore` is Updated**
If you've modified `.gitignore`, make sure it's applied:

git rm -r --cached .ddev
git add .ddev/config.yml
git commit -m "Update .gitignore and track .ddev/config.yml"
git push origin master

—

### ✅ **5. Check `.gitattributes` (If Exists)**
If there's a `.gitattributes` file, check if it has:

.ddev/config.yml export-ignore

If it does, remove that line and commit the change.

—

### 🔥 **Final Fix: Re-clone Repository**
If none of the above works, try this:

git clone <repo-url> new-folder
cd new-folder
ls -la .ddev/

If `.ddev/config.yml` is missing, something else is preventing the commit. Let me know what you see. 🚀

—

### ✅ **1. Check If the File Is Ignored**
Run this command to verify whether Git is ignoring the file:

git check-ignore -v .ddev/config.yml

– **If it prints a line** → The file is still being ignored.
– **If no output appears** → The file is not ignored, and something else might be causing the issue.

—

### ✅ **2. Force Git to Track the File**
If `.ddev/config.yml` was ignored before, Git might not be tracking it. Run:

git add -f .ddev/config.yml
git commit -m "Force add .ddev/config.yml"
git push origin master

—

### ✅ **3. Remove Cached `.ddev` (If Needed)**
Since `.gitignore` rules don’t apply retroactively, you may need to remove `.ddev` from Git’s cache and re-add the config file:

git rm -r --cached .ddev
git add .ddev/config.yml
git commit -m "Fix tracking for .ddev/config.yml"
git push origin master

—

### ✅ **4. Ensure No `.gitattributes` Conflicts**
Check if you have a `.gitattributes` file that contains:

.ddev/config.yml export-ignore

If so, **remove that line** and commit the change.

—

### ✅ **5. Confirm Git Status**
Run:

git status

– If `.ddev/config.yml` is in the list of **"Changes not staged for commit"**, run:

git add .ddev/config.yml
git commit -m "Track .ddev/config.yml"
git push origin master

—

### ✅ **6. Clone Repo Fresh (Last Resort)**
If nothing works, try re-cloning your repository:

git clone <repo-url> new-folder
cd new-folder
ls -la .ddev/

Check if `.ddev/config.yml` appears. If not, let me know what you see.

—

**This should fix the issue!** Let me know if you need further help. 🚀

—

### ✅ **1. Check If the File Exists**
Run:

ls -la .ddev/

or on PowerShell:

Get-ChildItem -Path .ddev -Force

If `.ddev/config.yml` **does not exist**, that’s the issue—you need to create it.

—

### ✅ **2. Check If Git Is Ignoring the File**
Run:

git check-ignore -v .ddev/config.yml

– If it **shows output**, Git is still ignoring the file.
– If **no output**, then Git is not ignoring it.

—

### ✅ **3. Re-add the File to Git**
Try forcing Git to track `.ddev/config.yml`:

git add -f .ddev/config.yml
git commit -m "Force track .ddev/config.yml"
git push origin master

—

### ✅ **4. Verify If the File Is in the Repository**
Run:

git ls-files | grep .ddev/config.yml

If it **does not appear**, the file is either missing or Git is still ignoring it.

—

### ✅ **5. Reset `.gitignore` (If Needed)**
If `.ddev/config.yml` is still ignored, modify `.gitignore` to make sure the rules are correct. Ensure you have:

/.ddev/*
!/.ddev/config.yml

Then, reapply the changes:

git rm -r --cached .ddev
git add .ddev/config.yml
git commit -m "Fix .gitignore to include .ddev/config.yml"
git push origin master

—

### ✅ **6. Try Cloning Fresh**
If nothing works, test by cloning the repo into a new folder:

git clone <repo-url> test-folder
cd test-folder
ls -la .ddev/

If `.ddev/config.yml` is missing, something is preventing it from being pushed.

—

This should fix it! 🚀 Let me know what happens.

—

### ✅ **1. Verify That the File Exists**
Run this command in **PowerShell**:

Get-ChildItem -Path .ddev -Force

or in **Git Bash**:

ls -la .ddev/

– If `.ddev/config.yml` **is missing**, create it manually.
– If it **exists**, move to the next step.

—

### ✅ **2. Confirm That Git Is Not Ignoring It**
Run:

git check-ignore -v .ddev/config.yml

– If it **returns a result**, Git is still ignoring the file.
– If it **does not return anything**, Git should track it.

—

### ✅ **3. Manually Add the File**
If Git ignored it before, you may need to **force-add** it:

git add -f .ddev/config.yml
git commit -m "Force add .ddev/config.yml"
git push origin master

—

### ✅ **4. Verify `.gitignore` Rules**
Make sure **these exact lines** are in `.gitignore`:

/.ddev/*
!/.ddev/config.yml

Then, remove `.ddev` from Git's cache and re-add the config file:

git rm -r --cached .ddev
git add .ddev/config.yml
git commit -m "Fix .ddev/config.yml tracking"
git push origin master

—

### ✅ **5. Rename and Recreate the File**
If nothing works, try renaming and recreating the file:

mv .ddev/config.yml .ddev/config_backup.yml
touch .ddev/config.yml
git add -f .ddev/config.yml
git commit -m "Re-add .ddev/config.yml"
git push origin master

—

### ✅ **6. Clone the Repository in a New Folder**
If it's still not being tracked, try cloning your repo into a new folder:

git clone <repo-url> new-folder
cd new-folder
ls -la .ddev/

If `.ddev/config.yml` is missing, it means it was never committed.

—

**Let me know what you find at each step!** 🚀

### **Fix the Issue**
Try these steps:

#### **1. Rename the file**
Run the following command inside the `.ddev` directory:

mv .ddev/config.yaml .ddev/config.yml

Then check if Git detects it:

git status

#### **2. Add the file manually**
If Git is still not tracking it, force add it:

git add -f .ddev/config.yml
git commit -m "Adding .ddev/config.yml"
git push origin master

#### **3. Verify `.gitignore`**
Make sure your `.gitignore` contains:

/.ddev/*
!/.ddev/config.yml

Then run:

git rm -r --cached .ddev
git add .ddev/config.yml
git commit -m "Fix .ddev/config.yml tracking"
git push origin master

Let me know if this works! 🚀