Member Since 4 Years Ago

Experience Points 1,770
Experience Level 1

3,230 experience to go until the next level!

In case you were wondering, you earn Laracasts experience when you:

  • Complete a lesson — 100pts
  • Create a forum thread — 50pts
  • Reply to a thread — 10pts
  • Leave a reply that is liked — 50pts
  • Receive a "Best Reply" award — 500pts
Lessons Completed 20
Best Reply Awards 0
Best Reply
  • start-engines Created with Sketch.

    Start Your Engines

    Earned once you have completed your first Laracasts lesson.

  • first-thousand Created with Sketch.

    First Thousand

    Earned once you have earned your first 1000 experience points.

  • 1-year Created with Sketch.

    One Year Member

    Earned when you have been with Laracasts for 1 year.

  • 2-years Created with Sketch.

    Two Year Member

    Earned when you have been with Laracasts for 2 years.

  • 3-years Created with Sketch.

    Three Year Member

    Earned when you have been with Laracasts for 3 years.

  • 4-years Created with Sketch.

    Four Year Member

    Earned when you have been with Laracasts for 4 years.

  • 5-years Created with Sketch.

    Five Year Member

    Earned when you have been with Laracasts for 5 years.

  • school-session Created with Sketch.

    School In Session

    Earned when at least one Laracasts series has been fully completed.

  • welcome-newcomer Created with Sketch.

    Welcome To The Community

    Earned after your first post on the Laracasts forum.

  • full-time-student Created with Sketch.

    Full Time Learner

    Earned once 100 Laracasts lessons have been completed.

  • pay-it-forward Created with Sketch.

    Pay It Forward

    Earned once you receive your first "Best Reply" award on the Laracasts forum.

  • subscriber-token Created with Sketch.


    Earned if you are a paying Laracasts subscriber.

  • lifer-token Created with Sketch.


    Earned if you have a lifetime subscription to Laracasts.

  • lara-evanghelist Created with Sketch.

    Laracasts Evangelist

    Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.

  • chatty-cathy Created with Sketch.

    Chatty Cathy

    Earned once you have achieved 500 forum replies.

  • lara-veteran Created with Sketch.

    Laracasts Veteran

    Earned once your experience points passes 100,000.

  • 10k-strong Created with Sketch.

    Ten Thousand Strong

    Earned once your experience points hits 10,000.

  • lara-master Created with Sketch.

    Laracasts Master

    Earned once 1000 Laracasts lessons have been completed.

  • laracasts-tutor Created with Sketch.

    Laracasts Tutor

    Earned once your "Best Reply" award count is 100 or more.

  • laracasts-sensei Created with Sketch.

    Laracasts Sensei

    Earned once your experience points passes 1 million.

  • top-50 Created with Sketch.

    Top 50

    Earned once your experience points ranks in the top 50 of all Laracasts users.

28 May
3 years ago

lcopeland left a reply on Laravel 5.2 Multi-Auth With API Guard

I have still been unsuccessful in finding the answer to this problem, and have not been able to find any examples of multi-auth and API guard settings being used simultaneously - I've started a bounty on Stack Overflow if anyone is interested.

24 May
3 years ago

lcopeland started a new conversation Cannot Get Any Auth Guards To Work

I thought this was a more specific question, but I've realized I cannot get any guards to work in my installation of 5.2. Is this feature still under development or something? I was excited to use L5.2's new features but now that I've installed it I can't get a single one to work. Has anyone gotten this feature to work who could comment on their experience? Am I missing a step here?

My middleware call:

