SSH Host Key Change Warning

Here's how you can safely address this:

### 1. **Verify the Change**
– **Contact the server administrator** to verify whether the SSH key for `35.236.219.140` was changed intentionally.
– If you're the administrator, confirm that the server's host key change was legitimate.

### 2. **Remove the Offending Key**
– If the change is verified as legitimate, you can remove the old key from the `known_hosts` file and add the new one. You can do this by running the following command:

ssh-keygen -f "/home/admin1/.ssh/known_hosts" -R "[35.236.219.140]:63808"

This will remove the old key from the `known_hosts` file.

### 3. **Reconnect to the Server**
– After removing the old key, try connecting again using SSH:

ssh user@35.236.219.140 -p 63808

– The SSH client should prompt you to add the new host key to your `known_hosts` file. Verify the fingerprint carefully to ensure it matches the one provided by the administrator (or that you trust).

If the key matches, type `yes` to add it.

### 4. **Update Known Hosts**
– After accepting the new key, it will be added to your `~/.ssh/known_hosts` file, and the warning should no longer appear.

If you cannot verify the key change or suspect a security issue, **do not connect** until you can verify the server’s identity. It’s important to ensure that you're not falling victim to a man-in-the-middle attack.

Here’s the basic syntax and usage for adding a package with Composer:

### Syntax:

composer require vendor/package-name

Where:
– `vendor/package-name` is the name of the package you want to install.

### Example:
To install a package, like `guzzlehttp/guzzle`, for HTTP requests, you would run:

composer require guzzlehttp/guzzle

This command:
– Downloads the latest version of the package.
– Adds the package to the `composer.json` file under the `require` section.
– Installs the package into the `vendor` directory.

### Adding Specific Versions:
You can specify a version or version range for the package:

composer require guzzlehttp/guzzle:^7.0

This would install version 7.0 or higher of Guzzle, but less than version 8.0.

### Installing Dev Dependencies:
If you need to add a package only for development (e.g., testing libraries, debugging tools), you can use the `–dev` flag:

composer require --dev phpunit/phpunit

This will add the package to the `require-dev` section in your `composer.json`.

### Updating Dependencies After Adding:
After adding a package, Composer will automatically update your `composer.lock` file to reflect the new dependency, ensuring that the installed versions are locked.

### Optional Flags:
– `–no-scripts`: Skips running scripts defined in `composer.json`.
– `–prefer-dist`: Downloads the package as a .tar or .zip archive (useful for speed).
– `–dev`: Adds the package to the `require-dev` section.

Once you’ve added your package, you can use `composer install` to install all the dependencies (if you haven't already).

Let me know if you have a specific package in mind that you want to install!