tldr;instead of now installing/using JIRA, Trello, Github, Jenkins/TravisCI, and Teamcity, I can just install one thing – Gitlab, spend a little time configuring it, and be ready to take your development process to the next 5 levels (if you’re not already there) Gitlab 9.4 was just released and I’m pretty excited about it. A lot of stuff that Gitlab is doing is really showing that they value empowering developers and pushing ops in The Right Direction ™ – for me that means towards automating deployment, and getting smarter about how we ship and test.
Some random notes on getting docker, nginx, your firewall and postres to play nicely (if they aren’t) This post is one I wrote a while back (as a follow up to the KVM post) but never published, as I’ve found some free time now, I’m going through and putting together posts that I jotted down but never got to publishing. After setting up my KVM-enabled VPS with Arch Linux, it came time to start moving over the deployments of my applications.
From zero to reasonably secure dockerized appliation running on a KVM VPS This post is one I’ve had written for a while but never published, as I’ve found some free time now, I’m going through and putting together posts that I jotted down but never got to publishing. This one was written when I ran into issues goign from an OpenVZ powered VPS to a KVM one, since I wanted to use docker to simplify my deployments a little bit (why I did so is a whole nother discussion, for another time).
… Or you shouldn’t. I don’t know, I’m just a random person on the internet. Don’t let random internet blog posts make your decisions for you, carefully weigh the options and decide what’s right for you. Or don’t. Disclaimers aside, many people have brought up the fact that despite hosting much of the best open source code on the planet, Github itself was not open source. Recently there was quite a rustling over an open letter to Github, which seemingly spurred Github to make all the actions they were taking to make the platform greater more publicly accessible.
tldr; I wrote a small script in python to use alsa command line tools to change the volume on my headset. A tool already exists that if faster and more robust. I should switch, but will I? who knows :). I own and (mostly) happily use a Logitech G930:
While the support under linux is pretty good already (most buttons work, and perform their intended functions), I recently got fed up with the fact that the little scroll wheel on the G930 wasn’t actually changing the volume.
So recently I’ve been working on porting B2G to a Huawei Softbank 201HW/U9201L phone. While doing so, however, I had the minor setback of bricking the phone. This is a brick in the sense that the device goes into an infinite boot loop, right after starting up — as soon as it starts up, it determines it needs to restart. As that project might actually take a long time to complete (I’m currently at the point of trying to manufacture a ClockWorkMod-compatible image that would fix what is broken on th phone, which currently seems to be a bunch of missing symlinks), I recently bought myself a Nexus 5.
Recently, during a trip to Japan, my FirefoxOS Flame‘s backlight decided to go out in a blaze of glory. Upon opening the device up, I found that the ribbon (as well as the connector) for the device had burn marks on them, and thought that might be the cause of the issue (some sort of short, I assume). Luckily, there is actually ongoing service for the FirefoxOS Flame, all you have to do is to send an email to flameservice@thundersoft.
After the recent rise of task-management related tools like Grunt, Gulp, and Broccoli, I’ve often wonered if there was an easier way to implement some of the most useful features that those tools provide: watch (of course, watch is not the only thing that these libraries provide, but is often the most unique/useful). Grunt, Gulp and Broccoli are wonderful tools, and these days basically come hand-in-hand with front-end development, however there are various downsides to installing/using them.
Welcome to first (of hopefully many) entries about my adventures using Arch Linux, which will most likely consist of me breaking things, then looking at documentation, then reading guides, then fixing the things I broke. Lots of things happened today (they’re going to be subjects of other blog posts), but one thing I just got through doing was creating a swap file for suspend-to-disk (hibernate) to use. Long story short, my phone died, and inbetween getting getting another one, my new laptop (which I like a lot) is going to be the only way I can keep in contact with people.