Weave Code
Laravel Directadmin Laravel Package
solitweb/laravel-directadmin
Laravel integration for the DirectAdmin control panel API. Manage hosting accounts, domains, email, databases and more from your Laravel app with a clean, fluent interface. Includes config publishing, easy credentials setup and support for common DirectAdmin API commands.
Laravel 5 DirectAdmin API wrapper
Frequently asked questions about Laravel Directadmin
- Does solitweb/laravel-directadmin work with Laravel 10, 11 and PHP 8.2?
- Probably not without changes. The package advertises Laravel 5 support, and its illuminate/support constraint almost certainly caps it below Laravel 10 and 11, which in turn makes PHP 8.1+ compatibility unlikely. Verify the exact composer constraints on Packagist before planning an install. If your application is on a modern Laravel version, treat this as a fork rather than a drop-in dependency.
- How do I install and configure solitweb/laravel-directadmin?
- Install it with composer require solitweb/laravel-directadmin, then publish the package configuration file so you can set your DirectAdmin host, port and credentials. On Laravel 5.5 and later the service provider and facade are registered automatically through package auto-discovery, so no manual registration is needed. A working spike against a sandbox DirectAdmin instance should take well under a day.
- Where do I set the DirectAdmin host, port and API credentials?
- Credentials live in the published config file, so you should drive them from environment variables rather than hardcoding them in the repository. DirectAdmin's legacy CMD_API interface typically runs on port 2222 over HTTPS. Keep that config out of version control and use separate entries per environment or per DirectAdmin server if you manage a fleet.
- Does the package support DirectAdmin login keys instead of the admin password?
- This is unconfirmed and needs to be checked against the source before you commit. DirectAdmin supports both plaintext admin passwords and scoped login keys, and the latter is strongly preferred. If the package only handles password authentication, you would be storing a root-equivalent control panel credential in application config, which is a significant security trade-off.
- Does the package detect DirectAdmin API errors, or does it report success on failure?
- DirectAdmin returns HTTP 200 even when a command fails, signalling the failure in the response body with error=1 along with a text and details field. A wrapper that does not parse that field will happily report success on failed provisioning, and this is a common defect in packages of this vintage. Inspect the response handling in the source and add your own error check if the package does not do it.
- Which DirectAdmin API commands are covered by this wrapper?
- The package is a thin transport adapter over the DirectAdmin CMD_API interface, described as supporting common commands for users, domains, email and databases. There are no DTOs or resource abstractions, so anything not explicitly wrapped has to go through raw pass-through. Map the endpoints you actually need, such as user creation, suspension, password changes and DNS, against what the package exposes before adopting it.
- Can I disable SSL verification for a self-signed certificate on port 2222?
- Control panels frequently serve a self-signed certificate on port 2222, so you will likely need a verify-peer toggle to connect at all. Check whether the package exposes that option through its config and, if it does, scope it to development or trusted internal networks only. Leaving peer verification off in production exposes your admin credentials to interception.
- Can I automate hosting account creation and suspension from a billing system with this package?
- That is exactly the intended use case: reseller and hosting automation, order-to-provision pipelines, and internal control planes that manage DirectAdmin users, domains, mailboxes and databases. The package gives you the API call, not the integration, so provisioning state, idempotency and reconciliation logic are yours to build. Wrap it in your own HostingProvisioner service so the rest of your application never depends on it directly.
- How should I test a Laravel DirectAdmin integration without a live server?
- The package is a thin HTTP wrapper with no visible CI matrix, so plan on testing your own adapter rather than relying on the package's tests. Define an interface for the operations you need and mock that in your application tests, then run a small set of integration tests against a sandbox DirectAdmin instance. Also assert that a response body containing error=1 surfaces as an exception in your code.
- Is solitweb/laravel-directadmin actively maintained, or should I fork it?
- It has roughly 21 stars and a single maintainer with no visible corporate backing, so treat upstream as a snapshot rather than a dependency you can count on for patches. Verify the last release date against the real tag history, since low-star packages often show metadata artefacts rather than genuine activity. The safest posture is to adopt it behind an interface you own, which turns a stale third-party package into a swappable adapter, or to write your own thin client given how small the DirectAdmin API surface is.
Weaver
How can I help you explore Laravel packages today?