Laravel API Docs Generator
Switch branches/tags
Nothing to show
Clone or download
stesvis and f2m2rd Update head.blade.php
The original version doesn't work when you deploy to a sub-folder on your server because the paths are hardcoded. This way using the asset() helper function resolves it.
Latest commit 8052837 Sep 19, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
src Update head.blade.php Sep 19, 2018
tests Initial Commit Nov 8, 2014
vendor Initial Commit Nov 8, 2014
LICENSE.md Update LICENSE.md Aug 21, 2016
README.md Update README to reflect updates Oct 20, 2017
composer.json Upgrade to laravel 5.5 Feb 22, 2018
composer.lock Initial Commit Nov 8, 2014
phpunit.xml Initial Commit Nov 8, 2014
provides.json Initial Commit Nov 8, 2014

README.md

Laravel API Docs Generator

This Laravel package provides an API Documentation generator based upon your Routes and Controller Method DocBlock comments.

Installation

Laravel 5.0

Begin by installing this package through Composer. Edit your project's composer.json file to require f2m2/apidocs.

"require-dev": {
    "f2m2/apidocs": "dev-master"
}

Next, update Composer from the Terminal:

composer update

Once the packaage has installed, the final step is to add the service provider. Open config/app.php, and add a new item to the providers array.

'F2m2\Apidocs\ApidocsServiceProvider',

Run the artisan command from the Terminal to see the new apidocs command.

php artisan apidocs:generate

Create a copy of the API Docs Config by running this artisan command:

php artisan vendor:publish

Laravel 4.2

See installation: https://github.com/f2m2/apidocs/tree/1.0.0

Notes

Route Prefix

Create a prefix for your routes with an API Version. i.e. 'api/v1

Route::group(['prefix' => 'api/v1'], function(){
     // ...
});

######## Laravel 5.4 defaults to api prefix (Route::prefix('api')). If your routes/api.php looks like this...

Route::group(['prefix' => 'v1'], function(){
     // ...
});

... then the route for the generate command would be api/v1 Otherwise it will be just api

DocBlock Example

Below is a docBlock example.

/**
* Display the specified resource.
* GET /user/{id}
*
* @param  int  $id  The id of a User
* @return Response
*/
public function show($id)
{
    // Display User
}

License

See LICENSE file.