For the multi-tenant guys, i have invested much time with it, then i made a simple demo app to support multitenancy in laravel, with just a few laravel bult-in components:

https://github.com/uxweb/laravel-multi-db

I would like to see page-reload in elixir out of the box. It is already possible to add it myself, but it would be great if it was included.

I think more queue commands would be very welcome. For example I would like a simple way to retry all failed jobs. Also I would love to be able to specify a different queue to move to after a certain amount of retries. That would come in handy for doing something like sending failed queue jobs to the buried queue (beanstalkd).

Support for Compass in elixir would also be nice!

Hmm localization support that extends to the database might be cool. I know there are packages out there that do this.

For example, it could be done through migrations or Eloquent:

Migrations

They could setup additional morph tables to support extra locales.

Schema::create('articles', function(Blueprint $table)
{
    $table->addLocalization('en','es');
    $table->removeLocalization('es');
}

Eloquent

protected $localize = ['en', 'es'];

Then based on the locale set, load from the correct table or default.

What about an integrated deploy workflow?

• Move bootstrap/cache to storage/framework/cache
• localization for the whole setup ... yes, I know there are packages that do this and implementations may vary but then why is illuminate/foundation/auth even included?

More of question than possibly a request, understanding the difference between Capitalization and lower case denotation of directory files. Looks like only the directory within the app folder are Capitalized ...

JSON Web Token implementation for API developments(out of the box).

Gin and Tonic dispenser

Move bootstrap/cache to storage/framework/cache

It has gone the other way around because it is easier for zero downtime deployment. (Shared storage folder)

Make it real time out of the box, like meteor.js

It would be cool if we get an opt in artisan command, something like php artisan app:type api or php artisan app:type normal and this automatically configures the framework to be ready for the type of application written in the command. (only two types of apps come to mind for now, but I am sure there can be more).

I am talking about some general stuff like: The API won't have views, it will have CORS headers set up, some additional json helper methods similar to the ones in the API development series by Jeffrey. $this->respondNotFound(['data' => $data])

I am thinking something similar to the new Laravel Spark package which is a preset installation for SaaS apps.

+1 for built in CRUD generator like Django admin.

I'm working on something related to multi-tenancy, well multi-database to be exact.

And what I'm trying to understand is how do you normally set the database connection on runtime, some example shows using middleware, but that wouldn't work from an artisan console (which many would use for handling queue, sending emails etc).

https://github.com/orchestral/tenanti/issues/19

A cleaner mail api. Bit more chaining and less callback. Or maybe even something more class based

@topvillas What problems do you have with mailing at the moment? Sending an email is a single operation, why do you need chaining? And the mail component is class-based.

@topvillas Mail is as easy as it gets. And it covers almost every base when it comes to sending mail.

I don't have a problem with mail and yeah, it's easy. I'd just prefer something more along the lines of ...

Mail::template('xxx.xxx')
->with(['x' => '1', 'y' => '2'])
->from('xxxx')
->to('xxxx')
->subject('xxxxx')
->headers('xxx', 'xxxx')
->send()

Or maybe being able to create a mailer class along the same lines as an event or command.

It's something I do anyway with my own class but I reckon it might be something cool to add to the framework

I wouldn't mind seeing what an out of the box solution for token mismatch exceptions would look like (for people who leave forms open for a while, hit submit, then get a whoops).

Currently it's a matter of registering an exception handler, redirecting the user with a regenerated token and asking them to submit again. It would be nice if an elegant solution could be created to handle this.

Would like to see some built-in query caching, like this:

https://gist.github.com/jlem/43f719d668bdf50e4043

I like building out my own APIs in my models, based on interfaces.

Just like you can do

$user->posts
$user->posts
$user->posts
$user->posts
$user->posts
$user->posts

And still only incur one query, I would like to be able to do the same for any arbitrary method - especially those that use the query builder to invoke new queries.

And I strongly want to emphasize that time-based caching is NOT an option here. I am looking for the same registry-based single request caching that "loaded" relations have.

How about less junk, make more simple. People isn't the main idea to query a database and display results, and other crud operations. Keep adding in un-neccessary junk, Laravel will be a 20 gig folder gees.

@jlrdw Sorry but I take exception to that...more simple?! Can you give some examples please? Unless PHP becomes a paint by numbers I struggle to see how it could be any more simpler and any more well documented. To the people who find Laravel complicated I would suggest going back to basics and understanding PHP in its simplest form and the same for OOP.

If you don't want any "unnecessary junk" it may be worth checking out Lumen...

What's considered to be unnecessary junk? Everything that Laravel offers out of the box is useful, unless you are building a static site which does not use many of the features of the framework. It really depends on the application you are building.

Token Authentication will make my life easier

I am new with laravel and maybe its not a good idea... but... yesterday i instinctively tried to update model relation but could not and was very surprised it is not included, everything else in eloquent is very intuitive and easy to memorize and to me, it was very logical that i could do it. Or maybe i can and i just didnt know how.

A little example where userlastview is hasOne relation:

//get topic
$topic = Topic::with('posts','userLastView')->get();

//update last view for current topic
$topic->userLastView->updated_at = Carbon::now();
$topic->userLastView->save();

//maybe even do something like this
$topic->userLastView->saveNew();

Currently it's a matter of registering an exception handler, redirecting the user with a regenerated token and asking them to submit again. It would be nice if an elegant solution could be created to handle this.

@deringer One workaround is to send an ajax request to regenerate the token when click on submit button then submit the form.

To make Laravel read my mind :)

Simple CRUD generator +1

@bugsysha - no way, that would make Laravel a rated R software :P

I'd love to see Laravel as a component based framework, similar to how JavaScript frameworks work. That might require an extra configuration at the start but the user will have a choice what he wants to use and what he needs at the moment.

For example: I don't need queues, jobs and logs for some reason in the application, so I want to turn them off (or they should be off by default). If I need them in the future, I'll turn them on. I believe Lumen works like this with Eloquent and some other components being turned off by default.