Not Secure Warnings are Coming to Chrome 56 – Add an SSL to prevent it

Chrome announced back in September that they want to move towards a more secure web, and one they plan to accomplish this is by marking HTTP pages that collect passwords or credit cards as non-secure.

Chrome 56 will be the first version that includes this change and it’s due out this month. Now is the time to upgrade your site to HTTPS if it isn’t already. Chrome is currently the most popular browser with 56% market share, based on netmarketshare, and this change will affect any site that has password registration and of course that accept credit cards.

If you need help adding an SSL there are many options available today to make it easier than ever before:

  • Let’s Encrypt – Free, automated, and open Certificate Authority
  • Cloudflare – Free plan with shared SSL and added DDOS protection.
  • Laravel Forge – Starting at $15 a month and works with DigitalOcean, Linode, & AWS and includes automatic support for Let’s Encrypt.
  • NameCheap – SSL Certificates starting at $9 a year.

To test out your sites before Chrome 56 ships you can open up the hidden Chrome flags preferences and change this setting manually and restart.

To get to this setting page just open Chrome and visit this URL: chrome://flags/#mark-non-secure-as

Source: Laravel News

This is Laravel Mix

One issue, with any build tool, is that for each new project, you have to reproduce the entire setup again and again. Wouldn’t it be useful if we could optimize for the 80% of folks who simply want general ES2015 + module compilation, some CSS preprocessing, and possibly a few other common tasks? And for the remaining 20%, well, they should have access to the underlying configuration file, so that they may tweak it to their project’s exact needs. Well, that’s exactly what Laravel Mix does for you.
Source: Laracasts

SameTime: Group Text Reminders App Built on Laravel

SameTime is a new web app by Tommy and Joey Marshall that will automatically send a text message to you and a group of eight friends on a designated schedule.

“We’d lament on a weekly basis how we wanted to wake up early or work out after work, but would keep sleeping in and watching reruns of Seinfeld.”, Tommy said, “We needed to keep each other accountable, but sending that “sooo did you do X?” text at certain times during a day wouldn’t happen because we’d either both forget or didn’t want to be annoying (accountability is hard). “

SameTime is perfect for anything that you and your friends want to be reminded about, workout, read, have lunch, etc. Another nice feature is everyone has 10 minutes to write a response that gets sent back to the group; this creates accountability for reminders like waking up and also prevents your group message from annoying you all day like most group texts do.

The app is free to use with no account needed and it’s built on Laravel making heavy use of its queueing system.

Source: Laravel News

Resuming Subscriptions

In this episode, we’ll update our API to allow users to resume their subscriptions. This will require that we add a resume method to the Subscription class. Stay tuned to the end for a bit of homework as well.
Source: Laracasts

Testing for Grace Periods

We need to offer users the ability to resume recently canceled subscriptions. But before we get to that point, we must first learn how to determine if a user is currently on their grace period. Let’s tackle that in this episode!
Source: Laracasts

2016 Laravel Survey Results

Back in September, we partnered with LaraJobs to run a Laravel survey to see what types of projects people are taking on with Laravel as well as get some feedback on what the Laravel community could be doing better. The results ended up with over 1,600 submissions and some interesting insights.

You can see the complete results on this 2016 Laravel Survey Results page and thanks for everyone who took the time to fill it out.

Source: Laravel News

Webpack Config From Scratch

You’ve learned a bit about vue-loader already; however, for learning purposes, let’s build up a Webpack configuration file from scratch, so that we can begin extracting and importing modules. This will give you a solid review of the fundamentals, while also providing an opportunity to review just how powerful (yet initially confusing) all this stuff can be. Don’t worry: in the next episode, I’ll show you some options to simplify new projects that use Webpack.

You may review the completed webpack.config.js file from this lesson on Github, and can learn more about Webpack’s concepts on their website.
Source: Laracasts

Automatic Facade’s coming to Laravel 5.4

Coming in Laravel 5.4 is a new feature that will allow you to use any class as a Facade on the fly. If you are not familiar with Laravel Facades here is what they are:

Facades provide a “static” interface to classes that are available in the application’s service container. Laravel ships with many facades which provide access to almost all of Laravel’s features. Laravel facades serve as “static proxies” to underlying classes in the service container, providing the benefit of a terse, expressive syntax while maintaining more testability and flexibility than traditional static methods.

Automatic Facade Example

In Taylor’s example from the announcement here is how it works:

namespace App;

class Zonda 
{
    public function zurf()
    {
        return ‘Zurfing’;
    }
}

Then, in the routes or controller:

use Facades {
    AppZonda
};

Route::get('/', function () {
    return Zonda::zurf();
});

Source: Laravel News

1 2