Turso + Laravel

SQLite for Production. Powered by libSQL and libSQL Extension for PHP.

Turso · Quickstart · Examples · Docs · Discord · Blog & Tutorials

A LibSQL Driver for Laravel

LibSQL is a fork of SQLite and this package is #1 LibSQL Driver that run natively using LibSQL Native Extension/Driver/Whatever and support Laravel Ecosystem.

Requirement

Before using this package, you need to install and configure LibSQL Native Extension for PHP. You can download from LibSQL Extension - Release

1. Download based on you distribution (Linux/Macos/Darwin)
2. The archive is contains the extension and libsql_php_extension.stubs.php
3. Save the extension file in your desire directory
4. Save the libsql_php_extension.stubs.php in your project or somewhare that can help you to use stand-alone LibSQL driver as an IDE helper. By default this stubs is come inside this package.
5. Configure php.ini file and added the extension address with relative path that pointed to the extension
6. Enjoy!

or you can use Turso PHP Install (Linux and MacOS Only) to install libSQL Extension for PHP without worry.

Installation

You can install the package via composer:

Then register the service provider at bootstrap/providers.php array:

Environment Variable Overview

You need to know the additional configuration in .env file, which come from Laravel and which come from LibSQL Driver. And here is the overview of .env:

Laravel

• DB_CONNECTION key is represent default database connection like libsql, sqlite, mysql, mariadb, pgsql, and sqlsrv.
• DB_DATABASE key is represent the location of database name or in this case is database filename.

LibSQL Driver

Create a new Turso Database here

• DB_AUTH_TOKEN - You can generate using turso db tokens create <database-name> command or you can visit your Turso Dashboard and select database you want to used and generate the token from there.
• DB_SYNC_URL - This generate by Turso when you craete a new database, you can get the database URL by using this command turso db show --url <database-name>
• DB_SYNC_INTERVAL - This variable defines the interval at which an embedded replica synchronizes with the primary database. It sets a duration for automatic synchronization of the database in the background. When configured, the embedded replica will periodically sync its local state with the state of the primary database to ensure it has the latest data. This is particularly useful for ensuring that replicas remain up-to-date with minimal manual intervention. Default is: 5 seconds.
• DB_READ_YOUR_WRITES - This variable configures the database connection to ensure that writes made by a connection are immediately visible to subsequent read operations initiated by the same connection. This is important in distributed systems to ensure consistency from the perspective of the writing process. When enabled, after a write operation is performed, any reads that follow from the same connection will see the results of that write. This option is typically enabled by default to ensure that clients always see their latest writes.
• DB_ENCRYPTION_KEY - This variable is defined for specifying the encryption key used in database encryption. It represents the secret key that is used to encrypt and decrypt the database content, ensuring that the data stored in the database is protected and can only be accessed by individuals who possess the correct key. This key is a critical component of encryption-at-rest strategies, where the goal is to secure data while it is stored on disk, preventing unauthorized access. Default is: empty.
• DB_REMOTE_ONLY - This variable is define to use remote connection only, if you only want to read and write the database from remote database. Default: false.

Configure The Connection

LibSQL has 3 types of connections to interact with the database: In-Memory Connection, Local Connection, Remote Connection, and Remote Replica Connection (Embedded Replica)

In-Memory Connection

To be able to use LibSQL in-memory as if you were using SQLite, simply change the following .env:

Local Connection

To be able to use LibSQL locally as if you were using SQLite, simply change the following .env:

Ignore other LibSQL .env variables.

Remote Connection

To use LibSQL Remote Connection only, you can define the following .env variables:

Remote Replica Connection (Embedded Replica)

To configure remote replica connection (embedded replica), you can simply use the following .env:

That's it! How easy to make different connection using LibSQL Driver in Laravel, right?!

Database Configuration

Add this configuration at config/database.php inside the connections array:

Copy and Paste and do not change it! Or try to change it and will broke your app or give you malfunction.

Usage

For database operation usage, everything have same interface like usual when you using Illuminate\Support\Facades\DB in your database model. But remember, this is LibSQL they have sync method that can be used when you connect with Remote Replica Connection (Embedded Replica).

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

• Imam Ali Mustofa
• All Contributors

License

The MIT License (MIT). Please see License File for more information.