Add latet posts from Aral's site

content/news/export-import-issues-with-gitlab-ce/index.md

+---
+title: "Export/import issues with GitLab CE"
+date: 2019-06-08T10:41:18+01:00
+categories: ["Labs"]
+author: "Aral Balkan"
+postURL: "https://ar.al/2019/06/08/export-import-issues-with-gitlab-ce/"
+sourceURL: "https://ar.al"
+sourceName: "Aral’s blog"
+---
+
+GitLab CE (the free/open source version of GitLab) has an import issues feature but doesn’t have an export issues feature (because, not enterprise, apparently).
+
+So if you fork a project and want to transfer the issues also, you’re out of luck. Unless you use the API, that is.

content/news/rerun-cloud-init-on-multipass/index.md

+---
+title: "Rerun cloud-init on multipass"
+date: 2019-06-15T10:40:45+01:00
+categories: ["Labs"]
+author: "Aral Balkan"
+postURL: "https://ar.al/2019/06/15/rerun-cloud-init-on-multipass/"
+sourceURL: "https://ar.al"
+sourceName: "Aral’s blog"
+---
+
+Today, I had the need to experiment with rerunning cloud-init on a virtual machine created with multipass. You can use cloud-init with multipass by specifying a cloud-init.yaml file when creating your instance. e.g,
+
+`multipass launch --name my-instance --cloud-init ./cloud-init.yaml`
+This is all well and good and works as you would expect. However, today, I wanted to experiment with running cloud-init on an already-provisioned instance.