Letsencrypt is a great initiative. It lets you create free signed SSL certificates. These certificates are only valid for 3 months, but that does not matter because they automated the process. It has become so easy to use SSL on your website that it makes you wonder why existing CA’s did not come up with this!
Already the majority of the websites I maintain are SSL only, such as this blog for example. However, this can be tricky to setup with the automated cert deployment. You run their client on your webserver and request a cert for a one or more domains and specify the webroot of the website where this site is hosted. The client places a challenge in the .well-known/acme-challenge/ directory to prove that you are the owner of the domain (or at least control the website that the domain points to). Then you daily run a cronjob that renew certificates.
If you move SSL only, you will probably do something like this:
<virtualhost *:80> DocumentRoot /var/www/html/blog ServerName bart.vanbrabant.eu Redirect / https://bart.vanbrabant.eu/ </virtualhost>
However, the next time leysencrypt tries to verify the challenge it will be redirected to the https website instead of retrieving the challenge over http. This is easily solved by changing the redirect in:
RedirectMatch 301 ^(?!/\.well-known/acme-challenge/).* https://bart.vanbrabant.eu$0