03 Jan 2017
8 minute read
Recently on a Rails project, I ran into an issue where I wanted to expose a
resource (lets say it was a product) in a RESTful route, but I also didn’t want
the URLs to be easily guessable. In other words, following Rails conventions my
standard “show” actions would be URLs like
https://example.com/products/3, which are
trivially guessable since we’re exposing the database’s auto-incrementing
integer primary key as the resource ID. To prevent people from writing a super
simple script that could scrape my whole product catalog, it would be nice if we
could make the URLs not trivially guessable while still remaining
publicly-accessable for people who know them.
05 Sep 2016
7 minute read
Recently I added Elm to a Rails application using webpack, and it took me a
while to figure out as I’m new to both so I figured I’d share what I did.
A complete example app is available on GitHub (abevoelker/rails-elm-example);
this post will walk through each step used to create it.
25 Apr 2016
15 minute read
Recently I ran into an issue with a Rails web application where I wanted to add
one-click unsubscribe links to transactional emails I send out. This website
tracks the inventory of retail product websites; users subscribe to individual
products and get notified via email when the price or stock status changes so
that they can quickly make purchasing decisions based on the information.
09 Apr 2015
17 minute read
Alternate title: “You could have invented Either!”
I’m still a rank beginner at Haskell, but I guess it’s already leaving some tracks in my brain as I find myself wanting algebraic data types and pattern matching when I’m writing Ruby.