Fixing apparent Laravel package incompatibility with Lumen

@CharlesW I got it to publish. I added the public_path function to lumen helpers file.

if (!function_exists('public_path')) {
    /**
     * Return the path to public dir
     *
     * @param null $path
     *
     * @return string
     */
    function public_path($path = null)
    {
        return rtrim(app()->basePath('public/' . $path), '/');
    }
}

Found info on that here:

https://gist.github.com/vluzrmos/30defc977877e0eba7b2

Did you configure your Lumen install to publish and create a config directory?

http://laravelista.com/json-web-token-authentication-for-lumen/

Now do we have an example to test?

My app.php

$app->register('Tymon\JWTAuth\Providers\JWTAuthServiceProvider');
$app->register('Aws\Laravel\AwsServiceProvider');
$app->register(Appzcoder\LumenRoutesList\RoutesCommandServiceProvider::class);
$app->register(JildertMiedema\LaravelPlupload\LaravelPluploadServiceProvider::class);

//$app->register('Barryvdh\Debugbar\ServiceProvider');

/** This gives you finer control over the payloads you create if you require it.
 *  Source: https://github.com/tymondesigns/jwt-auth/wiki/Installation
 */
class_alias('Tymon\JWTAuth\Facades\JWTAuth', 'JWTAuth');
class_alias('Tymon\JWTAuth\Facades\JWTFactory', 'JWTFactory'); // Optional

class_alias('Aws\Laravel\AwsFacade', 'AWS');
class_alias('Collective\Html\HtmlFacade', 'HTML');
class_alias('Collective\Html\FormFacade', 'Form');
class_alias(JildertMiedema\LaravelPlupload\Facades\Plupload::class, 'Plupload');

Jamess-MacBook-Pro:lumen jimm$
Jamess-MacBook-Pro:lumen jimm$ php artisan vendor:publish
Copied Directory [/vendor/jildertmiedema/laravel-plupload/public/assets] To [/public/vendor/jildertmiedema/laravel-plupload]
Publishing Complete!
Jamess-MacBook-Pro:lumen jimm$

Lumen does not provide all of the functionality that's available in laravel. So the expectations it has for service providers are different.. if you want to use this in lumen, you'll probably have to fork and make a bunch of changes... or you could use laravel instead of lumen.

It doesn't seem to me you'd really want that kind of a package with lumen though to begin with.. lumen is really intended for building a very light-weight api, not something that's also going to be providing a full frontend/etc.. you might be better off using laravel.

Or, include plupload in your frontend app, since it is just a javascript library, and point it to the appropriate api routes that you manually build out with lumen.

Lovely! Adding compat_l5.php and VendorPublishCommand did the trick. Thank you!

As a Larvel/Lumen newbie, I don't quite get what's going on here big-picture-wise. Should I not expect to be able to use Laravel service providers as-is with Lumen? Is it intentional that for places where Lumen shares docs with Laravel, there can be caveats that aren't spelled out? Or do we think these are just growing pains because Lumen is shiny and new?

Mostly, just wondering if it was a poor choice to use Lumen instead of Laravel for my API.

— Charles

@CharlesW Lumen is just lightweight Laravel. There is no magical difference. Turn on what you need. As you saw when you added the helpers. I don't use Eloquent, I have my own model library. Lumen speeds up the whole interface. Now I added a route, I need a Browser piece to test front end. The examples I found are depending on Flash or Silverlight???

http://www.plupload.com/docs/Options

@CharlesW

@willvincent: Or, include plupload in your frontend app, since it is just a javascript library, and point it to the appropriate api routes that you manually build out with lumen.

Makes sense, and that's how I'm currently building — Larvel for the front-end, Lumen for the API.

@jimmck: Lumen is just lightweight Laravel. There is no magical difference.

Yeah, I thought Lumen would just be Laravel with stuff turned off by default. But important stuff is missing and it seems like devs are expected to know how to port additional Laravel stuff over if needed. I expect that seems pretty straightforward to you, but I'm not quite there yet. :O) Thanks again!

— Charles

I guess I don't understand if you're using laravel to provide your frontend why you wouldn't also build the backend into it too.. to my mind lumen makes the most sense when you just need a simple api to back something like a javascript frontend, or the like..

@willvincent: I guess I don't understand if you're using laravel to provide your frontend why you wouldn't also build the backend into it too.

Lumen is intended for microservices and APIs, and the REST API I'm building falls squarely into that territory, so it seemed to make sense. Effectively, I bought the messaging on the home page at face value. :O)

I'd appreciate any thoughts from experienced Laravel users on why that might not be the best way to go.

— Charles

Right, sure.. but why a separate (server side) app that talks to it? /shrug/ everybody's got their own needs I guess :)

At any rate -- you shouldn't need the plupload package in your rest api, since plupload is client-side JS... a laravel package for a client-side library seems largely unnecessary.

@willvincent: why a separate (server side) app that talks to it?

The service will support a PC/mobile website, but also a mobile app and devices as well. It's mostly a matter of wanting to be able to scale and control access to the front-end and the service separately.

you shouldn't need the plupload package in your rest api

Part of the package is client-side support (which I'll be using as well), but I also need it to support chunked transfer encoding for large file uploads.

— Charles

Guys. As a dev who has worked with many languages, API's, databases and more frameworks (Than Dead Cats :) Its seems that this Laravel world of devs is under the impression it just makes things work. It does not. Lumen is a manual transmission version of Laravel. Laravel is still a very young codebase. There are parts that need to mature. Windows 1.0 was very flawed. The docs did not always match your code. You had to figure out what was going on. @CharlesW I appreciated your question, I will use it as a take away to finish the investigation. Learn how things work and form your own opinion. Choosing Laravel or Lumen or whatever, you are going to face issues. @willvincent Client side libraries have been talking to server side libraries since you could cross wire a serial port. Or write a VT100 display module library in DIBOL and call RSTS/E libraries to DEC ISAM libraries. Enjoy the coding :) :)!!! One reason I like Jeff, he always advocates, Read The Code!!!!

BTW. I am so bummed that Halt and Catch Fire ended last week. So Bummed!!!!

Client side libraries have been talking to server side libraries since you could cross wire a serial port.

Yeah. obviously. What's your point? o.O

https://github.com/basicit/lumen-vendor-publish for use "php artisan vendor:publish in your console".

I added directory seperator for cross operating system support:

if ( !function_exists('public_path')) { function public_path($path = null) { return rtrim( app()->basePath( DIRECTORY_SEPARATOR.'public'. ($path ? DIRECTOY_SEPARATOR . $path : $path) ), '/'); } }