Route::group(['middleware' => 'auth:exampleguard'], function () {
    //various routes

My declaration of guards in auth.php

'guards' => [
        'web' => [
            'driver' => 'session',
            'provider' => 'users',

        'api' => [
            'driver' => 'token',
            'provider' => 'otherusers',
        'exampleguard' => [
            'driver' => 'session',
            'provider' => 'users',

When I call auth:exampleguard, I get

InvalidArgumentException in AuthManager.php line 86:
Auth guard [booger] is not defined.

And if I try calling auth:api, I get behavior as if I was just using the regular web guard. Is there some other thing I need to initialize before calling guards actually, well, calls the guards? I haven't seen that in the tutorials I've seen so far but I'm pretty baffled here.

lcopeland left a reply on Laravel 5.2 Multi-Auth With API Guard

Nobody have any ideas? I've seen multiple tutorials on both multi-auth and api guards, but none of them combine the two - I don't know where the mix could be going so badly wrong.

23 May
3 years ago

lcopeland started a new conversation Laravel 5.2 Multi-Auth With API Guard

Hi all. I'm trying to get a multi auth system working where Users can log in via the normal web portal, but a separate database of entities called Robots can also log in via an API guard style token driver. I'm very excited about how easy 5.2 is supposed to make this but I can't seem to get it working - no matter what I do, the setup I have is not directing my auth guard to the correct Robot database and keeps trying to authenticate these requests as Users via tokens (which fails, because users don't have tokens).

Can someone help me find where I've gone wrong?

I've started by putting together a middleware group in Kernel.php:

'api' => [

This uses settings in config/auth.php

'guards' => [
        'web' => [
            'driver' => 'session',
            'provider' => 'users',

        'api' => [
            'driver' => 'token',
            'provider' => 'robots',

    'providers' => [
        'users' => [
            'driver' => 'eloquent',
            'model' => App\User::class,
        'robots' => [
            'driver' => 'eloquent',
            'model' => App\Models\Robot::class,

The middleware gets called in routes.php

Route::group(['middleware' => 'api'], function () {
    Route::get('api/request', 'API\[email protected]');

It uses this model:


namespace App\Models;

use Illuminate\Database\Eloquent\Model;
use Illuminate\Contracts\Auth\Authenticatable;

class Robots extends Authenticatable
    protected $fillable = [
    protected $guard = 'Robots';
    protected $hidden = [

Quite the web of files, and I'm lost. Any ideas? }

18 Aug
3 years ago

lcopeland left a reply on Adding Foreign Keys With Migrations

Figured it out, I hadn't declared some of my foreign key fields to be indexes, ie this:


vs this:


I did end up having to manually edit the order of my migrations anyway, though, since the tables could no longer delete in the order they were declared due to the new constraints. I'm not sure how you could do it without needing to "hack" the version control system - re-declare all your tables, maybe?

lcopeland left a reply on Adding Foreign Keys With Migrations

I figured out the first part - needed to include the ->index() method when declaring my foreign keys - but I'm still running into all sorts of errors regarding migration order. Laravel just cannot keep it straight what tables it's supposed to delete first, and every time the migration system fails (which is constantly) it requires a ton of manual deletion and a composer dump-autoload just to get basic functions up and running again.

Does this idea of database version control just completely fall apart once foreign key constraints get involved?

lcopeland left a reply on Adding Foreign Keys

@helmerdavila, I understand that the tables need to be created first - they're already in the database as a result of older migrations. My question is whether it is possible to add foreign keys afterwards as a part of using migrations as version control, rather than inserting it in the original table declarations and having to hack the timestamps on the migrations so that everything executes in the correct order.

(If all else fails, I'll probably take this second option - I honestly would prefer if the migration system would just let us define our own execution order so we could use it as a schema definition rather than version control, which I think it does a pretty crappy job of, especially for cases like this.)

@veve286 updated all my tables to have unsigned fields, but I'm still getting the exact same error. I don't think that's it.

17 Aug
3 years ago

lcopeland started a new conversation Adding Foreign Keys

I'm having trouble adding foreign keys to my database in laravel using migrations. Since migrations can't be reordered, I can't put them in my table creation migrations directly without needing to hack the times so that things get created in the right order. However, I'm not having any luck creating them after, either, and all my searches have turned up is people (somewhat unhelpfully) suggesting that I put them in the create methods.

Here's the table insert I'm trying to use: public function up() { Schema::table('jobs', function($table) { //NOT including a foriegn key constraint here for customer. They can rechose. $table->foreign('created_by_user_id')->references('id')->on('users'); $table->foreign('customer_id')->references('id')->on('customers'); }); }

Anyone got ideas?

27 Jul
3 years ago

lcopeland left a reply on Database To View - How To Structure?

Sorry if this is a dumb question, but where is the SQL in your above model example? Would it in turn reference another class like an Eloquent model for that, or would it acquire table data itself in the construct method?

Also, I thought that returning views from post methods was bad practice due to redirect woes and trying to keep HTTP verbs straight (post should only handle the posting, not "getting" the results to show back to the user)?

lcopeland started a new conversation Database To View - How To Structure?

As a relatively new, self-taught coder, I'm feeling overwhelmed with trying to structure my application properly. I've been watching a lot of laracasts, but I still don't feel like I have a good feel for where the responsibilities of my application are.

My task is conceptually simple - I have to receive an id from a user submitted form, grab a bunch of entries from my database sorted by that identifier, perform a bunch of data analysis functions on them (averages, sums, etc), and then return all that data in a view.

What's the convention for where each task happens? I'm currently doing the following: - receive user input in a post method in my controller and validate it - pass the identifiers to the methods of a model class that fetches from the database and performs the analytics. I'm using query builder rather than Eloquent right now because I don't understand what Eloquent offers other than some very minor simplifications in syntax and a couple auto insertions. - Format the returned data in the controller and create an array of data to send to the page - Send that data to a get method in the controller that calls the view.

What changes should I make to this pattern? I'm not that worried about distancing the application from the database, since what I'm building would likely be thrown out altogether if the database were ever to change. But I am concerned about making it encapsulated enough that other developers can understand what I'm doing.

24 Jul
3 years ago

lcopeland left a reply on Why Controller=entity, Rather Than Controller=verb?

Nah I'm doing it even worse than that. My upload controller doesn't just handle the article upload, it handles ALL the uploads, for every type of entity. I posted this same question to stack overflow and their answer was that though this can work in a technical sense, it's not object oriented and doesn't follow the basic principles of encapsulation.

My real question now is how to best refactor my code. I've never fully gotten what the high level structure of a user-entry application is really supposed to look like from laracasts, even though I understand the low level mechanics alright. Basically, I have a form on my site where a user can submit a really huge variety of things at once - a project, subproject, article, uploaded file, and series of note fields all at the same time. Using a single UploadController that just handled everything was easy, because I could just route all the different entries to their corresponding methods without any bells and whistles. But I'm increasingly getting the sense that in my newbie ignorance, I've made some kind of huge mistake that will haunt me in the long run.

What's a good way to handle this kind of multi-entry form? Have one EntryController that handles the view generation and submission, and then calls a bunch of other controllers (ProjectController, FileController) to do the insertion logic? What's the ideal structure for delegating this diverse set of tasks to respond to a single user action?

lcopeland started a new conversation Why Is It Controller=entity, Rather Than Controller=verb?

I'm curious about the design philosophy of resource controllers, where you define a new controller for an individual entity, say, "project" or "article", and then provide methods based on verbs (create, edit, update, destroy, etc).

In the context of my application, I feel like I get more utility by having a controller for each verb itself - say, "UploadController" - which is then responsible for handling that operation for every entity that needs it. This allows me to share tasks like validation between similar entities, and I don't have to include operations (say, update on a read-only entry) for entities that don't need them. It also lets me call a single controller for pages where I'm creating many different kinds of entities at once, such as generating a hierarchy of entries like project->subproject->article all from one form.

But am I missing some huge disadvantage to this? Why is the controller=entity & method=verb structure so popular, vs controller=verb & method=entity?

22 Jul
3 years ago

lcopeland left a reply on Moving Laravel To Production - Is It Possible?

Gah, I ended up figuring out the 404 issue, it was a typo in the apache2 .conf file that was preventing mod_rewrite from taking effect on the URLs. Now to just figure out all the rest of them!

lcopeland left a reply on Moving Laravel To Production - Is It Possible?

My current issue is getting these 404 errors from my controllers. Interestingly, while trying to copy over my project files into an existing laravel install, I noticed that the Welcome controller (with the logo/cheesy quote) would work just fine... but I can't get any of the other ones to do the same. Is this another permissions issue or something?

lcopeland left a reply on Moving Laravel To Production - Is It Possible?

@HFH I've run into that a couple times but I've resolved it the way you've said. But not all of my WSODs have been based around storage, and often they clear up only to reveal another issue...

Thanks for that cache clear command, though. I didn't know about that one. However, it does strike me as strange that the caching issues only showed up after I moved the installation - shouldn't it stand to reason that they should have been present on my development server as well?

lcopeland started a new conversation Moving Laravel To Production - Is It Possible?

I'm having a lot of trouble getting my Laravel 5 development project onto a different server (Ubuntu LTS). I've tried moving the files with git, FTP, and even a thumb drive, but no matter how many times I move things around and change settings, I can't even get the most basic pages of my site to load properly. Just a few of the issues I'm seeing:

  1. untraceable White Screens Of Death
  2. caching issues where month old versions of my routes and views are called instead of the real ones
  3. permission complaints from composer and artisan even when the entire directory is given full permissions
  4. 404 errors from my controllers, even when the routes.php seems to be working fine.
  5. generally, the whole routes->controllers->views structure seems to fall apart when I move my filesystem to a different computer.

Does anybody have a workflow for moving laravel installs that they could share? What files to copy, what should just be installed locally, and what tips and tricks to keep in mind? I've been working on this for more than two days now and making no progress, and the particularities of this framework when it comes to installation are driving me up the wall.


lcopeland left a reply on Old Version Of Homepage Shown... But It Doesn't Exist Anymore!

Nuking the server didn't help - it's still here! And git isn't even here this time - I haven't installed it on the new machine.

I'm finding this issue particularly weird because Artisan shows the corrects routes using route:list, and I can't access old routes that I've since deleted, even though the view I'm seeing in the browser has links to them. So it seems like it's only my views directory that's somehow being superimposed with an old version.

Has anybody ever run into this problem before?

21 Jul
3 years ago

lcopeland started a new conversation Old Version Of Homepage Shown... But It Doesn't Exist Anymore!

I've been trying to get my laravel project ported over to another server on my network (a temporary "production" server so my co-workers can use the web tools I've created). After several unsuccessful attempts to do this via git, I've given up and gone back to Filezilla to just get the whole thing on there via FTP.

However, I'm absolutely baffled by a problem I'm now having with the installation - after uploading the files, I can go on the server and check everything via the linux bash and they're fine - all up to date, correct configuration, etc.But when I visit the site itself, I'm seeing an old version like the one I tried to put on with Git.

Thing is, the files for that don't even exist anymore! I deleted the old repo and uninstalled git too. It doesn't appear to be the whole site, and the style is all messed up because it isn't calling any of the stylesheets properly. But the fact remains that to even be bringing it up, it would have to reference both a routes.php file and home.blade.php that don't exist. Apache is setup just fine, I've tried clearing the browser cache, and the problem exists across multiple computers. If I can't figure it out soon I'm just going to nuke the whole production server and reinstall from scratch... or have an exorcism.


lcopeland left a reply on Changing Migration Order

@jaewun ok, that helps me out a bit in understanding why they're the way they are. I was thinking about them more as a structural tool than version control.

That being said, I'm not sure I actually really want version control. I've been using migrations mostly to have more direct and easy access to my database structure, and to be able to easily rollback changes when I'm altering my table structure. I don't need backups of every bit of experimentation I do, and I kind of like the convenience of having one file per table that I can micromanage. Are there any alternative packages to migrations that would offer more functionality as a design/seeding technology?

20 Jul
3 years ago

lcopeland left a reply on Changing Migration Order

Bleh, really? That seems pretty inconvenient, I'm surprised a more direct management system isn't there. Is this just not a problem people usually run into? Is my workflow causing me to have this issue where I shouldn't?

lcopeland started a new conversation Changing Migration Order

I'm getting a "General error: 1005 Can't create table" when I try to migrate my tables after making creating some foreign key constraint changes.

I understand why the errors are happening - my current migration order isn't creating my parent tables before the child ones, and so my foreign keys are getting all messed up because the tables they depend on don't exist yet. But it seems a bit hacked (and inconvenient) to change the migration order by arbitrarily changing the timestamps of each migration to make them execute in the proper order.


Is there a good Artisan tool to change the order in which migrations are applied? I haven't found anything online but people just making up fake timestamps in the order they want.

14 Jul
4 years ago

lcopeland left a reply on Manually Entering Users With Auth

Ok, thanks for the advice guys. I'll make my own registration controller and implement the changes to Auth.

13 Jul
4 years ago

lcopeland left a reply on Manually Entering Users With Auth

Would I lose anything security or organization wise by doing that compared to using the Auth controller?

lcopeland started a new conversation Manually Entering Users With Auth

I'd like to change the registration system on my site so that only existing users can add new ones. Ideally, a signed in user could simply access a form while signed in to their account and enter a new user to the database, without any changes to their session status.

I'm wondering if I can still use the Auth controller for the hash and recovery features, but I would need to make some changes: the registration page would need to be accessible by users who are already logged in, and on submission, the user should stay logged into their own account rather than being signed in to the one they just created.

Is it worth doing this with Auth, or should I just make my own controller? If it is worth it, what kinds of steps would I need to take in order to change the registration process in this way?

01 Jul
4 years ago

lcopeland left a reply on Resources: Always? Or Sometimes?

I can outline the problem specifically; I thought talking about this in abstract terms might be better but I think its just being confusing.

What we're doing is tracking masonry bricks as they are laid into a wall. These bricks are laid in the thousands to hundreds of thousands per job, and are sorted as such: brick-> course (a line of bricks)-> wall -> day-> project -> job. Each level has unique information associated with it, not just compiled stuff.

My point is that I'm never actually editing or dealing with the lower levels individually - we upload them in massive batches by file. What's more is that they're never edited or shown individually, but huge collections of bricks or courses are sorted by say, wall or job, to show average data. So while I need the ability to create bricks in the DB, I have no use for showing, editing, or otherwise managing them individually. If I'm going to change something, I would delete the entire collection at the wall or project level and replace it with updated data. So the idea of having restful controllers for every level of this chain seems very wasteful to me, unless there's a very compelling reason to keep them for reasons I'm not aware of. I figure there totally could be, though, so that's why I'm asking :)

I hope that clears things up.

lcopeland left a reply on Resources: Always? Or Sometimes?

I guess the point I'm making is that we're pretty frequently going to be making entries that require moving up our entire parent/child chain. The system I'm making is all about data analysis, not user-created content, so these models are more about sorting and categorizing data than actually ever being displayed by themselves. Creating an entirely new job, will all the sublevels it requires, will be a very common task - on the other hand, actually viewing the data of just one cycle or subcycle will never happen - they will always be congregated in groups, usually of a hundred or several thousand, to form averages and statistical representations.

If a cycle is never going to be shown by itself, or edited by itself, or updated by itself, why should it have these methods?

lcopeland left a reply on Resources: Always? Or Sometimes?

If I were creating a subcycle file for a new job, to follow my example, it would require that I:

  1. insert the subcycle
  2. jump to a new controller to create the cycle
  3. jump to a new controller to make the project etc etc.

Whereas, if I just had a UploadsController, I would simply call the subcycle method, then the cycle one, then the project one, etc.

lcopeland started a new conversation Resources: Always? Or Sometimes?

I have a question about general RESTful conventions and best practice for using things like the Laravel resource route.

I'm working in an application that stores data within a lot of hierarchy levels: subcycles are within a cycle are within a day are within a project are within a job, etc etc. When I make a new entry on the lowest level, it requires either selecting the correct upper levels, or creating a whole new hierarchy starting from the highest category.

Now, working from within the conventions used by Jeffery in his videos, that would mean that every level of the system would have its own controller, with all the store/edit/show methods available from the resource call. But that would mean that if I'm starting a new job, I'd be calling 5 different controllers in one form! And it seems like each one would be pretty wasteful, since the higher levels exist mostly to record and sort timing, and I don't need to have their information displayed or edited all that frequently.

It seems more efficient to me to have a single controller for storage, say, StorageController, that contains the storage code for all my different levels as separate methods. That way I can just call the methods in order as I create a new entry, and it's easy to edit and cross reference code rather than having to hop between controller files all the time if I want to compare.

I'm a real newbie when it comes to this kind of stuff though and I don't know any of the arguments to the contrary. Are there some really convincing reasons for me to stick to the Restful conventions? Or is this a valid exception to the convention?

30 Jun
4 years ago

lcopeland started a new conversation Clumsy Multi-page Forms

I'm a beginner to Laravel, and also to front-end oriented programming (most of my background is in database management). I'm attempting to put together a multiple page form that allows users to move through a hierarchy of data:

  1. on the first page, they can select a project or create a new one,
  2. on the second they select a subsection of that project (or again, make a new one)
  3. on the third page they can perform file uploads or specific tasks for that subsection.

My hacked-together way of doing this was simply to have each page after the first be a POST route that grabs the identifying data of the previous step to generate the correct select fields for the view and populate the database properly. However, after some research I've learned that directly calling views from a post route is a clumsy way of doing things (mixing up GET and POST methodology), made especially evident by the fact that validation error redirects cannot work with post routes. Thus, if the user ever messes up in the form, rather than being redirected to the last stage with a list of errors, they end up with a Method Not Allowed exception.

What is a better (RESTful) way of achieving this kind of multiple-page form? I'm not very good at front end stuff and would rather avoid Ajax if I can.

Here's some of my code as it stands:

route file:

Route::get('newentry', 'NewEntryController@index');

example method for a form page

public function selectday()
            //get post from job form and validate
            $request = Request::all();
            $job_id = intval(Request::get('job_id'));
            //create data variable, pass job_id for hidden field
            $data = [];
            $data['job_id'] = $job_id;
            //apply ruleset
            $rules = array(
                'job_id'    => 'required'
            $validator = Validator::make($request, $rules);
            if ($validator->passes()) {
                //get the subset of days
                $data['days'] = DB::table('daily_runs')
                    ->orderBy('id', 'asc')
                return View::make('')->with('data', $data);
            } else {

                return Redirect::to('newentry/selectjob')->withInput()->withErrors($validator); //this redirect will not work. 
        } //end selectday

This code will work if the user makes no mistakes (as I mentioned, if they mess up the validation redirect will throw a Method Not Allowed exception) but from what I'm hearing I'm approaching it with poor coding practice. What steps could I take in the controller/view structure to make it better?

23 Jun
4 years ago

lcopeland left a reply on Starting With Front End

So, my current issue is that both Bower and Node are trying to install their dependency directories in my main folder, and it looks like this is the root of all the other problems I'm having. Bower I know can be redirected to install to the resources folder through a .bowerrc file, but I'm not sure what the equivalent for Node is. And once I do that, are there other tasks I should perform besides just deleting the erroneous bower_components and node_components directories they created? Should I try uninstalling those components first?

lcopeland left a reply on Starting With Front End

Well, in trying to get this front end up and running I have successfully destroyed my entire project. Bower still won't install even basic directories for Jquery, Gulp runs a "Cannot find module 'laravel-elixir-browser-sync'" error when I try and run it, and now even Netbeans refuses to sync the project due to errors from the Less compiler. Funnily enough, the site still loads ok, but the entire page layout has physically moved down on the browser page by about an inch.

Does anybody have some good resources for salvaging code and starting from scratch?

22 Jun
4 years ago

lcopeland left a reply on Starting With Front End

Thanks guys! These look great for starting with front end tech - but do either of you happen to have anything for installing the base frameworks on laravel 5 specifically? Bower and Gulp are giving me an awful lot of trouble with their installations, and I think it's mostly because they're simply not set up correctly in the file hierarchy. Any good resources for that?

lcopeland started a new conversation Starting With Front End

Hey guys,

I'm just starting out with front end development, virtually from scratch. I've did a little bit of CSS and Javascript back in school, but nothing organized, and not with the assistance of any frameworks.

I'd like to get started on learning and experimenting with the front end on my current Laravel 5 project, but I'm a little frustrated by the current front end beginner series which seems to be pretty out of date - none of the boilerplate files or structure that Jeffery uses in his video seems to still be around in the current install. Services like Bower and Gulp seem great to me in theory, but I'm having a lot of trouble integrating them in practice.

Does anyone have any pointers to some good tutorials on getting a standard template and framework based front end working on a Laravel 5 install? I'm not set on any particular technology - if the community's moved on to some other new stack of front end resources, I'd be happy to try that too! I'm just looking for something standard and more or less noob friendly so I can learn by experimenting.

Anybody have suggestions?

08 Jun
4 years ago

lcopeland started a new conversation Handling Automated HTTP

Is there an easy way to create controllers for handling secure HTTP requests from an automated system that can't handle user interfaces? It seems like there are some handy tools in the included auth tools that come with the laravel installation, but I'm not sure how to separate the internals from their user interface focus. Anybody have any suggestions?

lcopeland left a reply on Having Trouble Installing

Figured it out - it was a combination of improperly set permissions on the Public file, and an incomplete path route in laravel.conf that wasn't accounting for the /html directory. A lesson to be careful of copy and paste problems from all the sites that just work out of /www instead of using /html. It's fixed now, thanks folks!

05 Jun
4 years ago

lcopeland started a new conversation Having Trouble Installing

Hi, I'm a relative newbie to web development and a total newbie to laravel. I'm having some trouble installing the framework on my Ubuntu 14.04 LTS - we're doing development on a private box on our local network, and I'm finding the installation instructions on the homepage to be pretty insufficient in terms of how much information they actually provide.

I've tried running some tutorials I've found online on the topic, but thus far I think I've only succeeded in screwing things up. I have composer set up, but I can't figure out how to manage the directories and permissions in /var/www/ since most of the tutorials seem to be directed to accessing the site off your own machine, which isn't what I'm doing. I'm also not sure how to set up the Apache2 conf files since so far I've only been getting 404s or the actual directory of Laravel.

This is turning out to be one of the most frustrating framework installations I've ever had to deal with - I'd love to hear it if someone's done something similar and has advice!