royksoft

royksoft

Member Since 7 Months Ago

Experience Points
10,020
Total
Experience

4,980 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
94
Lessons
Completed
Best Reply Awards
0
Best Reply
Awards
  • start your 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-in-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 Created with Sketch.

    Subscriber

    Earned if you are a paying Laracasts subscriber.

  • lifer Created with Sketch.

    Lifer

    Earned if you have a lifetime subscription to Laracasts.

  • evangelist 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.

Level 3
10,020 XP
Sep
25
3 weeks ago
Activity icon

Replied to Alternative To "new Up” Objects In Other Objects

Thankyou, the videos from that point are really helpful, hopefully I'll start to understand them soon.

I'm not so clear on when to reach for these techniques, or how to pass parameters into objects created in / by the container, but I'm sure I'm getting closer to the "lightbulb" moment!

Thanks

Sep
24
4 weeks ago
Activity icon

Started a new Conversation Alternative To "new Up” Objects In Other Objects

I'm a new developer just getting started with testing.

I see in a lot of places that it's a code smell to "new up” objects in other objects.

I'm wondering what are the alternatives. Logically I can use dependency injection, but that requires that I new up the object in the level above, which is probably also in another object.

Are controllers (being the "top of the tree") the only places that should I should instantiate object to keep things unit-testable?

Could any folk share some googlable jargon that will get me a little further towards understanding.

Thanks!

Sep
11
1 month ago
Activity icon

Replied to Local Package On Localhost And Github Version On Stage & Production

OK, I've made some progress, and I can phrase the question better now.

There seem to be 3 options:

  1. Configure to use composer to autoload directly from the local folder. Here's composer.json:

     "autoload": {
         "psr-4": {
           "App\": "app/"
           "PackageOfInterest\": "local-packages/packageOfInterest/"
         }
       }
    
  2. Configure to use the local folder as a repository through composer (which puts it in the /vendor directory on composer update. Here's composer.json:

     "repositories": [
         {
           "type": "path",
           "url": "local-packages/packageOfInterest"
         }
       ]
    
  3. Configure to use the github package as a repository through composer (again, putting it in the /vendor directory. Here's composer.json:

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

So, my new question:

Is it possible to configure the same composer.json file to prefer (1) in local development, and fall-back to (3) in production?

Thanks!

Activity icon

Started a new Conversation Local Package On Localhost And Github Version On Stage & Production

Hi,

I've forked an un-maintaned package from github, to use in two of my laravel projects.

I'd like to find a way to use the local package files within the projects locally (for speed of development), and then for the projects to pull the github version in staging and production (on forge).

The local package files are in a folder sym-linked into my projects called /local-packages/packageOfInterest.

Is there any way to do this? Obviously when deploying my project I have to make sure that my local package updates are also pushed to github, but that's easy to do. The benefit of using locally is the speed of development and ease of testing with both projects.

Tried 2 things so far:

  1. I can use the local package locally, by configuring packages.json appropriately, but of course it failed when pushing to production, because the local packages are not there. I don't really want to combine the package files into the projects.

  2. I can run the local project from the github repo. But then when I need to make a change to the package I can't test it locally without pushing to github and then doing composer update. That's slow (not to mention the messy github history when I'm fixing typos).

Does anyone have any pointers? Thanks!!