Download the PHP package leolabs/gdapi-php without Composer
On this page you can find all versions of the php package leolabs/gdapi-php. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package gdapi-php
gdapi-php
A PHP client for Go Daddy® REST APIs.
Requirements
- PHP 5.3 or greater
- libcurl PHP extension with SSL support
- An account in a compatible service, such as Cloud Servers™
- Your API Access and Secret key pair
Getting Started
If you haven't already tried it, open up the base URL of the API you want to use in a browser. Enter your Access Key as the username and your Secret Key as the password. This interface will allow you to get familiar with what Resource types are available in the API and what operations and actions you can perform on them. For more information, see the documentation site.
Setting Up
A PHAR archive of the latest stable version is available over in the Downloads page. We recommend you use this rather than the source code from the repo directly.
Using the PHAR Archive
Download the .phar file:
curl -O https://github.com/downloads/godaddy/gdapi-php/gdapi.phar
Create a client:
Using the source
To use the source code instead, clone it:
git clone https://github.com/godaddy/gdapi-php.git
Create a client:
Problems connecting
Consult the SSL Problems section if you get an error when creating the client that says something like this:
SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Finding Resources
Each resource type in the API is available as a member of the Client.
Listing all resources in a collection
Filtering
Filters allow you to search a collection for resources matching a set of conditions.
Getting a single Resource by ID
If you know the ID of the resource you are looking for already, you can also get it directly.
Working with Resources
Accessing attributes
Resources have a getter method for each attribute, as "get"+{attribute name}. Attributes that can be changed also have a "set"+{attribute name} method. The first character of the attribute name may be capitalized for readability, but the rest of the name must match the API.
Making changes
Creating new resources
Removing resources
With an instance of the resource:
Or statically:
Executing Actions
Actions are used to perform operations that go beyond simple create/read/update/delete. Resources have a "do"+{action name} method for each action. The first character of the action name may be capitalized for readability, but the rest of the name must match the API.
Following Links
Response collections and resources generally have a "links" attribute containing URLs to related resources and collections. For example a virtual machine belongs to a network and has one or more volumes. Resources have a "fetch"+{link name} method for each link. Invoking this will return the linked resource
Handling Errors
By default, any error response will be thrown as an exception. The most general type of exception is \GDAPI\APIException, but several more specific types are defined in class/APIException.php.
It is important that you put the catch blocks from most-specific to least-specfic classes. PHP runs through your catch statements in order and only calls the first one that matches the exception. If you flipped the two catches above, "Something else went wrong" would be printed for any exception, even if it was a NotFoundException.
If you prefer to not use exceptions, you can disable them when creating the Client. When an error occurs, instead of throwing an exception the response returned will be an instance of \GDAPI\Error.
Advanced Options
Mapping response objects to your own classes
By default all response objects are an instance of \GDAPI\Resource, \GDAPI\Collection, or \GDAPI\Error. In many cases it is useful to map responses to your own classes and add your own behavior to them.
SSL Problems
Some installations of libcurl do not come with certificates for any Certificate Authorities (CA). This client always verifies the certificate by default, but having no CA certificates means it won't be able to verify any SSL certificate. To fix this problem, you need a list of CA certificates to trust. Curl provides a copy that contains the same CA certs as Mozilla browsers: cacert.pem.
If you have permission to edit your php.ini, you can fix this globally for anything that uses the libcurl extension:
Add a line like this to your php.ini, then restart your web server, if applicable:
curl.cainfo = /path/to/cacert.pem
If you don't have permission, or don't want to make a global change, you can configure just the GDAPI client to use the file:
More options
For info on other options that are available, see the $defaults array in class/Client.php.
