hanami | The web , with simplicity | REST library

I have a Hanami web application where one feature is to compare strings in the database with a user provided string. To do this, I use the postgres extension pg_trgm. The translated query condition in Ruby looks like this:

.where {similarity(:content, source_text_for_lookup) > sim_score_limit}

The problem I need to solve is to get the computed similarity score back to Ruby and present it to the user. However, the similarity score is not an attribute, since it is only relevant or it should only exist when the function is called in PG to compare the two strings.

Is there a way to do this?

Regards, Sebastjan

I have a Hanami 1.3.3 application which should run with Puma as production webserver. I want to use puma in cluster mode and use preload_app properly. Now I'm struggling with the right Puma config. I know, that every child-process (worker) must have its own fresh DB-connection, redis-connection, etc. My application uses multiple db-connections, redis, sidekiq. The main db is handled via hanami-model, the other db's are handled with pg-gem (connections are set up at class::initialize) directly.

What's the right hanami-way to handle this?

Here's one approach:

I'm trying to make a ruby hanami api using mongoid but the instalation fails because of bson. I get this error

I need help with deciding on a DB design approach. We're building a translation tool with Hanami (Ruby web framework) and thus ROM. We are facing the design decision of having one DB (Postgresql) table for translation records, where each record is for one source and one target language combination. However, source and target may be any language: EN-DE, FR-EN.

The other possibility would be DB table per language pair.

We currently have about 1.500.000 legacy records. We will not reach 2.000.000 soon, but still, we need to consider it.

We are inclined to the first option, but would it be feasible in terms of querying and performance? The main difference being, for option one matching languages must be queried first, and then the query for corresponding translation string is triggered.

Would there be a significant difference in performance for between both options?

Thank you

seba

I'm discovering Hanami those days (Hanami 1.3), I'm polishing the test project I've worked on, and I can't find a way to access the current page url/path from a view or a template (the idea is handling the navigation links visual state, as you may have guessed).

I've tried to guess helper names (routes.current_page, routes.current_url, routes.current...) but I've not been lucky. I've checked the routing helpers documentation, got through the hanami/hanami and hanami/router repositories but didn't find what I was looking for.

Did I miss something or is this simply not built-in?

I have hanami 1.3.0 app named booking. There is rake task in /rakelib/motel.rake :

I'm going to write a service that will using amqp protocol, without http at all. I like hanami's paradigm of repository-entity-model-interactors and I wonder to use those in my project. Generating all that stuff by hand, sure, is boring.

So, I wonder to grab rake tasks. Looking into config/environment etc, ughhhh. What is the best method, shortly, to use those tools without hanami router and controllers? Or, it is all integrated tightly?

As I think for that moment, there are two ways:

a) To include only hanami-model into my Gemfile, then copy by hand every needed file from gem hanami.

b) To create hanami project and do not use rackup.

I'm disappointed.

I have hanami application version 1.0.0 I have next routes.rb file:

If I use roadie/premailer to transform my emails in Hanami, then where should I place the transformation code in Hanami?

Thx