<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Web on Personal Blog of Maximilian Ehlers</title><link>https://blog.sodawa.com/tags/web/</link><description>Recent content in Web on Personal Blog of Maximilian Ehlers</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 07 Jul 2017 12:12:00 +0000</lastBuildDate><atom:link href="https://blog.sodawa.com/tags/web/index.xml" rel="self" type="application/rss+xml"/><item><title>Deploying SSL secured website in 10 minutes</title><link>https://blog.sodawa.com/blog/deploying-ssl-secured-website-in-10-minutes/</link><pubDate>Fri, 07 Jul 2017 12:12:00 +0000</pubDate><guid>https://blog.sodawa.com/blog/deploying-ssl-secured-website-in-10-minutes/</guid><description>Caddy Through a colleague I have recently stumbled upon caddy. It is a new Webserver written in Go.
You might think why not use nginx?, and this was exactly my question. The answer is best explained by the following config file for caddy:
ehlers.space Yup, that is it. This will run this blog with SSL through Letsencrypt and keep it up to date. No need for manual certification extending or even using the auto-cert bot.</description></item></channel></rss>