Creating Queueable Jobs

Next, let’s create the two queueable jobs that we use for encryption and uploading to S3:

php artisan make:job EncryptFilephp artisan make:job MoveFileToS3

This will create two files in app/Http/Jobs : EncryptFile.php and MoveFileToS3.php. These jobs will accept a param in the constructor, which represents the filename. We add the functionality of encrypting and uploading to S3 in the handle method. This is what the two jobs look like:

<?php

namespace App\Jobs;

use Illuminate\Bus\Queueable;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Foundation\Bus\Dispatchable;
use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Queue\SerializesModels;
use SoareCostin\FileVault\Facades\FileVault;

class EncryptFile implements ShouldQueue
{
 use Dispatchable, InteractsWithQueue, Queueable, SerializesModels;

 protected $filename;

 /**
 * Create a new job instance.
 *
 * @return void
 */
 public function __construct($filename)
 {
 $this->filename = $filename;
 }

 /**
 * Execute the job.
 *
 * @return void
 */
 public function handle()
 {
 FileVault::encrypt($this->filename);
 }
}<?php

namespace App\Jobs;

use Exception;
use Illuminate\Bus\Queueable;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Foundation\Bus\Dispatchable;
use Illuminate\Http\File;
use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Queue\SerializesModels;
use Illuminate\Support\Facades\Storage;

class MoveFileToS3 implements ShouldQueue
{
 use Dispatchable, InteractsWithQueue, Queueable, SerializesModels;

 protected $filename;

 /**
 * Create a new job instance.
 *
 * @return void
 */
 public function __construct($filename)
 {
 $this->filename = $filename . '.enc';
 }

 /**
 * Execute the job.
 *
 * @return void
 */
 public function handle()
 {
 // Upload file to S3
 $result = Storage::disk('s3')->putFileAs(
 '/',
 new File(storage_path('app/' . $this->filename)),
 $this->filename
 );

 // Forces collection of any existing garbage cycles
 // If we don't add this, in some cases the file remains locked
 gc_collect_cycles();

 if ($result == false) {
 throw new Exception("Couldn't upload file to S3");
 }

 // delete file from local filesystem
 if (!Storage::disk('local')->delete($this->filename)) {
 throw new Exception('File could not be deleted from the local filesystem ');
 }
 }
}

As you can see, the EncryptFile job is simple — we are just using the FileVault package to encrypt a file and save it into the same directory, with the same name and the .enc extension. It’s exactly what we were doing before, in the HomeController’s store method.

For the MoveFileToS3 job, we are first using the Laravel putFileAs method that will automatically stream our file to S3, following the same directory convention as we had on the local filesystem.

We are then calling the PHP gc_collect_cycles function, in order to force collection of any existing garbage cycles. In some cases, if we don’t run this function then the file will remain locked and we won’t be able to delete it in the next step.

Finally, we are deleting the file from the filesystem and throwing Exceptions if the upload or the delete processes fail.

I want my site to show as robindirksen.nl and not www.robindirksen.nl in the search results or ay other place, but how do you handle the removal of www in your application so you don’t lose your visitors?

There are a few ways how you can solve this. I recommend the server side (for example nginx or htaccess) above application based redirects (for example Laravel) because these will also redirect static files to the non-www version of your site.

Nginx configuration

You can make a new configuration in your configuration directory, this is usually in the /etc/nginx/conf.d/ directory. You can make a file (for example: /etc/nginx/conf.d/redirect.conf) and place the following configuration:

