Sometimes there are unique content requirements that require content editors to insert Twig code in Craft CMS entries. However this raises several security concerns and issues. In this post I'll highlight the solution I developed for my blog.

With a new year comes a new server (now Debian 9 wooo!) and a new blog system built on craft 3.

Right of the bat I faced multiple challenges deploying this new blog because of a wonderful bug that causes the locking of project.yaml to not work in production environments. Long story short I had to reinstall this blog four times before it actually working.

The blog is served by Caddy which is awesome! It provides HTTPS with Let's Encrypt and HTTP2 with zero configuration. Here is what my setup looks like: