Privatracker is a SaaS tool designed to serve as a privacy-respecting alternative to traditional web analytics platforms like Google Analytics. Let's check out the tech stack and discuss approaches and alternatives.
For the first time since the 2000s, I'm working on a new Rails application without using any form of real build steps on the front-end. We're making it using vanilla ES6 with import maps for Hotwire, and vanilla CSS with nesting and variables for styling. All running on a delightfully new simple asset pipeline called Propshaft. It's al...
Privatracker is a SaaS tool designed to serve as a privacy-respecting alternative to traditional web analytics platforms like Google Analytics. Let's check out the tech stack and discuss approaches and alternatives.
Dive into the story of Lineman.js. From pioneering features to untimely challenges, discover how it shaped modern web development.
Edit: In the original version of this post I made a mistake. This post has been corrected. See the details at the below for an explanation of the mistake and the solution. Mistake Summary & Solution In the original version of this post I had stated that the App servers IP in the Kamal configuration should be set to it’s public IP. This is incorrect. With the SSH proxy pointing at the public IP as well, this resulted in a jumphost connection problem, meaning it tried to connect to the public IP through a proxy of the public IP. This obviously didn’t work and resulted in inconsistent behavior with Kamal. The solution was to replace the App servers IP address to be the private IP instead. As a result, the only place the public IP of the server is referenced is in the Kamal SSH proxy configuration.
For the first time since the 2000s, I'm working on a new Rails application without using any form of real build steps on the front-end. We're making it using vanilla ES6 with import maps for Hotwire, and vanilla CSS with nesting and variables for styling. All running on a delightfully new simple asset pipeline called Propshaft. It's al...
Why compression dictionaries will force us to rethink our bundling strategies and their naming
Work on Rails 8 is starting, so I dug through the official GitHub milestone to break down all the upcoming goodies for you. There's plenty coming, including Solid Queue, Solid Cache and Kamal becoming defaults, better support for PWAs, an official LSP, and more!