ruby-install VS PostgreSQL

Let’s get started. I prefer to manage my Ruby installations on my development machine with chruby paired with ruby-install. Another outstanding set of tools is rbenv with ruby-build. I highly recommend installing Ruby with one of those two sets of tools. Follow the instructions on their project’s READMEs. For this article, I’ll be running Ruby (MRI) v3.3.0.

Use the ruby-install tool for this. https://github.com/postmodern/ruby-install

Anyone have ideas on what the issue is? The closest error message I found searching online was linked to this post which I'm not sure is exactly the same since their error message is on a different line (line 9 vs 14) and doesn't mention openssl like my error message does.

Another option would be to use ruby-install to manually install your desired Ruby version to somewhere on your path. The downside here is that you lose the ability to switch between Rubies. This type of installation would allow you to set $GEM_HOME and $GEM_PATH however you like though.

you may need to browse some issues like this one https://github.com/postmodern/ruby-install/issues/399

I use https://github.com/postmodern/ruby-install along with https://github.com/postmodern/chruby

ruby-install 0.8.3 has been released. This version explicitly pins the homebrew openssl dependency to [email protected]. OpenSSL 3.0 was released this month and is now available in homebrew. Unfortunately, ruby’s openssl bindings are still working on OpenSSL 3.0 support, so attempting to compile any current ruby version against OpenSSL 3.0 from homebrew will result in a compilation error. Until all actively supported versions of Ruby support OpenSSL 3.0, ruby-install will continue to compile against [email protected] on macOS with homebrew.

PostgreSQL

The LMS Moodle Operator serves as a meta-operator, orchestrating the deployment and management of Moodle instances in Kubernetes. It handles the entire stack required to run Moodle, including components like Postgres, Keydb, NFS-Ganesha, and Moodle itself. Each of these components has its own Kubernetes Operator, ensuring seamless integration and management.

Another key feature of txtai is being able to quickly move from prototyping to production. This article will demonstrate how txtai can integrate with Postgres, a powerful, production-ready and open source object-relational database system. After txtai persists content to Postgres, we'll show it can be directly queried with SQL from any Postgres client

SQL (Structured Query Language) databases are relational databases. They organize data into tables with rows and columns, and they use SQL for querying and managing data. Examples include MySQL, PostgreSQL, and SQLite.

Node.js, MySQL and PostgreSQL servers installed on your machine

Each app’s front end is built with Qwik and uses Tailwind for styling. The server-side is powered by Qwik City (Qwik’s official meta-framework) and runs on Node.js hosted on a shared Linode VPS. The apps also use PM2 for process management and Caddy as a reverse proxy and SSL provisioner. The data is stored in a PostgreSQL database that also runs on a shared Linode VPS. The apps interact with the database using Drizzle, an Object-Relational Mapper (ORM) for JavaScript. The entire infrastructure for both apps is managed with Terraform using the Terraform Linode provider, which was new to me, but made provisioning and destroying infrastructure really fast and easy (once I learned how it all worked).

I've used MySQL for years. But recently, I found myself working PostgreSQL and simple things like dumping and restoring a database are different enough that I decided to document the process. It's straightforward enough once I knew how.

A running Rails application needs a database to connect to. You may already have your database of choice installed, but if not, I recommend PostgreSQL, or Postgres for short. On a Mac, probably the easiest way to install it is with Posrgres.app. Another option, the one I prefer, is to use Homebrew. With Homebrew installed, this command will install PostgreSQL version 16 along with libpq:

PostgreSQL