Laravel 5.2 (What features do we all want?)

multi-tenancy

+1 for multi-tenancy

You mean simplify the usage of multiple database ?

Auth for multiple tables, ODM for mongodb, and schema dumping

@lstables There is no one way to implement multi-tenancy, just look at the number of threads on it there are on this forum alone, and the wildly varying responses. Therefore, I wouldn’t hold my breath at “multi-tenancy” being baked in to the Laravel core.

I've built three medium/large sized multi-tenant apps so far using Laravel... everything you need is already there (has been since L4 tbh).

Better API support out of the box, possible merge from dingo/api package: https://github.com/dingo/api

Just to clarify its a discussion for the thing we all want.

For 5.1 to last a while and not be completely outdated in one month. Gees 5.1 just came out.

mongodb support and mongodb added to homestead

What do you guys mean by multi-tenant apps? Taylor's asked the same question on Twitter but still noone replied.

Software Multitenancy refers to a software architecture in which a single instance of a software runs on a server and serves multiple tenants. A tenant is a group of users who share a common access with specific privileges to the software instance. With a multitenant architecture, a software application is designed to provide every tenant a dedicated share of the instance including its data, configuration, user management, tenant individual functionality and non-functional properties. Multitenancy contrasts with multi-instance architectures, where separate software instances operate on behalf of different tenants.

Wikipedia

Still have no clue what that is.

Wikipedia doesn't always help, especially when it's an extensive article. Thought someone would be able to describe what multi-tenant apps are with an example. Usually that's how people most quickly learn and adapt new terms.

Multitenancy - simplified...

Let me install one instance of Laravel and allow many sites to access the same instance, but only access their own data.

Of course that's already doable, it just needs some documentation and/or Jeffrey to show how to do it.

What feature would I like?

Simple CRUD generation out of the box, like Yii.

That is so handy as a starting point and a massive time saver for prototyping.

I'm looking for:

1. speed increases (hey, OSX and iOS is doing it)
2. Multitenancy (however, this could be a package like socialite or cashier)
3. better i18n and g11n

CRUD is sort of fulfilled by the CI and Jeff"s package.

Since we have a LTS, I think Taylor should focus on the "perfect" project. The sample/boilerplate kind of project he was talking about during the podcast. So anyone can hack their way forward basing that project and the best practices on it.

Also more than 5.2 Its good if Taylor can focus more on packages/services, maybe something for benchmarking.

RBAC

Bake Console

The interpretation of multi tenancy is wide. For instance AuraEQ has a package that mutates models to allow for an additional tenant Id. I am currently making progress on an unobtrusive package that distinctly seperates database,files etc. If you're interested in the latter, I'd love to see your idea's about such a package.

As what I'd love to see is a new website (or page on laravel.com) that lists and allows rating of laravel specific packages from packagist.

I think a simple way to change the database connection at runtime will solve most multitenancy problems. Here you have to tweak with the config values.

For laravel 5.2 I would love... A builtin/easy way to setup a server for event broadcasting. I'm sick of installing new things on my server for single purposes like this.

Some interesting points here, keep um coming guys, then it can be passed on to Taylor to have a look through.

@Putheaengineer what do you mean with a bake console?

Sorry shouldn't have marked that as "answered" trigger happy on the mouse, keep your posts coming....

Also I'd love to see route model binding disappear. There is countless threads here with newbies totally lost with routing etc because of this.

I would like to see some markdown parser for blade.

@deadlockgB there is already plenty of composer packages for this

league/commonmark is one of them (Jeffrey uses it here)

From Taylor's twitter feed

Note: just because I said roles and permission was most popular suggestion doesn’t mean I intend to build it :)

Are we just posting to the wind here????

Well, Taylor's reason is: if there are a good packages for it, there's no need for him to build one. At least that's what I understood from the conversation I had with him on Slack few weeks ago (about ACL and him building an official package)