How to Get PostgreSQL Version Using SQL Query

~ tadmin

When working with PostgreSQL, it’s often necessary to check the version of the database server to ensure compatibility with features, extensions, and security updates. Here’s a quick guide on how to retrieve the PostgreSQL version using SQL queries.

Using version() Function

The simplest way to get detailed PostgreSQL version information is by running the following SQL query:

SELECT version();

This will return a string containing the PostgreSQL version along with additional system details. For example:

PostgreSQL 15.2 (Ubuntu 15.2-1.pgdg22.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, 64-bit

Using SHOW server_version

If you only need the numeric version of PostgreSQL (without extra system details), you can use:

SHOW server_version;

This will return a cleaner output, such as:

15.2

Why Knowing the PostgreSQL Version Matters

  • Feature Compatibility: Some features are only available in specific PostgreSQL versions.
  • Performance Improvements: PostgreSQL frequently enhances performance and query optimization.
  • Security Updates: Keeping your database up-to-date ensures security patches are applied.

By using these simple queries, you can quickly determine the PostgreSQL version and ensure your database environment is up-to-date and compatible with your applications.

Do you find this helpful? Follow our community for more PostgreSQL and database-related tips!

Changing Domain from rndpwd.info to rndpwd.shkodenko.com

Random Password Generator
~ tadmin

We are excited to announce that our service, previously accessible at https://rndpwd.info, has now moved to a new domain: https://rndpwd.shkodenko.com.

Why the Change?

This transition allows us to integrate our service under a unified domain, making it easier to manage and ensuring better branding consistency. All functionalities remain the same, and we are committed to providing the same level of security and performance as before.

What You Need to Do

If you have been using https://rndpwd.info, simply update your bookmarks and any API integrations to point to https://rndpwd.shkodenko.com.

Redirects and Support

To ensure a smooth transition, we have implemented automatic redirects from the old domain. However, if you encounter any issues, feel free to reach out.

Thank you for your continued support!

Any comments, donations and support for us is very welcomed. 😊

Extracting and Using an RSA Public Key for JWT Verification in Laravel

~ tadmin

Introduction

When working with JWT authentication in Laravel, you may encounter the error:

openssl_verify(): Supplied key param cannot be coerced into a public key

This typically happens when verifying an RS256-signed JWT with an incorrect or improperly formatted public key. In this guide, we’ll walk through the steps to extract and use the correct RSA public key for JWT verification.

Understanding the Issue

JWT Header Inspection

Before solving the issue, inspect the JWT header to determine the signing algorithm:

echo "YOUR_JWT_TOKEN_HERE" | cut -d "." -f1 | base64 --decode

If you see something like this:

{
  "alg": "RS256",
  "kid": "public:01fa2927-9677-42bb-9233-fa8f68f261fc"
}
  • "alg": "RS256" means the token is signed using RSA encryption, requiring a public key for verification.
  • "kid" (Key ID) helps locate the correct public key.

Finding the JWKS (JSON Web Key Set) URL

Public keys for JWT verification are often stored in a JWKS endpoint. If your JWT includes an iss (issuer) field like:

"iss": "https://id-int-hydra.dev.local/"

Try accessing the JWKS URL:

https://id-int-hydra.dev.local/.well-known/jwks.json

Use this command to retrieve the public key information:

curl -s https://id-int-hydra.dev.local/.well-known/jwks.json | jq

Extracting the RSA Public Key from JWKS

If the JWKS response contains:

{
  "keys": [
    {
      "kid": "public:01fa2927-9677-42bb-9233-fa8f68f261fc",
      "kty": "RSA",
      "alg": "RS256",
      "n": "base64url-encoded-key",
      "e": "AQAB"
    }
  ]
}

You need to convert the n and e values to PEM format.

Python Script to Convert JWKS to PEM

Create a script (convert_jwks_to_pem.py) with the following code:

import json
import base64
from cryptography.hazmat.primitives.asymmetric import rsa
from cryptography.hazmat.primitives import serialization
from cryptography.hazmat.backends import default_backend

# Example JWKS response
jwks = {
  "keys": [
    {
      "kid": "public:01fa2927-9677-42bb-9233-fa8f68f261fc",
      "kty": "RSA",
      "alg": "RS256",
      "n": "base64url_encoded_n_value",
      "e": "AQAB"
    }
  ]
}

def base64url_decode(input):
    input += '=' * (4 - (len(input) % 4))  # Pad correctly
    return base64.urlsafe_b64decode(input)

key = jwks["keys"][0]
modulus = int.from_bytes(base64url_decode(key["n"]), byteorder='big')
exponent = int.from_bytes(base64url_decode(key["e"]), byteorder='big')

public_key = rsa.RSAPublicNumbers(exponent, modulus).public_key(default_backend())

pem = public_key.public_bytes(
    encoding=serialization.Encoding.PEM,
    format=serialization.PublicFormat.SubjectPublicKeyInfo
)

print(pem.decode())

Run the script to generate a valid RSA public key in PEM format:

python convert_jwks_to_pem.py > public_key.pem

Verifying the Public Key

To confirm the validity of the generated public key, run:

openssl rsa -in public_key.pem -pubin -text

If successful, you should see details about the RSA key structure.

Using the Public Key in Laravel

1️⃣ Store the Public Key in .env

JWT_PUBLIC_KEY="-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqh...
-----END PUBLIC KEY-----"

2️⃣ Update Laravel Configuration (config/auth.php)

'jwt_public_key' => env('JWT_PUBLIC_KEY'),

3️⃣ Modify JWT Verification in Laravel

Modify your controller to load the correct key:

use Firebase\JWT\JWT;
use Firebase\JWT\Key;

$publicKey = config('auth.jwt_public_key');
$decoded = JWT::decode($token, new Key($publicKey, 'RS256'));

Conclusion

By following these steps, you can successfully extract, verify, and use an RSA public key for JWT authentication in Laravel. This ensures secure and correct token verification in your application.

Let me know in the comments if you have any questions or need further clarification! 🚀

Linux find: Find Files in a Folder That Changed Today

~ tadmin

Linux find: Find Files in a Folder That Changed Today

The find command in Linux is a powerful tool for searching files and directories based on various criteria, including modification time. If you need to find files in a specific folder that were modified today, you can use the -mtime option.

Basic Command

To list all files in a directory that were modified within the last 24 hours, run:

find /path/to/search -mtime -1

How It Works

  • find – The command used to search for files and directories.
  • /path/to/search – Replace this with the directory where you want to perform the search.
  • -mtime -1 – Finds files modified within the last 24 hours.

Understanding -mtime Values

  • -mtime 0 → Finds files modified today (since the last midnight).
  • -mtime -1 → Finds files modified in the last 24 hours.
  • -mtime +1 → Finds files modified more than a day ago.

Include Subdirectories

By default, find searches recursively within all subdirectories. If you want to restrict the search to the current folder only, use:

find /path/to/search -maxdepth 1 -mtime -1

Filtering by File Type

To find only files (excluding directories):

find /path/to/search -type f -mtime -1

To find only directories:

find /path/to/search -type d -mtime -1

Sorting Results

If you want to sort the results by modification time (newest first), you can combine find with ls:

find /path/to/search -mtime -1 -type f -exec ls -lt {} +

Finding Files Modified in the Last X Hours

If you need more precision (e.g., finding files modified within the last 6 hours), use the -mmin option:

find /path/to/search -mmin -360

(360 minutes = 6 hours)

Executing a Command on Found Files

To delete files modified within the last 24 hours, use:

find /path/to/search -mtime -1 -type f -delete

⚠️ Be careful with -delete—there is no undo!

Alternatively, to compress the found files:

find /path/to/search -mtime -1 -type f -exec tar -czf modified_today.tar.gz {} +

Conclusion

The find command is an essential tool for system administrators and developers who need to locate and manage recently modified files efficiently. Whether you’re looking for logs, recent uploads, or system changes, these techniques will help streamline your workflow.

Would you like me to add a troubleshooting section or more examples? 🚀

Analyze Laravel code for upgrading PostgreSQL database version

~ tadmin

Checking PHP Code and Laravel Migrations for PostgreSQL database version upgrade from 14 to 17 Compatibility

Upgrading your PostgreSQL database from version 14 to 17 is an excellent way to take advantage of new features and performance improvements. However, ensuring that your Laravel application’s PHP code and migrations are compatible with both versions is critical to a smooth upgrade process. This guide provides actionable steps and tools to help you analyze your codebase and detect potential compatibility issues.

1. PHPStan with Laravel Support

PHPStan is a powerful static analysis tool that can detect potential issues in your PHP code, including database-related code. To check your Laravel migrations and queries:

  1. Install PHPStan with the Laravel extension: 
    composer require nunomaduro/larastan --dev
  2. Configure phpstan.neon: 
    includes:
 - ./vendor/nunomaduro/larastan/extension.neon

parameters:
 level: max
 paths:
   - app/
   - database/
  3. Run PHPStan to analyze your code: 
    vendor/bin/phpstan analyse

This will highlight any potential issues, including database query problems, ensuring your code is robust across PostgreSQL versions.

2. Laravel IDE Helper

Laravel’s Query Builder and Eloquent ORM can obscure query generation. Install the Laravel IDE Helper to make static analysis tools more effective:

composer require --dev barryvdh/laravel-ide-helper
php artisan ide-helper:generate

This enhances tools like PHPStan by improving type hints and making it easier to catch potential query-related issues.

3. Database Query Validation with PHPUnit

Write tests to validate your database queries and migrations. PHPUnit allows you to simulate queries against your database and ensure compatibility. For example:

public function testQueryCompatibility()
{
    $result = DB::select('SELECT current_setting(\'server_version\')');
    $this->assertNotEmpty($result);
}

Run these tests in environments with PostgreSQL 14 and 17 to catch any incompatibilities.

4. SQL Compatibility Linter

For raw SQL queries in your migrations or code, use a PostgreSQL linter or validate directly against both database versions:

  1. Dump queries with Laravel’s migration pretend mode: 
    php artisan migrate:status --pretend > queries.sql
  2. Test the SQL against both versions: 
    psql -h localhost -d your_database -f queries.sql
  3. Use PostgreSQL’s EXPLAIN or EXPLAIN ANALYZE to check for performance issues or changes in query plans.

5. Laravel Pint

Use Laravel Pint to enforce clean coding standards in your migrations and database-related code:

composer require laravel/pint --dev
vendor/bin/pint

While Pint doesn’t directly check PostgreSQL compatibility, it ensures your code is clean and easier to review for potential issues.

6. Extensions and Modules Compatibility

If your application relies on PostgreSQL extensions like PostGIS, pg_trgm, or uuid-ossp, ensure they’re compatible with version 17. Run the following query to list installed extensions:

SELECT * FROM pg_available_extensions WHERE installed_version IS NOT NULL;

Check for updates or compatibility notes for each extension.

7. Custom PostgreSQL Checker Script

For custom raw SQL queries, test them explicitly against PostgreSQL 14 and 17:

php artisan migrate:status --pretend

Take the output and run it manually in both environments to ensure compatibility.

8. Database Compatibility Tools

Use PostgreSQL’s built-in tools to check schema compatibility:

  • Export your schema: 
    pg_dump -s -h localhost -U your_user your_database > schema.sql
  • Test it against PostgreSQL 17: 
    psql -d your_test_database -f schema.sql

9. Manual Query Validation

If you’re using raw SQL, validate specific queries manually:

  1. Check for deprecated data types: 
    SELECT table_name, column_name, data_type
FROM information_schema.columns
WHERE data_type IN ('unknown', 'abstime', 'reltime', 'tinterval');
  2. Check for invalid object dependencies: 
    SELECT conname, conrelid::regclass AS table_name
FROM pg_constraint
WHERE convalidated = false;

10. Test in a Staging Environment

Finally, deploy your Laravel application to a staging environment with PostgreSQL 17. Run comprehensive tests to ensure all queries, migrations, and application functionality work as expected.

Summary

To ensure your Laravel application’s PHP code and migrations are compatible with PostgreSQL 14 and 17:

  1. Use PHPStan with Laravel extensions for static analysis.
  2. Write PHPUnit tests to validate queries and migrations.
  3. Validate raw SQL using PostgreSQL’s tools.
  4. Test extensions and modules for compatibility.
  5. Deploy to a staging environment with PostgreSQL 17 for end-to-end testing.

By following these steps, you can confidently upgrade your PostgreSQL database and keep your Laravel application running smoothly.

Let me know your thoughts or if you have additional questions about any of these steps in the comments box below the post!

Linux tail Command: How to Display and Track the Last Part of a File

~ tadmin

Linux tail Command: How to Display and Track the Last Part of a File

The tail command in Linux is a powerful utility that allows users to display the last part (or “tail”) of a file. It’s especially useful for monitoring log files or examining large files where only the most recent data is of interest.

In this article, we’ll explore some of the most common and practical ways to use the tail command, with tips to make the most of its features.

Basic Usage of the tail Command

By default, the tail command shows the last 10 lines of a file. To customize how many lines are displayed, you can use the -n option.

For example, to display the last 55 lines of the file /var/log/messages, you can use the following command:

$ tail -n 55 /var/log/messages

Monitoring File Changes in Real Time

One of the most powerful features of tail is the ability to track file updates in real time using the -f option. This is particularly useful when monitoring log files for changes.

For example:

$ tail -n 55 -f /var/log/messages

This command shows the last 55 lines of the file /var/log/messages and keeps the terminal open, displaying any new lines added to the file as they appear. This is invaluable when debugging or keeping an eye on system events.

Combining tail with Other Utilities

The tail command becomes even more versatile when combined with other Linux tools. Here are some common use cases:

1. Viewing Long Outputs with more

If you need to view a large number of lines and prefer scrolling through them interactively, you can pipe the output of tail to the more command:

$ tail -n 255 -f /var/log/messages | more

This command displays the last 255 lines of /var/log/messages and allows you to navigate through the output page by page.

2. Filtering Output with grep

To focus on specific information in a file, you can combine tail with grep to filter lines based on keywords. For instance, if you’re interested in logs related to the named service, use the following:

$ tail -n 55 -f /var/log/messages | grep "named"

This will display and track only the lines containing the word “named” from the last 55 lines of the log file, along with any new matching entries that appear.

Practical Tips for Using tail

  1. Debugging Made Easy: Use tail -f to monitor live logs during software deployments or server debugging.
  2. Optimizing System Monitoring: Combine tail with utilities like grep or awk to isolate and analyze critical log data.
  3. Check Permissions: Ensure you have the necessary read permissions for the file you’re trying to access with tail.

Conclusion

The tail command is an essential tool for Linux users, providing an efficient way to access the most recent data in a file, monitor changes in real time, and filter information for specific use cases. Whether you’re debugging an issue, analyzing logs, or just exploring system behavior, mastering tail and its options can significantly enhance your productivity.

Do you use tail in your daily work? Let us know your favorite tips or tricks in the comments below!

Filtering Requests by Status Code 498 in Graylog

~ tadmin

Filtering Requests by Status Code 498 in Graylog

Graylog is a powerful tool for log management and analysis, widely used by IT professionals to monitor and troubleshoot their systems. One common task is filtering logs by specific HTTP status codes to identify and address issues. In this post, we’ll walk you through the steps to filter requests with status code 498 in Graylog.

Why Filter by Status Code 498?

HTTP status code 498 indicates an invalid token. This can be particularly useful to monitor in environments where token-based authentication is used, as it helps identify potential issues with token validation.

Steps to Filter by Status Code 498

  1. Log in to Graylog: Start by logging into your Graylog instance with your credentials.

  2. Navigate to the Search Page: Once logged in, head to the search bar at the top of the page.

  3. Enter the Query: To filter logs by status code 498, enter the following query in the search bar:

    http_status_code:498

    This query tells Graylog to display only the log entries where the HTTP status code is 498.

  4. Execute the Search: Press Enter or click the search icon to run the query. Graylog will then display all the relevant log entries.

  5. Save the Search: If you find yourself frequently needing to filter by this status code, you can save the search for future use. Click the "Save" button, give your search a name, and it will be available for quick access next time.

Advanced Filtering and Automation

For more advanced filtering or to automate this process, you can use Graylog’s REST API. This allows you to create custom queries and integrate them into your scripts or monitoring tools, providing a more streamlined workflow.

Conclusion

Filtering by specific status codes in Graylog is a straightforward process that can greatly enhance your ability to monitor and troubleshoot your systems. By following the steps outlined above, you can quickly and easily filter requests with status code 498, helping you maintain a secure and efficient environment.

How to Undo a Commit, Pull Remote Changes, and Reapply Your Work in Git

Git
~ tadmin

How to Undo a Commit, Pull Remote Changes, and Reapply Your Work in Git

When working with Git, it’s common to encounter situations where you’ve made a local commit, but later realize you need to pull changes from the remote repository before reapplying your work. Here’s a step-by-step guide to achieve this smoothly.

Step 1: Undo the Last Local Commit

To undo the last local commit without losing your changes, use:

git reset --soft HEAD~1

This command undoes the last commit but keeps your changes staged for the next commit.

If you want to completely undo the commit and unstage the changes, use:

git reset HEAD~1

For cases where you want to discard the changes altogether:

git reset --hard HEAD~1

Warning: Using --hard will delete your changes permanently.

Step 2: Check Remote Origins

To see the configured remotes:

git remote -v

Ensure you know the correct remote you want to pull from (e.g., origin). If you have multiple remotes, double-check which one is appropriate for your changes.

Step 3: Pull Changes from the Remote

To pull the latest changes from the correct remote and branch, run:

git pull <remote-name> <branch-name>

For example, if your remote is origin and the branch is main, use:

git pull origin main

If there are conflicts, Git will prompt you to resolve them manually. After resolving conflicts, stage the resolved files:

git add <file>

Then continue the merge process:

git commit

Step 4: Reapply Your Commit

Once you’ve pulled the changes and resolved any conflicts, reapply your changes. Since your changes were unstaged in Step 1, you can stage them again:

git add .

And then create the commit:

git commit -m "Your commit message"

Optional: Confirm Remote Setup

To confirm which remotes and branches are configured, use:

git branch -r

If you want to verify the branch’s remote tracking setup, check:

git branch -vv

To push your changes to the intended remote, run:

git push <remote-name> <branch-name>

Troubleshooting Tips

  1. Check the state of your working directory: Run git status to see which files are staged, unstaged, or untracked.
  2. Verify branch tracking: Ensure you’re on the correct branch and that it’s tracking the expected remote.
  3. Resolve conflicts carefully: If conflicts arise during the pull, resolve them thoughtfully to avoid losing changes.

By following these steps, you can effectively manage your Git workflow, ensuring your local changes are synced with the remote repository while avoiding unnecessary headaches. This process is invaluable for collaborative environments where pulling and merging changes is a frequent requirement.

Do you have additional tips or a favorite Git trick? Share your thoughts and experiences in the comments!

Linux Screen Command: Manage Multiple Terminal Sessions Efficiently

~ tadmin

Linux Screen Command: Manage Multiple Terminal Sessions Efficiently

If you frequently work on Linux systems and need to manage multiple terminal sessions within a single window, the Linux Screen utility is an indispensable tool. In this guide, you’ll learn how to install and use Screen on popular Linux distributions like Ubuntu, Fedora, CentOS, and more. We’ll also explore essential commands to make your workflow smoother.

What Is the Linux Screen Command?

The Linux Screen utility is a terminal multiplexer that allows you to create, manage, and switch between multiple terminal sessions within a single window. It’s particularly useful for system administrators and developers who often run long-running processes or work on remote servers.

How to Install Screen on Linux

For RPM-Based Distributions (Fedora, CentOS, Red Hat):

To install Screen on RPM-based Linux distributions, use the yum package manager:

sudo yum install screen

For Debian-Based Distributions (Ubuntu):

For Ubuntu or other Debian-based systems, follow these steps:

sudo apt update  
sudo apt install screen

Essential Linux Screen Commands

Below is a list of common Screen commands to help you get started:

Basic Commands:

  • Start a Screen session: 
    screen -a
  • Create a named window: 
    screen -t <window_name>
  • Create a new window (shortcut): Press [ Ctrl + a + c ].
  • Delete a window (shortcut): Press [ Ctrl + d ].

Navigating Between Windows:

  • Switch to the last open window: Press [ Ctrl + a ].
  • Move to the next window: Press [ Ctrl + a + n ].
  • Move to the previous window: Press [ Ctrl + a + p ].

Detaching and Reattaching Sessions:

  • Detach from a session: Press [ Ctrl + a + d ].
  • Reattach a session: 
    screen -r
  • Reattach to a detached session: 
    screen -dr
  • Handle an “active session” error:
    If you see an error indicating the screen is already active, use:

    screen -x

Window Management Tips:

  • View a list of open windows: Press [ Ctrl + a + " ]. Navigate using arrow keys to select the desired window.
  • Rename a window: Press [ Ctrl + a + A ]. Enter a custom name for the window and press Enter to save.

These shortcuts make it easy to manage multiple sessions without losing track of your work.

Why Use Linux Screen?

The Screen command is invaluable for multitasking, especially when managing remote servers or running long processes. Its ability to keep terminal sessions alive even after disconnection ensures you never lose progress during unexpected interruptions.

Conclusion

Mastering the Linux Screen command can greatly enhance your productivity by enabling seamless multitasking in the terminal. Whether you’re a seasoned sysadmin or a Linux beginner, this tool is a must-have in your command-line arsenal.

Have you tried using the Screen command? Share your favorite tips and tricks in the comments below!

How to Compare Two Arrays from Files in PHP

~ tadmin

How to Compare Two Arrays from Files in PHP

Comparing arrays is a common task when dealing with datasets in PHP. Suppose you have two files containing lists of text values, and you want to find:

  1. Values present in both files.
  2. Values that exist only in the second file.

In this post, I’ll guide you through the steps to achieve this, complete with an easy-to-understand PHP script.

The Problem

Imagine you have two text files:

file1.txt

transactions, zone_sync_blockers, zone_versions, conditions, internal_conditions, conditions_from_regions, condition_properties, condition_versions, polygon_belonging_to_zone, zone_hierarchy, district_kinds, district_types, countries, geo_zones, area_types, zones, streets, divisions, polygons, regions, geo_zone_belonging_to_zone, features, features_changes, settlements, geo_zone_versions, postmachine_regions, storage_regions, division_regions, condition_groups, city_district_kinds

file2.txt

access_roles, packages, features, features_changes, condition_properties, zones, condition_groups, zone_hierarchy, district_kinds, reports, zone_versions, users, user_zone_permissions, geo_zone_versions, division_regions, condition_versions, conditions, notifications, individual_timetables, eu_reports, zone_sync_blockers, polygon_versions, settlements, area_types, city_district_kinds, conditions_from_regions, countries, hydra_access_tokens, spatial_ref_sys, en_reports, geo_zone_belonging_to_zone, geography_columns, geometry_columns, invalid_district_reports, divisions, postmachine_regions, storage_regions, district_types, failed_jobs, en_grouped_reports, geo_zones, internal_conditions, migrations, password_resets, eu_grouped_sender_aggregated_reports, eu_grouped_sender_detailed_reports, eu_grouped_recipient_detailed_reports, eu_grouped_recipient_aggregated_reports, personal_access_tokens, polygon_belonging_to_zone, additional_user_cities, polygons, positions, regions, streets, transactions

Your goal is to:

  • Identify which values are common between the two files.
  • Find values exclusive to the second file.

The Solution

Here’s a PHP script that compares the two arrays:

<?php
// Read the contents of the files into arrays
$file1 = file_get_contents('file1.txt');
$file2 = file_get_contents('file2.txt');

// Convert the comma-separated values into arrays
$array1 = array_map('trim', explode(',', $file1));
$array2 = array_map('trim', explode(',', $file2));

// Find common values (present in both arrays)
$commonValues = array_intersect($array1, $array2);

// Find values only in the second array
$onlyInSecondArray = array_diff($array2, $array1);

// Count the number of elements in each result
$countCommon = count($commonValues);
$countOnlyInSecond = count($onlyInSecondArray);

// Output the results
echo "Values present in both arrays (Count: $countCommon):\n";
echo implode(", ", $commonValues) . "\n\n";

echo "Values only in the second array (Count: $countOnlyInSecond):\n";
echo implode(", ", $onlyInSecondArray) . "\n";

How It Works

  1. Reading Files: The script uses file_get_contents() to read the contents of file1.txt and file2.txt.
  2. Converting to Arrays: The explode() function splits the text into arrays, and array_map('trim', ...) removes any extra whitespace.
  3. Finding Common and Exclusive Values:
    • array_intersect() identifies the common values.
    • array_diff() identifies values that exist in the second array but not in the first.
  4. Counting Elements: The count() function calculates the number of elements in each result.
  5. Output: The results, along with their counts, are displayed on the screen.

Example Output

For the provided files, running the script produces:

Values present in both arrays (Count: 28):
transactions, zone_sync_blockers, zone_versions, conditions, internal_conditions, conditions_from_regions, condition_properties, condition_versions, polygon_belonging_to_zone, zone_hierarchy, district_kinds, district_types, countries, geo_zones, area_types, zones, streets, divisions, polygons, regions, geo_zone_belonging_to_zone, features, features_changes, settlements, geo_zone_versions, postmachine_regions, storage_regions, division_regions, condition_groups, city_district_kinds

Values only in the second array (Count: 37):
access_roles, packages, reports, users, user_zone_permissions, notifications, individual_timetables, eu_reports, polygon_versions, hydra_access_tokens, spatial_ref_sys, en_reports, geography_columns, geometry_columns, invalid_district_reports, failed_jobs, en_grouped_reports, migrations, password_resets, eu_grouped_sender_aggregated_reports, eu_grouped_sender_detailed_reports, eu_grouped_recipient_detailed_reports, eu_grouped_recipient_aggregated_reports, personal_access_tokens, additional_user_cities, positions

Conclusion

This script is a handy way to compare datasets in PHP, especially when working with files. By leveraging PHP’s built-in array functions, you can efficiently process and analyze data.

Feel free to modify the script to suit your needs, and don’t forget to share your thoughts or enhancements in the comments below!

Happy coding!