Join the Open Source Pledge

The Open Source Pledge is a group of companies with a shared commitment to paying the maintainers of the Open Source software.

The pledge aims to establish a new social norm in the tech industry of companies paying Open-Source maintainers so that burnout and related security issues, such as those in XZ and Apache Log4j, can become a thing of the past.

Every modern business—whether they know it or not—relies on Open Source software, yet few give back. The PHP Foundation celebrates the #OpenSourcePledge, whose members have committed to correcting this imbalance. Together, we can build a stronger, more resilient OSS ecosystem. 🌱 -- The PHP Foundation

Companies that have already signed up include Laravel, Sentry, Private Packagist, and more. You can see a full list on their members page.

If you are a company that would like to join, they ask you to pay $2,000 per year per developer at your company. Then, self-report annually with a blog post outlining your payments to maintainers.

For more information about the pledge, visit the Open Source Pledge site.

The post Join the Open Source Pledge appeared first on Laravel News.

Join the Laravel Newsletter to get all the latest Laravel articles like this directly in your inbox.

Read more https://laravel-news.com/open-source-pledge

Details

Category: Dev News

Prism is an AI Package for Laravel

Prism is a powerful Laravel package for integrating Large Language Models (LLMs) into your applications. Using Prism, you can easily use different AI providers using the package's driver pattern, which gives you a unified interface to work with popular AI providers out of the box. Prism has three built-in providers available at the time of writing—Anthropic, Open AI, and Ollama—with the ability to create custom drivers:

// Anthropic
$prism = Prism::text()
    ->using('anthropic', 'claude-3-5-sonnet-20240620')
    ->withSystemPrompt(view('prompts.nyx'))
    ->withPrompt('Explain quantum computing to a 5-year-old.');

$response = $prism();

echo $response->text;

// Open AI
$prism = Prism::text()
    ->using('openai', 'gpt-4o')
    ->withSystemPrompt(view('prompts.nyx'))
    ->withPrompt('Explain quantum computing to a 5-year-old.');

// Ollama
$prism = Prism::text()
    ->using('ollama', 'qwen2.5:14b')
    ->withSystemPrompt(view('prompts.nyx'))
    ->withPrompt('Explain quantum computing to a 5-year-old.');

Main Features

• Elegant Provider Integrations - Seamlessly switch between AI providers like OpenAI, Anthropic, and Ollama with a clean, expressive syntax you'll love.
• Fluent Text Generation API - Craft AI-powered text with an intuitive, chainable API that feels right at home in your Laravel projects.
• Seamless Tool Integration - Empower your AI with custom tools and external APIs, extending its capabilities with Laravel-like simplicity.
• Prism Server - use tools like ChatGPT web UIs or any OpenAI SDK to interact with your custom Prism models.
• Seamless integration with Laravel's ecosystem
• Built-in support for AI-powered tools and function calling
• Flexible configuration options to fine-tune your AI interactions

You can learn more about this package and get full installation instructions in the official Prism documentation. The source code is available on GitHub at echolabsdev/prism.

The post Prism is an AI Package for Laravel appeared first on Laravel News.

Join the Laravel Newsletter to get all the latest Laravel articles like this directly in your inbox.

Read more https://laravel-news.com/prism-ai-laravel

Details

Category: Dev News

Composer Package Executor (CPX) - bring NPX to Composer

Tired of managing different development tools across projects? cpx (Composer Package Executor) is a handy tool developed by Liam Hammett that simplifies your workflow. Similar to npx for npm, cpx allows you to run any command from a Composer package, even if it's not installed in your project.

Say goodbye to version conflicts and installation hassles. cpx takes care of package installations and updates behind the scenes, letting you focus on what matters - coding. This ensures consistency across your projects, whether you're working solo or collaborating in a team.

To install cpx you do so using composer:

composer global require cpx/cpx

Then, you execute any composer package by doing:

cpx vendor/package <command>

For example:

cpx laravel/installer new
 
# Or, for popular packages, you can use the command's alias directly
 
