Following up on the ‘Rails from “zero” to kubernetes’ series, we’ll see today how to expose your service to the internet, since I think we all agree that mapping directly the port of your rails app to the internet is not a really wise choice.
Kubernetes has a “simple but works” solution called ingress, ingress is an HTTP proxy, it will work as a reverse proxy for HTTP and HTTPS for any service that exposes one one port.
Following up on our previous post, we’ll now make kubernetes work for us, and automatically scale our application.
One of the really cool kubernetes features is the ability to automatically span new pods for your deployment based on the CPU usage of your pods. This is kinda simple, but very useful.
In the previous post, we created our first kubernetes pod, but one important part is missing, it is not possible to access that application, we’ll solve this with a service now….
Last year I wrote about using docker-compose to have a test/development environment similar to your production environment (you can check the post here) My environment kept growing and becoming more complex, and I started using docker swarm to deploy the applications, and after some time I started using kubernetes, I’ve learnt something about kubernetes in…
Really cool gem that allows you to run your pending migrations from the comfort of your browser.
This post is the write-up of how I fixed a production problem that happened a few minutes ago, and can probably save some time for you too, so read this and remember for your next code that deals with time
Some time ago I missed one of the cool features from the time I worked with JavaEE, that was a request scope for some variables.
I know the instance variables on controllers do a great job simulating it, but I needed to access context in a completely different part of the application, that wasn’t always called from controllers, variables that should be scoped to that request.
So I thought, I could create something like that for my rails app.
https://edgeguides.rubyonrails.org/action_text_overview.html In many projects we have the requirement to have a rich text editor available, for full documents, user profiles, blog posts, comments, product descriptions, … And every time we think, which editor to use, some times we just get our current favorite, or the one we used in the last project, in my case…
Beware of default scope, most of the times it appears to be helpful, it will just be causing you hidden bugs to deal with later