- How do I install the samuelmwangiw/linode package in Laravel?
- Install it with Composer using composer require samuelmwangiw/linode. Laravel auto-discovers the package service provider, so you can start using the wrapper after installation. Publish the configuration file and add your Linode API token to the environment before making API calls.
- What Laravel and PHP versions does this Linode package support?
- The package is designed for Laravel applications, but exact version constraints should be checked in its composer.json. After the Saloon v3 upgrade, compatibility should be verified against Laravel 9, 10, and 11 and PHP 8.1 or newer. Test dependency resolution in a development branch before upgrading production applications.
- What can I manage with this Laravel Linode SDK?
- The package wraps the Linode API and lets you manage Linodes, volumes, domains, and other cloud resources from your PHP application. It provides a fluent interface for common provisioning and management tasks. It is intended for Laravel projects that need to automate Linode infrastructure operations.
- How do I publish the Linode package configuration in Laravel?
- Use Laravel's vendor:publish Artisan command and select the Linode package provider or configuration tag. The package includes publishable configuration for storing settings such as your API token and other client options. After publishing, review the config file and set the required environment variables.
- Is samuelmwangiw/linode compatible with Saloon v3?
- Version 2.4.0 upgrades the package's internal Saloon dependency from v2 to v3. The package now targets Saloon v3 only, so projects pinned to Saloon v2 may encounter Composer conflicts. If your code interacts directly with Saloon requests, responses, or middleware, review Saloon v3 breaking changes before upgrading.
- Will upgrading to v2.4.0 break my existing Linode integration?
- The upgrade is likely breaking for consumers that directly interact with Saloon request or response objects or extend the package's HTTP layer. If you only use the package's public fluent API, migration may be limited to dependency resolution and testing. Pin v2.3.0 until you have validated the upgrade in a non-production environment.
- How do I test Linode API calls in Laravel without hitting the real API?
- Because the package is Saloon-powered, you can typically mock Saloon responses in your test suite instead of calling Linode directly. Add integration tests that validate your application flow against representative responses, and use a separate Linode test token for any sandbox checks. Review the package tests and Saloon v3 mocking APIs for the correct approach.
- Does this package require a Linode API token, and how is it configured?
- Yes, you need a Linode API token to authenticate requests. Publish the package configuration and add the token through your .env file or the published config file, following the key names defined there. Keep the token out of version control and use restricted permissions where possible.
- What are the alternatives to this package for managing Linode from Laravel?
- You can call the Linode API directly with Guzzle or Saloon, or use Linode's official tooling and API documentation to build a custom integration. Other Laravel Linode wrappers may exist, but evaluate their maintenance status and Saloon compatibility. This package is a good fit when you want a fluent Laravel wrapper with publishable configuration and service provider integration.
- Is this package safe to use in production and how should I migrate from v2.3.0?
- Review the package's composer.json changes and Saloon v3 breaking changes, then update dependencies in a development branch. Run the package tests and your application integration tests, and validate real Linode API calls before deploying. Until that is complete, pin v2.3.0 in production and track Saloon v3 security and bug fixes for ongoing maintenance.