To get rid of the /public you can either:
A) Upload vender, bootstrap, and app folders on directory higher than the htdocs or www folder. Then place all files in the public folder to the into htdocs or www.
B) Move files in public directory one folder higher, modify index.php removing the up directory “../” from the includes.
C) Make an .htaccess file in the root something to the effect of
RewriteEngine On
RewriteRule ^(.*)$ public/$1 [L]
Let’s talk a bit about scoped queries in Laravel. First here is a basic Book Eloquent Model with two handy scopes for type and fewerPagesThan.
//Book Model
class Book extends Eloquent {
public function scopeType( $query, $type ) {
return $query->where( 'books.type', '=', $type );
}
public function scopeFewerPagesThan( $query, $pages ) {
return $query->where( 'books.pages', '<=', $pages );
}
}
I often see confusion when we try to use scoping. Some would expect the following to give them back all 'autobiography' books:
Book::type('autobiography'); // This works right? Nope!
But it doesn't. Scoping functions will only refine your query. For instance all the following are great examples of using scoping:
Book::type('autobiography')->get();
Book::with('author')->type('autobiography')->get();
Book::fewerPagesThan(500)->type('autobiography')->get();
When using scopes to refine and filter down which Models to retrieve, you will always need to add a ->get() at the end. This allows you can chain multiple "scopes" onto each other as in the 3rd example. Basically it needs to know when you are done filtering down and when to actually hit the database.
So the 3rd example could be broken down like this to really drive home the point:
$maxPages = 500;
$books = new Book();
$books->type('autobiography');
if( $maxPages )
$books->fewerPagesThan($maxPages);
$opportunities->get();
In every case before the ->get() call $books var is a Eloquent/Builder that is being built up.
After the ->get() call $books var gets overwritten with an Eloquent/Collection that has been filled with our data from the database.
This is a very powerful and flexible to way to scope and filter down models that are in your database. It is better to filter them down with scopes in the DB query than filter down a collection that has already been loaded into memory. Make the your DB do some weight lifting for you. 😉
I had a case where I had an array of model ids, and I wanted to return a collection of these models. That is I had a list of model ids, but it appeared no nice way to get all of them at once. However from the 4.2 API docs you can see that the find() should be able to return either a Model, or a Collection of models.
Naturally to get one model just use:
User::find( $id );
You could loop over the ::find() to pull each one manually, but that will result in multiple unnecessary queries to the database right? Who wants that?
Here is a quite simple approach that Eloquent supports that seems quite obvious after you see it. You can just pass an array of model ids right to the find() function!
$arr = array($id1, $id2, $id3);
User::find( $arr );
This will return a collection of models just as you would expect, no fussing around with loops.  A simple way to get Multiple Specific Laravel Models by Id.