Download the PHP package graham-campbell/digitalocean without Composer

Laravel DigitalOcean

Laravel DigitalOcean was created by, and is maintained by Graham Campbell, and is a DigitalOcean PHP API Client bridge for Laravel. It utilises my Laravel Manager package. Feel free to check out the contribution guidelines.

Installation

This version requires PHP 7.4-8.3 and supports Laravel 8-11.

To get the latest version, simply require the project using Composer:

Once installed, if you are not using automatic package discovery, then you need to register the GrahamCampbell\DigitalOcean\DigitalOceanServiceProvider service provider in your config/app.php.

You can also optionally alias our facade:

Configuration

Laravel DigitalOcean requires connection configuration.

To get started, you'll need to publish all vendor assets:

This will create a config/digitalocean.php file in your app that you can modify to set your configuration. Also, make sure you check for changes to the original config file in this package between releases.

There are two config options:

Default Connection Name

This option ('default') is where you may specify which of the connections below you wish to use as your default connection for all work. Of course, you may use many connections at once using the manager class. The default value for this setting is 'main'.

DigitalOcean Connections

This option ('connections') is where each of the connections are setup for your application. Example configuration has been included, but you may add as many connections as you would like. Note that the 2 supported authentication methods are: "none" and "token".

Usage

DigitalOceanManager

This is the class of most interest. It is bound to the ioc container as 'digitalocean' and can be accessed using the Facades\DigitalOcean facade. This class implements the ManagerInterface by extending AbstractManager. The interface and abstract class are both part of my Laravel Manager package, so you may want to go and checkout the docs for how to use the manager class over at that repo. Note that the connection class returned will always be an instance of DigitalOceanV2\Client.

Facades\DigitalOcean

This facade will dynamically pass static method calls to the 'digitalocean' object in the ioc container which by default is the DigitalOceanManager class.

DigitalOceanServiceProvider

This class contains no public methods of interest. This class should be added to the providers array in config/app.php. This class will setup ioc bindings.

Real Examples

Here you can see an example of just how simple this package is to use. Out of the box, the default adapter is main. After you enter your authentication details in the config file, it will just work:

The digitalocean manager will behave like it is a DigitalOceanV2\Client class. If you want to call specific connections, you can do with the connection method:

With that in mind, note that:

If you prefer to use dependency injection over facades like me, then you can easily inject the manager like so:

For more information on how to use the DigitalOceanV2\Client class we are calling behind the scenes here, check out the docs at https://github.com/DigitalOceanPHP/Client/tree/4.9.0#examples, and the manager class at https://github.com/GrahamCampbell/Laravel-Manager#usage.

Further Information

There are other classes in this package that are not documented here. This is because they are not intended for public use and are used internally by this package.

Security

If you discover a security vulnerability within this package, please send an email to [email protected]. All security vulnerabilities will be promptly addressed. You may view our full security policy here.

License

Laravel DigitalOcean is licensed under The MIT License (MIT).

For Enterprise

Available as part of the Tidelift Subscription

The maintainers of graham-campbell/digitalocean and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. Learn more.