In the first two posts of the series, I looked at setting up Dokku and setting up automated builds and testing with Codeship, Code Climate, and Hakiri. This one ties those two together and covers the process I’m using for automated deployments with Dokku and Codeship (and the gotchas I hit along the way).
This release implements basic tracking of short URL usage. It tracks the following data:
This release protects the application’s domain from being redirected to by the app to avoid possible infinite loops or inaccessible application routes.
Last time in the Dokku series I went through how I set up Dokku on a VPS. This one is going to be about setting up Codeship, Code Climate and Hakiri (Ruby only, though the principles should be pretty similar for other languages/frameworks) to automate builds and testing. Should be a bit shorter, because there were fewer gotchas in this than in setting up Dokku (not that there were many there!)
This release introduces the ability to use randomly generated slugs for Short URLs.
Heya. I posted last week about building Url Grey, my URL shortener, a process which lead me to discovering and setting up some new tools. Specifically, Dokku, Codeship for Continuous integration and delivery, and Code Climate and Hakiri for code security, style, and test coverage reporting. I’ve decided to write the whole process up more completely, in part for myself, and in part because there a few hiccoughs I ran into that didn’t have answers (or readily apparent answers–it took me some hunting and piecing together of things) online.
This will be part of a series (hello slug up above!), starting with setting up Dokku, and moving on through the process of linking all the pieces together to get a continuous deployment setup.
My wife and I went down to Cornwall for our anniversary this last week, and we decided to take surfing lessons. It’s a little embarassing that I’m now 29 and grew up in Southern California, pretty much in Huntington Beach, and have never surfed in my life. My English wife from Gloucestershire (think countryside) had actually surfed before me. So we decided to learn how to surf on our anniversary.
Even my captain laughs at me for this.
Super quick one–I just jumped on the JSON feed bandwagon, so you can now get all the stuff here at flyinggrizzly.io/feed.json. I’m not using it yet, but it took me less than a minute to set up (merging the PRs took longer than the actual work, which mirrors the reports from just about everyone else, including the guy whose code I aped–thanks dude!).
It’s been quite a while since my last post on TDD, and I have promised myself that I would get something out before the end of the month, so this may be a little slap-dash. Especially considering that today it’s my anniversary and there are bigger things on my mind!
Over the last 2 weeks, I’ve been writing a URL shortener in Rails, and I’ve now got it to a point where I’m using it personally on the great wide internets! I call it Url Grey, and the code is all on Github. It’s still got some work to do, but getting this far has been a ton of fun, and a massive (and useful) learning experience.
A parable told in code.
class Rubyist < Human
include EmotionalAccessors
include RelationshipToTDD
attr_reader :tdd, :experience, :joy, :worry_about_others_perception
def initialize
@worry_about_others_perception = 10 # or so I'm told
@experience = 2 # years, on average?
@joy = 0 # cannot be inferred without more data
end
...
end
class RubyN00b < Rubyist
def initialize
super
@worry_about_others_perception += 500
@experience = 0
@tdd = false
end
...
end