cpx laravel new

If you switch between numerous projects, they may use different tooling and so cpx will help to normalize your workflow by providing commands that actually detect what tools your project is using and uses the correct one for you. Are you working on a project that uses Pests for testing? No problem! cpx automatically detects your project's testing framework (including PHPUnit or Codeception) and runs the appropriate tests with cpx test. Similar logic applies to static analysis with cpx check, which detects PHPStan, Psalm, or Phan, and code formatting with cpx format, which works with PHP-CS-Fixer, Laravel Pint, or PHPCBF.

cpx also integrates nicely with Laravel and so your app will be bootstrapped so you can use any Laravel service.

Learn more about this tool at cpx.dev and view the source code on GitHub.

The post Composer Package Executor (CPX) - bring NPX to Composer appeared first on Laravel News.

Join the Laravel Newsletter to get all the latest Laravel articles like this directly in your inbox.

Read more https://laravel-news.com/cpx

Details

Category: Dev News

Optimize Your SQLite Database with the Laravel Optimize DB Package

The Laravel Optimize DB package provides a good starting point for production-ready SQLite databases. Pest creator and core Laravel team member Nuno Maduro created this package.

This package is meant for SQLite (3.46+) in a Laravel project and works by applying migration to your project and runtime configuration applied via the package's service provider. It applies the following settings at the time of writing:

 ┌───────────────────────────┬─────────────┬───────────┐
 │ Setting                   │ Value       │ Via       │
 ├───────────────────────────┼─────────────┼───────────┤
 │ PRAGMA auto_vacuum        │ incremental │ Migration │
 │ PRAGMA journal_mode       │ WAL         │ Migration │
 │ PRAGMA page_size          │ 32768       │ Migration │
 │ PRAGMA busy_timeout       │ 5000        │ Runtime   │
 │ PRAGMA cache_size         │ -20000      │ Runtime   │
 │ PRAGMA foreign_keys       │ ON          │ Runtime   │
 │ PRAGMA incremental_vacuum │ (enabled)   │ Runtime   │
 │ PRAGMA mmap_size          │ 2147483648  │ Runtime   │
 │ PRAGMA temp_store         │ MEMORY      │ Runtime   │
 │ PRAGMA synchronous        │ NORMAL      │ Runtime   │
 └───────────────────────────┴─────────────┴───────────┘

High Impact Settings

I won't cover each setting, but the following three settings could potentially have a highly positive impact on SQLite performance.

journal_mode = WAL:

• Why it’s beneficial: Write-Ahead Logging (WAL) is one of the most effective ways to improve concurrency and performance in SQLite, especially for applications that need to support multiple readers and writers. It allows the database to handle many reads simultaneously while still maintaining atomicity and durability for writes.
• Use case: Great for databases with mixed read/write workloads and high concurrency requirements.

⠀cache_size = -20000 (20 MB cache):

• Why it’s beneficial: Increasing the cache size helps store more pages in memory, reducing the need for disk I/O. This is especially useful for databases that are read frequently or have hot data. A larger cache means fewer page reads from disk, resulting in faster query responses.
• Use case: Important when dealing with large datasets and you have sufficient memory resources available.

⠀mmap_size = 2147483648 (2 GB memory mapping):

• Why it’s beneficial: Memory-mapping the database file can dramatically improve performance by reducing the overhead associated with file system operations. It allows the database to access data directly in memory, bypassing the need for repeated system calls to read or write data.
• Use case: Very beneficial for large databases on systems with ample memory, where file access speed is a priority.

The package is considered a work-in-progress, so use it carefully. The package advises not to use it in production yet and to back up your database before requiring it. You can learn more about this package and view the source code on Github.

The post Optimize Your SQLite Database with the Laravel Optimize DB Package appeared first on Laravel News.

Join the Laravel Newsletter to get all the latest Laravel articles like this directly in your inbox.

Read more https://laravel-news.com/optimize-db-for-laravel-sqlite

Details

Category: Dev News