I’m writing a small app using React Native. Since I’m a fan of Tailwind for styling on the web, I wanted to use it for the app as well. The package tailwind-rn is available, but requires the use of tailwind('...') to apply styles, which doesn’t work with the intellisense plugin for VSCode.

Two tings have collided. Me wanting to learn Rust and the r/roguelikedev summer tutorial follow-along. My main motivation (for now) is learning Rust, so I’ve set a restriction for myself: I won’t be using external dependencies for anything that can feasibly be done manually. To keep things manageable, that means that my rogue like will be old school and take place in a plain ol’ terminal.

If you’ve ever struggled getting to grips with webpack, now is a good time to get started. The stable release of webpack version 2 is out, and this guide will take you from zero to a functional webpack configuration. The end result will be a small, but working React application. The configuration will be expanded one item at a time and will be driven by error messages. By not starting out with a boilerplate, you’ll be able to understand what each part does, and thus be able to expand upon it yourself if new needs arise.

Lately I’ve been working on automatically provisioning servers while trying to remain sane as well as getting simple automatic deployments running. I’ve been bit by it before, but it wasn’t until I was trying to set up loadbalancers and DNS in Rackspace, that I took some time to look into the problem: with_subelements doesn’t work properly. At least not the way I thought it should work.

I’ve heard that the best way to learn a new programming language is to create a proper project in it. golive is my “Learn Golang”-project. It is a simple deployment tool that listens to webhook requests from git repository providers such as Bitbucket and Github. If the pushed repository and branch matches something in the configuration file, corresponding jobs run.

I was recently tasked with transitioning a server setup from the medieval times of “we can’t get in contact with the server-guy, but here are some vague instructions that are probably outdated” to the modern times of “automate all the things!” Trying to make sure the process was fully codified and idempotent, I ran into some snags here and there. This is a documentation of those snags, both for a future me, but also for others, should they struggle with the same things. As the title says, it is focused on Ansible, its integration with Rackspace and how to keep the playbook idempotent – that is, how to make sure that running the playbook has no effect if no changes has been made to it.