It looks like your Laravel application is attempting to use a SQLite database, even though you mentioned you are not using a database. This is likely because Laravel's cache, session, or queue drivers are set to use the database connection by default, or your .env file is configured to use SQLite.
Here's how you can resolve this:
1. Check Your .env File
Make sure your .env file does not set the cache, session, or queue drivers to database. Instead, use file or array for local/testing, or a more appropriate driver for production (like redis or memcached if available).
CACHE_DRIVER=file
SESSION_DRIVER=file
QUEUE_CONNECTION=sync
2. Remove or Update Database Configuration
If you are not using a database at all, set your database connection to null or a dummy value in .env:
DB_CONNECTION=null
Or, if you want to keep the default, just ensure nothing is trying to use the database.
3. Clear Config Cache
After making changes to your .env, clear the config cache:
php artisan config:clear
php artisan cache:clear
4. Check for Database Usage in Code
Ensure you are not calling any code that would use the database, such as:
Cache::store('database')Session::driver('database')- Any Eloquent or DB queries
5. Remove Database Cache Tables (if any)
If you previously set up cache or sessions to use the database, you might have migration files or references. You can safely remove those if you’re not using a database.
Summary:
Your error is because Laravel is trying to use a SQLite database for caching or sessions. Update your .env to use file drivers, clear your config cache, and make sure your code does not reference the database.
Let me know if you need more help!