server { server_name www.robindirksen.nl; return 301 $scheme://robindirksen.nl$request_uri; } 

This will redirect everything that requests www.robindirksen.nl to the non-www version, robindirksen.nl.

.htaccess file

In a Laravel application you will find a .htaccess file in your public folder. Here you can add the following code to redirect the visitors.

RewriteEngine On RewriteCond %{HTTP_HOST} ^www.robindirksen.nl$ [NC] RewriteRule ^(.*)$ http://robindirksen.nl/$1 [R=301,L] 

To enable redirect you have to install mod_rewrite to the server and switch RewriteEngine to on.

Laravel Application

One of the ways to do this is by making a middleware and enable this to all your requests.

<?php namespace App\Http\Middleware; use Closure; use Illuminate\Support\Facades\Redirect; class RedirectToNonWwwMiddleware { /** * Handle an incoming request. * * @param \Illuminate\Http\Request $request * @param \Closure $next * @return mixed */ public function handle($request, Closure $next) { if (substr($request->header('host'), 0, 4) == 'www.') { $request->headers->set('host', 'robindirksen.nl'); return Redirect::to($request->path()); } return $next($request); } } 

After you’ve made your middleware you need to add it to the requests, this can be done by adding it to all of the requests (web, api etc) or only the web.

To add it to all of your requests, you can add the middleware (\App\Http\Middleware\TrustProxies::class) to the $middleware array, then it will look sometime like this:

<?php namespace App\Http; use Illuminate\Foundation\Http\Kernel as HttpKernel; class Kernel extends HttpKernel { /** * The application's global HTTP middleware stack. * * These middleware are run during every request to your application. * * @var array */ protected $middleware = [ \App\Http\Middleware\CheckForMaintenanceMode::class, \Illuminate\Foundation\Http\Middleware\ValidatePostSize::class, \App\Http\Middleware\TrimStrings::class, \Illuminate\Foundation\Http\Middleware\ConvertEmptyStringsToNull::class, \App\Http\Middleware\TrustProxies::class, ]; 

It’s also possible to only add it to the web-group requests (and not your api endpoints). With a basic Laravel 6 installation it will be added to all the requests made to the routes defined in routes/web.php.

<?php namespace App\Http; use Illuminate\Foundation\Http\Kernel as HttpKernel; class Kernel extends HttpKernel { /** * The application's route middleware groups. * * @var array */ protected $middlewareGroups = [ 'web' => [ \App\Http\Middleware\EncryptCookies::class, \Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse::class, \Illuminate\Session\Middleware\StartSession::class, // \Illuminate\Session\Middleware\AuthenticateSession::class, \Illuminate\View\Middleware\ShareErrorsFromSession::class, \App\Http\Middleware\VerifyCsrfToken::class, \Illuminate\Routing\Middleware\SubstituteBindings::class, \App\Http\Middleware\HttpsProtocolMiddleware::class, \App\Http\Middleware\RedirectToNonWwwMiddleware::class ], 'api' => [ ... ], ]; } 

Please pay attention, when you have likes to static files (like images, css or javascript) you have to enable htaccess or nginx redirects, otherwise those keep be served from the www version. This happens because the static files won’t boot the framework what means it don’t received the redirect.

Which status code do I need to use?

Last but not least, which redirect http code do you need to use? It’s really simple, you want to permanently show your non-www site in the results, then you redirect with a 301 status code.

Sometimes it can happen to only redirect the users for a specific time to another url, then you want a temporarily redirect. This can be done by redirecting with a 302 status code.

Diana Prince faces off against two new formidable foes and reunites with an old love in the hotly anticipated first trailer for Wonder Woman 1984, with Gal Gadot reprising her titular role. Director Patty Jenkins unveiled the trailer today at Comic Con Experience (CCXP) in Sao Paulo, Brazil.

Inspired by the comic book heroine created by William Moulton Marston in the 1940s for DC Comics, Wonder Woman made her big-screen debut in the DCEU with 2016’s Batman v Superman: Dawn of Justice, followed by 2017’s Justice League. The first fell short of box office expectations; the second bombed outright. So when Jenkins took on Wonder Woman’s origin story, she deliberately departed from the grim humorlessness and dark sensibility of those earlier films, bringing a brighter energy and wit to her tale, along with the usual action. That vision paid off: Wonder Woman went on to gross $821 million worldwide and earned critical raves, making it the most successful of the DCEU films thus far.

Jenkins first broached the possibility of a sequel shortly after the first film’s release in June 2017, and principal photography began a year later. It has been described as a standalone film rather than a direct sequel, “in the same way that Indiana Jones or [James] Bond are, instead of one continuous story that requires many installments.” (That standalone strategy worked well for Warner Bros’  2019 box office smash Joker, which became the first R-rated film to gross over $1 billion worldwide.)

This second film is set almost seventy years after the original film. “In this movie we find [Diana] in 1984 and [she] is quite lonely — she’s lost her friends and doing what she needs to do,” Gadot said at CCXP. “She’s helping mankind and saving them until something crazy happens to her.”

This being the 1980s, Diana is operating in a Cold War scenario, taking on Pedro Pascal’s villainous Maxwell Lord, a shrewd and powerful businessman. Kristen Wiig also co-stars as Barbara Ann Minerva, a British archaeologist in the comic books who becomes Wonder Woman’s arch-nemesis Cheetah. Connie Nielsen and Robin Wright reprise their roles as Diana’s mother, Hippolyta, and aunt, Antiope, respectively, in flashbacks to Diana’s Amazonian upbringing on Themyscira.

As New Order’s “Blue Monday” plays in the background, we see Diana having some heart-to-heart girl talk with Wiig’s Minerva about long-lost loves and a glimpse of an old photograph of Steve Trevor. “My life hasn’t been what you probably think it has,” Diana tells Barbara. “We all have our struggles.” Then trouble breaks out at a local supermall, and Diana intervenes to restore order. Inside the mall there are walls of TVs that just happen to be showing Maxwell Lord giving a motivational pitch. “Life is good but it can be better,” he says. “All you need is to want it. Think about finally having everything you always wanted.”

Lord has had various incarnations in the comics, including one where he had supernatural powers of persuasion. It’s unclear from the trailer what, if any, powers he displays in this film, but there are hints he might play some role in the miraculous reappearance of Steve while Diana is attending a gala. We see Diana and Steve’s emotional reunion, and then a shot of Lord declaring he will now take what he wants in return.

The rest of the trailer is a series of action shots as Diana and Steve work together once again to thwart whatever evil plan is threatening the day—including flashbacks to a young Diana competing in an Amazonian tournament, and a glorious shot of Diana’s iconic golden armor. But we don’t get to see Wiig in full Cheetah mode, which is a shame.

Wonder Woman 1984 hits theaters June 5, 2020. If it’s as successful as its predecessor, we can probably expect a third Wonder Woman film. Jenkins told the Hollywood Reporter earlier this year she has already mapped out the plot for a third installment, in a more contemporary setting.

Listing image by YouTube/Warner Bros

Brian Ascher is a partner at Venrock, where he invests broadly across enterprise and fintech and serves on the boards of several companies, including Personal Capital, 6Sense, Socrates AI, Dynamic Signal, Retail Solutions, SmartBiz Loans, and Inrix.

More posts by this contributor

• Running through walls: 6Sense’s Amanda Kahlow on values that stick
• Running Through Walls: Dynamic Signal’s Russ Fradin on how good businesses constantly pivot

Laravel and MySQL 8: Fixing MySQL Server Has Gone Away Error

If you’ve tried to upgrade your Laravel applications to use MySQL 8, you might have run into the following error that left you scratching your head:

SQLSTATE[HY000] [2006] MySQL server has gone away 

The php.net manual has an outdated (but still relevant explanation):

When running a PHP version before 7.1.16, or PHP 7.2 before 7.2.4, set MySQL 8 Server’s default password plugin to mysql_native_password or else you will see errors similar to The server requested authentication method unknown to the client [caching_sha2_password] even when caching_sha2_password is not used.

This is because MySQL 8 defaults to caching_sha2_password, a plugin that is not recognized by the older PHP (mysqlnd) releases. Instead, change it by setting default_authentication_plugin=mysql_native_password in my.cnf. The caching_sha2_password plugin will be supported in a future PHP release. In the meantime, the mysql_xdevapi extension does support it.

We should expect a future version of PHP to have support for caching_sha2_password authentication. However, in the meantime, you can fix it quickly with the following changes:

First, we need to find the paths MySQL will look for a configuration file. We can find out by running mysql --help. The command prints out a lot of info, but you’re looking for something like the following:

mysql --help ... Default options are read from the following files in the given order: /etc/my.cnf /etc/mysql/my.cnf /usr/local/etc/my.cnf ~/.my.cnf 

Take the paths from your command output and adapt the following with the paths you get from mysql --help:

ls -la \ /etc/my.cnf \ /etc/mysql/my.cnf \ /usr/local/etc/my.cnf \ ~/.my.cnf ls: /etc/my.cnf: No such file or directory ls: /etc/mysql/my.cnf: No such file or directory -rw-r--r-- 1 paul staff 61 Dec 5 19:40 /Users/paul/.my.cnf -rw-r--r-- 1 paul admin 113 Oct 28 2017 /usr/local/etc/my.cnf 

I like to manage the file from ~/.my.cnf, but unless you’ve previously done that, you’ll probably have to create the file if you want to manage configuration from that path.

I suggest you use the ~/.my.cnf path, but whatever path you determine you need to add the following:

[mysqld] default_authentication_plugin=mysql_native_password 

If you’re using Homebrew and you want to update the /usr/local/etc/my.cnf file, add the following at the end of the file under [mysqld]:

# Default Homebrew MySQL server config [mysqld] # Only allow connections from localhost bind-address = 127.0.0.1 default_authentication_plugin=mysql_native_password 

Last, you need to restart MySQL using whatever method is appropriate for your system. If you’re using Homebrew on a Mac, you can run brew services:

brew services restart mysql 

If you’re using Docker, here’s an example Docker Compose configuration to get MySQL 8 working with Laravel and other PHP projects:

services: # ... mysql: image: mysql:8.0 # PDO Doesn't support MySQL 8 caching_sha2_password Authentication # @see https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html#upgrade-caching-sha2-password command: --default-authentication-plugin=mysql_native_password ports: - 13306:3306 volumes: - mysql:/var/lib/mysql environment: MYSQL_DATABASE: my_database MYSQL_ROOT_PASSWORD: root volumes: mysql: driver: "local" 

With that change in place, you should be able to connect to MySQL 8 from PHP applications!

---

Filed in: News

---