RubyFlow The Ruby and Rails community linklog

×

The Ruby and Rails community linklog

Made a library? Written a blog post? Found a useful tutorial? Share it with the Ruby community here or just enjoy what everyone else has found!

Submit a post

You can use basic HTML markup (e.g. <a>) or Markdown.
Note that your post may be edited to suit the format of the site.

As you are not logged in, you will be
directed via GitHub to signup or sign in

Post Preview

Note: Only the first pargraph is shown on the front page and overly long paragraphs may be broken up.

Streaming LLM Responses

In this episode, we look at running a self hosted Large Language Model (LLM) and consuming it with a Rails application. We will use a background to make API requests to the LLM and then stream the responses in real-time to the browser. https://www.driftingruby.com/episodes/streaming-llm-responses

Using the XDG Base Directory Specification

Hello. 👋 I wanted to share an article on leveraging XDG in your CLIs, web applications, libraries, frameworks, etc. There’s been some chatter in this space as of late, which is great to see, so wanted to show how this works and gems you can use to build upon it if interested. There’s a lot you can do with this specification, so enjoy!

How to host a Ruby Coderetreat Workshop for Game of Life challenge at a regular Ruby

Coderetreat is a full day practice workshop, which could be also shorten to 4-hours-long, intensive practice event and it would perfectly fit to the format of a regular Ruby Meetup. The Coderetreat event has a standard format, even though there are different forms and flavors. We usually use Pair-Programming and Test Driven-Development to implement Conway’s Game of Life and delete your code at the end of each session. [more inside]

How to Dual Boot Your Ruby or Rails Application with Different Versions of Ruby

Dual booting Ruby is similar to any other dependency, but there are some important differences that we need to address to do it right. There are more ways to do this but we try to minimize the disruption to the normal development workflow as much as possible. With these ideas you can default to use the current Ruby version while also being able to use the next version on demand with a few commands. [more inside]

Loading older posts