Wrote some more about mailu

3 files changed, 19 insertions, 3 deletions

diff --git a/_posts/2018-05-31-new-site.markdown b/_posts/2018-05-31-new-site.markdown
index 10ff8a1..899c70a 100644
--- a/_posts/2018-05-31-new-site.markdown
+++ b/_posts/2018-05-31-new-site.markdown
@@ -11,6 +11,8 @@ This site is currently built with [Jekyll][jekyll], and served using [nginx][ngi
 
 The same Raspberry also hosts [my wife's blog][heyworlditshenry], where she writes about our son Henry, who sadly passed away shortly after he was born.
 
+I've got a few personal projects active at the moment, and I hope to write about all of them!
+
 [jekyll]: https://jekyllrb.com/
 [nginx]: https://nginx.com
 [rpi-2b]: https://www.raspberrypi.org/products/raspberry-pi-2-model-b/
diff --git a/_posts/2018-06-01-mailu.md b/_posts/2018-06-01-mailu.md
index ef43bb2..a3a0efd 100644
--- a/_posts/2018-06-01-mailu.md
+++ b/_posts/2018-06-01-mailu.md
@@ -33,8 +33,10 @@ There are a couple of alternative ways to get a good mail server setup: [iRedMai
 
 This approach actually leads really neatly onto the last solution I tried, and the one I actually have working: [Mailu][mailu]. This project provides all the same open-source email components (postfix, dovecot), but pre-configured and packaged as [Docker][docker] images. This has a couple of advantages over iRedMail: 
 * You don't need a fresh Debian install. You only need a working Docker installation.
-* Other system packages will not interfere.
-* It's more easily movable. Since I pushed all my images to docker hub, I just copy over the data directory and the docker-compose file to a new Pi, execute `docker-compose up -d` and it's all back up.
+* You can configure & run other services on the same machine without interference.
+* It's more easily portable: copy over the single /var/lib/mailu directory to another machine, and spin up all the servers again with `docker-compose up` and it's all back up & working again.
+
+The project didn't work out of the box with Raspberry Pi - not all the base images are ARM compatible. This was a pretty easy thing to fix though, and I now maintain a permanent fork of mailu for Raspberry Pi over [here][mailu-rpi]
 
 [rpi]:https://www.raspberrypi.org/
 [dovecot-basic]:https://wiki.dovecot.org/BasicConfiguration
@@ -47,4 +49,5 @@ This approach actually leads really neatly onto the last solution I tried, and t
 [caddy-forum-non-http]:https://caddy.community/t/server-types-other-than-http/65/7
 [iredmail]:https://www.iredmail.org/
 [mailu]:https://github.com/Mailu/Mailu
-[docker]:http://docker.io/
\ No newline at end of file
+[docker]:http://docker.io/
+[mailu-rpi]:https://github.com/MFAshby/mailu
\ No newline at end of file
diff --git a/_posts/2018-06-02-unicornpaint.md b/_posts/2018-06-02-unicornpaint.md
new file mode 100644
index 0000000..8600348
--- /dev/null
+++ b/_posts/2018-06-02-unicornpaint.md
@@ -0,0 +1,11 @@
+---
+layout: post
+title:  "Unicorn Paint"
+date:   2018-06-02 22:33:00 +0100
+categories: jekyll update
+---
+
+See [unicornpaint] for details. I'll write about this later...
+
+
+[unicornpaint]:https://unicorn.mfashby.net
\ No newline at end of file