It has been there for a while under Virtualmin, but I was hesitating on using the GUI configuration of Let's Encrypt from Virtualmin on an existing manual configuration. Let's Encrypt does not allow you to make any change afterwards, yielding this error :
Request failed : The native Let's Encrypt client was used previously on this system, and must be used for all future certificate requests.
Drupal 8 evolves quickly, and it's easy to get lost amongst the several documentations that have been written since the beta releases, Drush and PHP version needs upgrade. Some things that I have learned.
Okay, VM's are easier to maintain solutions, but in some situations you just don't have enough RAM for having Virtualbox running all the time.
After trying the latest dev release of VDD (needed to run Drupal 8, because at the time of writing this, the stable release is stucked to PHP 5.3), I decided to give a try to VLAD, another Vagrant alike solution.
Main reasons : git and drush are not already installed on th VDD dev, and sometimes I got stucked on the vagrant provisioning.
First reaction after installing VLAD : Woooooow !
Here are some of the sweet goodies that awaits you :
Be ready for the opening of free ninety-day lifetime certificates !
The objective of Let?s Encrypt and the ACME protocol is to make it possible to set up an HTTPS server and have it automatically obtain a browser-trusted certificate, without any human intervention. This is accomplished by running a certificate management agent on the web server.
One of the many amazing sessions given at the DrupalCamp Leuven 2015 was about tests applied to small / medium sized projects. I was a bit sceptical, we all agree that testing should be part of any development process, but it can run you quickly out of budget on small projects. @pfrenssen has just proven the opposite.
The best PHP time saver book ever about the latest features of the language (PHP 5.5+), good practices and deployment. A must have for Drupal 8.
We talk here about OOP, namespaces, traits, generators, closure, PSR, components, optimization, deployment (Capistrano), profiling (XDebug, XHProf), unit tests (PHPUnit, Travis CI), dev environment (Vagrant), ...
This tip is for people that would access a Vagrant dev website from another VM (let's say to test another version of Internet Explorer via e.g. https://github.com/xdissent/ievms) or via another device than the host environment (smartphone, tablet, ...).
Vagrant allows you to quickly deploy dev environments on a Virtualbox VM.
xip.io will let you access your dev website from other devices (already tried to patch /etc/hosts on an iPad?)
I wondered if there was a solution to play around with Drupal 8 on a Chromebook (super cheap hardware / "everything in the cloud model" with a 16G SSD).
After some reddit I discovered that Koding.com provides you freely, in the browser, a VM / terminal plus a text editor for PHP and other popular languages (Ruby, Python, ...).
Open up your Koding Terminal and cd in the Web directory (default, single docroot for a VM).
cd Web
After spending some time configuring Yosemite to end up in a poor result (slow server, MySQL crashing repeatedly), I decided have a look at this Vagrant stuff.
I was astonished how easy it was to get up and running with it.