ruby-next VS Vagrant

But if it really bothers you, check out ruby-next.

I hope to get some time to try to contribute it to ruby-next https://github.com/ruby-next/ruby-next/issues/98

As it would happen, the folks behind Ruby Next have some ideas here, and have done a significant amount of work in enabling this very vision to become a reality.

Don’t give the punchline away, but this post is actually a big tutorial about using Ruby Next to modify Ruby exactly to your tastes. Here’s hoping you’ll have as much fun reading this fantasy as I did writing it. 😅

You can with Ruby Next: https://github.com/ruby-next/ruby-next#proposed-and-edge-features

Ensuring high availability with limited resources can be challenging. I recently want to proove you can do it using Keepalived and just two servers 💪✨. To prove it, I used Vagrant. Here's a quick rundown of my journey! 🚀

Vagrant - Make sure you have Vagrant installed on your machine. You can download it from Vagrant's official site.

I do believe that using containers makes a ton of sense in writing data pipelines. You can use the same image to develop and run the pipeline, preventing "it works on my machine" issues. You can test different variations of the image without having to stand up additional infrastructure or potentially breaking the workflows of others who're using the same infrastructure. Finally, knowledge of containerization is increasingly expected of all engineers, while knowledge of other tools that solve similar issues (like Vagrant or Ansible) is less common.

Running NixOS on a virtual machine (VM) is a safe and reproducible way to test such configurations. As for VMs, I have used VirtualBox, Vagrant and lxd in the past. However, I have found QEMU to be the simplest and most flexible solution for my needs.

I found out that the error was that initialy I was using an old version of the vagrant utility for vmware: 1.0.21, so I read this post: https://github.com/hashicorp/vagrant/issues/12052 and there I saw that I needed to install the new version, in my case 1.0.22 which I mentioned on the point #3.

Vagrant is a tool for building and managing virtual machine environments in a single workflow. Developed by Hashicorp, it is used to replicate multiple virtual environments. It can efficiently run in all virtualized environments, providing the highest level of isolation to users.

Another important tool from the same organization is Vagrant, which provides extra help in running VMs built with Packer. Of course, the choice of a VM provider is also very important, as some VM providers may not be supported on certain platforms. For example, there are no VMware or VirtualBox releases that support Apple Silicon. However, QEMU is supported on most platforms, including Apple Silicon, which is why this provider was chosen here.

https://github.com/hashicorp/vagrant/issues/1052#issuecommen...

Again at this point the jokes are frankly writing themselves. Like bro make it possible for people to follow your advice.

Also if you directly state or indirectly insinuate that your tool is ANY/ALL OF Local First, or Open Source, or Free As In Freedom you better have offline docs.

If you don't have offline docs your users and collaborators don't have Freedom 1. If you can't exercise Freedom 1 you are severely hampered in your ability to exercise Freedoms 0, 2, or 3 for any nontrivial FOSS system.

The problem has gotten so bad the I started the Freedom Respecting Technology movement which I'm gonna plug here: https://makesourcenotcode.github.io/freedom_respecting_techn...

Vagrant