<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ops on Personal Blog of Maximilian Ehlers</title><link>https://blog.sodawa.com/tags/ops/</link><description>Recent content in Ops on Personal Blog of Maximilian Ehlers</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 21 Nov 2019 17:49:58 +0000</lastBuildDate><atom:link href="https://blog.sodawa.com/tags/ops/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker and Wireguard</title><link>https://blog.sodawa.com/blog/docker-in-wireguard/</link><pubDate>Thu, 21 Nov 2019 17:49:58 +0000</pubDate><guid>https://blog.sodawa.com/blog/docker-in-wireguard/</guid><description>Adding docker containers to Wireguard network Docker is the most convenient way of delivering my applications to servers, and Wireguard is the best VPN tool I have found so far. Naturally I would like to combine the two to give some of my Apps access to a Private Network, in which they can find a database for example.
This greatly increases security and eliminates a while lot of headaches around securing the database.</description></item><item><title>Security and convenience with Docker private networks</title><link>https://blog.sodawa.com/blog/security-and-convenience-with-docker-private-networks/</link><pubDate>Mon, 14 Aug 2017 18:56:00 +0000</pubDate><guid>https://blog.sodawa.com/blog/security-and-convenience-with-docker-private-networks/</guid><description>Docker is great, and I do not want to write much about what it does, but rather a problem that I have faced in my setup.
What I wanted to do was hosting a webserver inside of 1 container and a git client (https://github.com/go-gitea/gitea) in another. The webserver should be able to proxy requests from a certain url to the git client.
First attempt What I did first was exposing a port on my git client as follows:</description></item><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>