Ground zero 2 cloud nine: May 2024

Thursday, May 30, 2024

MERGING MULTIPLE SPF RECORDS FOR YOUR GODADDY DOMAIN

If you have multiple SPF records, delete them to avoid conflicts.Add a single SPF record with the combined directives:

Eg:
1.  v=spf1 include:_spf.elasticemail.com include:spf.protection.outlook.com -all

2. v=spf1 include:_spf.mlsend.com include:_spf.mlsend.com include:_spf.elasticemail.com include:spf.protection.outlook.com -all

Combined

 v=spf1 include:_spf.elasticemail.com include:spf.protection.outlook.com include:_spf.mlsend.com -all

Save Changes:
- Save the changes to your DNS records.

Verify the SPF Record

After updating the SPF record, verify that it has been correctly applied:

Use MXToolbox SPF Lookup https://mxtoolbox.com/SuperTool.aspx to check the SPF record for your domain.
Ensure that the record includes all necessary includes (_spf.elasticemail.com, spf.protection.outlook.com, _spf.mlsend.com).

Tuesday, May 28, 2024

Adding Meta Tags

Steps to Implement

Edit your HTML file: Open your HTML document in your preferred text editor.
Insert meta tags: Add the meta tags within the <head> section as shown in the example above.
Save the changes: After adding the meta tags, save the file.
Upload your file: If your website is hosted, upload the updated HTML file to your web server.

Validation

After adding meta tags, you can validate your HTML to ensure there are no errors. You can use the W3C Markup Validation Service https://validator.w3.org/ to check your HTML.

How to check if code is changed from LUMEN to LARAVEL

Here are some ways to check your code after your team migrated it from Lumen to Laravel:

General checks:

Project Structure:
- Verify the Laravel directory structure. Laravel has a specific directory layout with folders like app, config, resources, etc. Ensure these folders exist and contain the expected files.
Configuration:
- Check the composer.json file to see if Laravel dependencies are installed.
- Review the config directory. Key Laravel configuration files like app.php, database.php, etc. should be present and configured correctly.
Autoloading:
- Ensure the autoload section in composer.json reflects the Laravel PSR-4 autoloading structure.
Routing:
- Look for the routes directory. Laravel uses routes defined in this directory for handling requests. Ensure routes are migrated properly from Lumen.
Controllers:
- Verify that controllers are located in the app/Http/Controllers directory (default Laravel location) and use Laravel controller features like dependency injection and middleware.

Framework-specific checks:

Lumen-specific code: Identify and remove any Lumen-specific code that is no longer relevant in Laravel. This could include custom service providers, facades, or helper functions.
Laravel features: Look for usage of new Laravel features like middleware, Eloquent ORM, or service providers that may have replaced Lumen functionality.

Testing:

Unit Tests: Run any existing unit tests to ensure core functionalities still work after the migration.
Manual Testing: Manually test critical functionalities of your application to identify any regressions introduced during the migration.

Additional resources:

Laravel Documentation: The Laravel documentation provides a good starting point for understanding the framework and its features: https://laravel.com/docs/11.x/installation
Upgrade Guide: If your team migrated from a specific Lumen version, there might be an official upgrade guide from Laravel that details specific migration steps: https://laravel.com/docs/9.x/upgrade

By following these steps and referencing the resources, you can gain a good understanding of the changes made during the migration and identify any potential issues. Remember, the specific checks will depend on the complexity of your application and the extent of the migration.

Thursday, May 9, 2024

Edit PDF

Edit PDF using https://www.sejda.com/pdf-editor?

Edit PDF META DATA https://pdfcandy.com/