Laravel and WordPress DDEV Setup

### 1. **Set Up DDEV for Laravel**

If you haven't already set up DDEV for your Laravel application, follow these steps:

1. **Navigate to Your Laravel Project Directory**:

cd /path/to/your/laravel/project

2. **Initialize DDEV**:

ddev config

– Follow the prompts to configure your project. Set the type to "laravel" and specify the project name.

3. **Start DDEV**:

ddev start

### 2. **Install Bedrock WordPress**

1. **Navigate to Your DDEV Directory**:

cd /path/to/your/ddev/project

2. **Create a Subdirectory for Bedrock**:

mkdir wpblog
   cd wpblog

3. **Install Bedrock Using Composer**:

composer create-project roots/bedrock .

### 3. **Configure DDEV for WordPress**

1. **Create a DDEV Configuration for WordPress**:
– In the `wpblog` directory, create a file named `ddev.config.yaml` with the following content:

webserver_type: nginx
   php_version: "8.1" # or your desired PHP version
   type: wordpress

2. **Add the WordPress Database Configuration**:
– Open the `wpblog/.env` file and configure the database settings:

DB_NAME=wordpress
   DB_USER=db
   DB_PASSWORD=db
   DB_HOST=db

3. **Set Up the Laravel `.env` File**:
– Ensure your Laravel `.env` file is correctly configured to connect to the database as well.

### 4. **Update Nginx Configuration for Subdirectory**

1. **Create a Custom Nginx Configuration**:
– In your Laravel project's `.ddev` directory, create or update the `nginx-site.conf` file to include the following:

location /wpblog {
       try_files $uri $uri/ /wpblog/index.php?$args;
   }

2. **Restart DDEV**:

ddev restart

### 5. **Access Your Sites**

– You should now be able to access your Laravel application at `http://.ddev.site` and your Bedrock WordPress installation at `http://.ddev.site/wpblog`.

### 6. **Database and Additional Configuration**

– Make sure to import any existing databases or set up new ones as needed.
– Configure WordPress settings through the admin panel at `http://.ddev.site/wpblog/wp-admin`.

### 7. **Final Steps**

– Test both applications to ensure they are running correctly.
– Adjust any further configurations as needed based on your specific requirements.

By following these steps, you should have your Laravel application running as the main site and the Bedrock WordPress installation accessible at `/wpblog`. Let me know if you need further assistance!

### 1. **Access DDEV Database**

First, you need to access the MySQL database within your DDEV environment:

ddev mysql

This command will log you into the MySQL shell as the `db` user, which is already configured in your DDEV setup.

### 2. **Create the Bedrock Database**

If you haven't created the `bedrock` database yet, you can create it with the following command inside the MySQL shell:

CREATE DATABASE bedrock;

### 3. **Grant Permissions to the `db` User**

Now, grant the `db` user permissions to access the `bedrock` database:

GRANT ALL PRIVILEGES ON bedrock.* TO 'db'@'%' IDENTIFIED BY 'db';

### 4. **Flush Privileges**

After granting the permissions, flush the privileges to ensure that the changes take effect:

FLUSH PRIVILEGES;

### 5. **Exit MySQL**

You can exit the MySQL shell by typing:

EXIT;

### 6. **Update Your Bedrock `.env` File**

Make sure your Bedrock `.env` file is set up to connect to the `bedrock` database using the `db` user. Update the following lines in your `.env` file located in the `wpblog` directory:

DB_NAME=bedrock
DB_USER=db
DB_PASSWORD=db
DB_HOST=db

### 7. **Restart DDEV**

Restart DDEV to ensure all configurations are applied:

ddev restart

### Conclusion

Now the `db` user has access to the `bedrock` database, and you should be able to proceed with your WordPress setup using Bedrock without issues. Let me know if you need any further assistance!

### 1. **Open Your Terminal**

Launch your terminal or command prompt.

### 2. **Navigate to the Directory with Your PEM File**

Use the `cd` command to navigate to the directory where your PEM file is located. For example:

cd D:aws

### 3. **Set the Correct Permissions for the PEM File (Linux/Mac)**

If you're using Linux or Mac, ensure that the PEM file has the correct permissions. You can set the permissions with the following command:

chmod 400 your-key-file.pem

### 4. **Connect to Your EC2 Instance**

Use the `ssh` command to connect to your EC2 instance. The command format is:

ssh -i /path/to/your-key-file.pem ec2-user@your-instance-public-dns

Replace the placeholders with your specific details:

