Porting to Laravel/ Illuminate 5

[itonics-tbeauvais]

Laravel 5 is almost out. Are there current plans to adapt the wonderful Elasticquent library to use this new version?

[stevepop]

I am interested in this too as I am currently migrating my codebase to Laravel 5

[kticka]

I'm starting new project on laravel 5, and I hope this pack will be adopted to ;)

[cerw]

Yes please 👍

[nWidart]

Any updates on this ?

[majkiee]

Yeah, would love to see a L5 port

[danhanly]

Love to see this work for L5

[mvodanovic]

It works with L5, there is a pull request which fixed it:
https://github.com/nWidart/Elasticquent/tree/feature/laravel-5
It just hasn't been pulled yet. If you want to use it with composer, just add this to composer.json:

"repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/nWidart/Elasticquent"
        }
    ],

And then add this to the require section:

"fairholm/elasticquent": "dev-feature/laravel-5"

[stoppy]

thanks @mvodanovic

[mustafaaloko]

As the author of this package didn't respond to Laravel 5 issue and also didn't merge any pull requests for changes. I have created a new package (Elasticquent 5) on top of this one to be compatible with Laravel 5. https://github.com/mustafaaloko/elasticquent5

[timgws]

@mustafaaloko there is already one that we (@adamfairholm and myself) are working on supporting now for Laravel 5.

https://github.com/elasticquent/elasticquent

[ejlocop]

@timgws i'm using Laravel 5.1.28, and your elasticquent/elasticquent. after reading the docs. i've found out that app/config/elasticquent.php doesn't exists in my folder after updating the composer.
what version of laravel does elasticquent requires?

[timgws]

@ejlocop if it does not exist after updating composer, that is fine. Just add the config file yourself.