Containers feel a bit like the elusive null packet. When reading & learning about Linux containers (cgroups), Docker containers, and containers in general, it's quick to realise that just like null packets, in concept "they are perfect in their simplicity and they are very true". Yet, achieving simplicity is hard damn

Firstly, make sure you're not missing out: you'll probably want to use Laravel Authorization Policies rather than guard checks. Remember: Put guards as close to the routes as possible, don't waste time having PHP build the page only to have the template block access. Start with the routes, and work

This pertains to Laravel 5.4, and probably above. Example: You have another auth provider called 'customer'. Tldr; * Copy both existing password controllers * Add a boker method in new ForgotPasswordController * Add a showLinkRequestForm in new ForgotPasswordController and point it to a new view * Update new ResetPasswordController: Set $redirectTo path set

At the moment you can't talk about containerisation without thinking about a hole host of dependant topics: * Auto discovery - Container Name Services & what do you mean port 80 is already in use? * Managing persistent storage in a containerised environment - Where do I put my database & oh damn where

Ubuntu 16.04 does not come with php5 packages. However, Horde requires the PDO extension, which can be resolved by installing the php5.6-pgsql module. This fixes the Could not instantiate PDO. PDOException: could not find driver (1) error: sudo apt-get install php5.6-pgsql Incompatibility with PEAR's Services_Weather package

General steps * Make sure mpls is enabled on each of the routers interfaces- including the Customer Edge (CE) interface. * Obviously the Provider (P) routers require this, but only the receiving Customer Edge (CE) router interface needs to be MPLS enabled unless Penultimate POP is being used. * Define include each of

(There's no such thing) To some the term "MPLS VPN" is really confusing because it reads that an MPLS VPN is somehow something additional to MPLS itself when in fact the very process of configuring MPLS results in the creations of virtual private routes for different customers. It's not like

The moment when you realise every web dev tool is inspired by some smug *NIX developer over 50 years ago. #dry There I was writing a simple Python scrip to parse an XML document. "I'd like to watch the changes to this python script as I'm following this Python XML

Take a look inside: /vendor/laravel/framework/src/Illuminate/Auth/Middleware/Authenticate.php Review the authenticate() method, which takes an array of guards. protected function authenticate(array $guards) { if (empty($guards)) { return $this->auth->authenticate(); } foreach ($guards as $guard) { if ($this->auth->guard($guard)->check()) { return $this->auth->shouldUse(

For this we will demonstrate creating a customer type with their own separate authentication table, model, login and registration. This shows in internal account creation whereby only the admin is allow to register new users of this type. This might be useful for scenarios where there are many user types

This is general advice, it's not correct for every scenario. This assumes you've not just deleted a file and it's in your recycle bin.. :) It assumes some technical assistance is required to perform the recovery, and this is advice on how to proceed to make it easier for the technician