– **`/path/to/your-key-file.pem`**: The path to your PEM file.
– **`ec2-user`**: The default username for Amazon Linux instances. Use `ubuntu` for Ubuntu instances.
– **`your-instance-public-dns`**: The public DNS or IP address of your EC2 instance. This can be found in the AWS Management Console under the EC2 instance details.

For example, if your PEM file is `k.pem` and your instance's public DNS is `ec2-16-170-254-93.eu-north-1.compute.amazonaws.com`, the command would look like this:

ssh -i D:awsk.pem ubuntu@ec2-16-170-254-93.eu-north-1.compute.amazonaws.com

### 5. **Accept the Host Key**

If this is your first time connecting to the instance, you may receive a prompt asking you to confirm the host key. Type `yes` to continue.

### 6. **You Are Now Connected**

Once connected, you will have command-line access to your EC2 instance.

### Troubleshooting

– **Permission Denied**: Ensure that the PEM file has the correct permissions (only readable by you).
– **Connection Timeout**: Check your security group settings in the AWS console to ensure that inbound SSH traffic (port 22) is allowed from your IP address.

Let me know if you need further assistance!

### 1. **Ensure Correct Permissions for the PEM File**

Even though you set the permissions using `chmod 400`, WSL sometimes has issues with file permissions. To ensure the permissions are set correctly:

1. Open your WSL terminal and navigate to the directory containing your PEM file.

cd /mnt/d/AWS-instance-projects

2. Check the permissions of the PEM file:

ls -l openeratech.pem

You should see something like this:

-r-------- 1 root root 1692 Feb 1 12:34 openeratech.pem

If it shows more than just read permissions for the owner, you can run the following command to set them:

chmod 400 openeratech.pem

### 2. **Use the Correct Username**

Ensure you are using the correct username for your EC2 instance. Here are some common usernames based on the AMI:

– **Amazon Linux**: `ec2-user`
– **Ubuntu**: `ubuntu`
– **CentOS**: `centos`
– **Debian**: `admin` or `root`

In your command, you are using `ubuntu`, which is correct for Ubuntu instances.

### 3. **Verify Your EC2 Security Group Settings**

Make sure that your EC2 instance's security group is configured to allow inbound SSH connections (port 22) from your current IP address:

1. Go to the **AWS Management Console**.
2. Navigate to the **EC2 Dashboard**.
3. Select your instance and click on the **Security** tab.
4. Click on the **Security Group** link.
5. Ensure there's a rule allowing inbound traffic on port 22 from your IP address (or `0.0.0.0/0` for all, but it's not recommended for security reasons).

### 4. **Check the Public DNS**

Make sure you are using the correct public DNS or IP address of your EC2 instance. You can find it in the **EC2 Management Console** under your instance details.

### 5. **Try Specifying the User with the IP Address**

Sometimes explicitly specifying the user along with the public IP address can help. Try the following command:

ssh -i "openeratech.pem" ubuntu@51.20.60.238

### 6. **Check for Multiple SSH Keys**

If you have multiple SSH keys on your system, ensure that the one you are using corresponds to the key pair associated with your EC2 instance. You can specify the key explicitly in your SSH command.

### 7. **Reboot the Instance**

As a last resort, if none of the above steps work, you might try rebooting the EC2 instance.

### Conclusion

If you've followed these steps and still encounter issues, please share any error messages you receive, and I'll be happy to assist you further!

### Steps to Fix the Permissions

1. **Change the Permissions of the PEM File**:
In your WSL terminal, run the following command to set the correct permissions:

chmod 400 /mnt/d/AWS-instance-projects/openeratech.pem

2. **Verify the Permissions Again**:
After changing the permissions, verify them to ensure they are set correctly:

ls -l /mnt/d/AWS-instance-projects/openeratech.pem

You should see something like this:

-r-------- 1 neerajubuntu neerajubuntu 1678 Feb  1 08:59 openeratech.pem

3. **Connect to Your EC2 Instance Again**:
Now, try connecting to your EC2 instance again using the SSH command:

ssh -i /mnt/d/AWS-instance-projects/openeratech.pem ubuntu@ec2-51-20-60-238.eu-north-1.compute.amazonaws.com

### Additional Considerations

– **File Ownership**: Ensure that the file is owned by your user. You can check this with the `ls -l` command. If the ownership is incorrect, you can change it using:

chown $USER:$USER /mnt/d/AWS-instance-projects/openeratech.pem

– **Use the Correct User**: Make sure you are using the correct username (`ubuntu` for Ubuntu AMIs) in your SSH command.

### Conclusion

After setting the correct permissions, you should be able to connect to your EC2 instance without encountering the "Permission denied (publickey)" error. If you still have issues, please let me know!