Explore >> Select a destination
|
You are here 
|
blog.appsignal.com | ||
| | | | |
blog.codeminer42.com
|
|
| | | | | As we all know, it is quite easy to create database tables with Ruby On Rails. However, some cases require personalizations to reproduce real world situations and the relationships between them. Here, we have two models: User and Meeting, with a 1..N relation where one Meeting has two User (yes, a two-person meeting.) The problem | |
| | | | |
lancecarlson.com
|
|
| | | | | Imagine a system that not only stores data but grasps its very essence. A system that can swiftly navigate through myriad data points to pinpoint the most relevant. That's the power of vector databases. They're tailor-made for QA systems, acting as memory boosters for large language models. Their ability to seamlessly link questions to exact answers showcases their pivotal role in modern AI. I'm going to show you how you can setup your very own vector database using Ruby on Rails so you can ask your data questions! | |
| | | | |
blog.arkency.com
|
|
| | | | | ||
| | | | |
blog.healthchecks.io
|
|
| | | In this guide, I will deploy a Healthchecks instance on a VPS. Here's the plan: Use the official Docker image and run it using Docker Compose. Store data in a managed PostgreSQL database. Use LetsEncrypt certificates initially, and load-balancer-managed certificates later for a HA setup. | ||
