Download the PHP package e-artspace/resourceful without Composer

Resourceful

Resourceful is a simple component designed for rapid prototyping REST JSON resources exposing mostly CRUD operations. It is driven off of JSON Hyper-Schemas and SILEX.
You use Hyper-Schemas to define your resources and their relationships with each other. No coding other than writing Hyper-Schemas and registering new resources is required. You only need to worry about your API and not it's implementation. Proper HTTP response codes and headers are managed automatically.

This package is inspired by the jdesrosiers/resourceful project project by Jason Desrosiers.

How it Works

Install Resourceful using composer

Define your front controller.

That's it. You are ready to get started. Run the application using the built-in PHP server.

You can use the json browser implementation at http://json-browser.s3-website-us-west-1.amazonaws.com/?url=http%3A//localhost%3A8080/. On the first run, a folder called schema is created and a default index schema and resource is created. You are expected to add links to this default index schema as you add resources. These links wil give your users a place to start.

Adding another new resource to your application, requires only one line of code in your front controller.

The first argument ov CRUDControllerProvider is the name of the json schema that defines the structure of type items. It must be unique to the application.

The persistance is managed by the store service in $app['schema name.store'] (e.g. $app['foo.store']) or, if not present, by the service in $app['data.store'] that is created by default as a local file system store.

The store service can be any Doctrine Cache implementation. The default implementation is usually good enough for a rapid prototype, but you can choose something like memcache or redis if you prefer. If you use the default store implementation, you can set the data direcotory in $app['data.dir'] paramether ( defaut '/tmp/resourceful');

Once the resource is registered, a good next step is to add a link in your index schema to create a "foo". Refresh your Jsonary browser and you should see the link you added to the index. Also, a default "foo" schema was generated in your /schema folder. Fill out your "foo" schema how you like and then use the index link you added to create a "foo". All CRUD operations are available for the resource. You can customize operation redefining $app['schema name.controller'] (e.g $app['foo.controller'])

You can disable the automatic creation of schema and sample date by setting $app['createDefault'] to false;

You can customize the function that creates unique id from items. Just redefine $app['uniqid'] or even a different version for each data type with $app['schema name.uniqid'] (e.g. $app['foo.uniqid']). The default is to generate id using the php function uniqid()

Thats all. Just keep adding resources and links between those resources to make a useful API.

Developing and Testing environment

A vagrant virtual appliance is available for developing and testing in a local workstation.

Local workstation requirements:

• install GIT. Select “checkout as is , commit Unix-style line endings”.
• install Vagrant
• install Virtualbox

The following commands can be used to perform the initial checkout of resourceful project:

Running a virtual appliance with vagrant

The following commands can be used to start a virtual appliance and login to it:

An apache web server is configured to localhost port 8080 (or the one you specified in vagrant up)

Run unit and functional tests in vagrant

The following commands can be used to start execute all unit tests:

Note that all the project repoistory is mounted (and synced) in /vagrant dir on the virtual host.

To get a test coverage report:

Run smoke system test in Postman

The virtual appliance http server is mapped on localhost:8080 on the workstation

import tests/system/smoke_test_v1.json in postman and call the runner.

Destroy virtual appliance

to destroy the virtual appliance:

More options with vagrant --help

Features

The Index Schema

it is largely up to you to make your REST/HTTP application discoverable, but Resourceful gets you off to a good start by automatically creating an index schema that points to the root of you app. The index should be updated to direct your users in what they can do with your application.

Schema Generation

The first time the application is run after a new resource is registered, a generic schema is created in the schema folder. This is trying to free you up from some of the boiler plate stuff so you can work faster.

Retrieving a Resource

If a requested resource does not exist, it a 404 Not Found response will be given. The Content-Type of the returned resource will use the JSON Hyper-Schema suggestion of including a profile attribute that points to the Hyper-Schema that defines the resource in the response.

Creating a Resource

A resource can be created in two ways. The most common way is to use POST. When a resource is created using POST, there will be a Link header pointing to the newly created resource. A resource can also be created using a PUT request on a URI that doesn't contain a resource. Resource creation will always respond with 201 Created. The new resource will be echoed in the response.

Modifying a Resource

A resource can be modified using a PUT request. PUT requests do not do partial updates. The resource passed will be stored exactly how it was passed. The modified resource will be returned with the response.

Deleting a Resource

When a resource is DELETEd, it will respond with a 204 No Content. If the resource to be DELETEd does not exist, the standard success response will be given. It is not considered an error to DELETE a resource that does not exist.

Validation

All input JSON is automatically validated for compliance with the JSON Schema that was defined for that resource. Validation failures result in 400 Bad Request responses.

Content Negotiation

Considering that Resourceful is based on JSON Hyper-Schema and Jsonary, the only format supported is JSON. So, any requests for a format other than JSON will result in a 406 Not Acceptable response. Any requests that pass content that is not JSON will result in a 415 Unsupported Media Type response. This is all handled by the silex-conneg-provider service provider.

Support for OPTIONS requests

I don't think anyone cares about OPTIONS request support unless they need it for CORS, but it is good to have for HTTP compliance anyway. Resourceful gets OPTIONS request support from the silex-cors-provider.

CORS Support

CORS support is provided by the silex-cors-provider service provider. To enable CORS support, add the cors after middleware to your application.

Supporting Projects

Silex

Resourceful is a Silex application with some service providers and controllers configured.

JSON Hyper-Schema

JSON Hyper-Schema is the basis of this project. JSON Hyper-Schema is the only proposal I have found that can do both discoverability and hyper linking. JSON Hyper-Schema makes this project possible.

Jsonary

Jsonary is a generic Hyper-Schema browser. It isn't perfect and it certainly isn't pretty, but it gives us the ability to view and manipulate any Hyper-Schema driven resource without the need to write any front-end code.

Jsv4

Jsv4 is a JSON Schema validator. Resourceful uses it to validate request JSON based on the Hyper-Schemas you write.

silex-conneg-provider

No silex REST/HTTP application is complete without the silex-conneg-provider or something like it. This service provider adds middleware that inspects a request's content negotiation headers and responds appropriately if there is a problem.

silex-cors-provider

The silex-cors-provider is primarily used for generating OPTIONS routes. However, CORS support comes in handy as well.

Doctrine Cache

I chose to use Doctrine Cache for data storage. They have a wide range of implementations, so you can choose how you want to store your data. Some options include the filesystem, memcache, or redis. If none of these meet your needs you can always write your own Doctrine\Common\Cache\Cache implementation.