Stephen Margheim

icon indicating a website link fractaledmind.github.io icon indicating an email [email protected]

icon location Berlin, Germany icon location Hey, I’m Stephen. I'm an American expat living in Berlin with my wife and two dogs. I am a contributor to Rails and the sqlite3-ruby gem as well as the maintain

Results 153 comments of Stephen Margheim

Using Litestream with no Procfile (such as a dockerized Kamal deploy)

I'm closing after the Puma plugin work as released

Use litestream.io expanded config versus replica_url

Yes, but branch off of #7 and not main. I will be finishing that branch soon, and it is starting to move in a similar direction. So we can avoid...

config.database_path issues

Yes, we are moving away from using `LITESTREAM_DATABASE_PATH` as it restricts Litestream to only backing up one database. The new install generator introspects your `database.yml` and sets up Litestream to...

config.database_path issues

@richjdsmith: Have you gotten this sorted?

Relax dependency on Rails to allow Rails 8

Released with version 0.5.0

More information in the context of each exception

> What do you think about improving the context identification in the gem itself? Would this go beyond the scope you initially imagined? I'm open to the PR, yes.

More information in the context of each exception

> Is there any reason no not use #inspect instead of creating the errors as just the class name? I dropped the `#to_honeybadger` case from the sanitizer, but kept the...

More information in the context of each exception

@everton: Would you like to make the PR to patch controllers and jobs to automatically add context?

Add `SolidErrors::migrated?` to ensure that automatically updated dependencies fail when missing migrations

I have released 0.4.0. There is an upgrade guide: https://github.com/fractaledmind/solid_errors/blob/main/UPGRADE.md But nothing more advanced than that. I'd be open to exploring something similar to GoodJob, but I think an initial...

Patch the action_dispatch executor to report rendered exceptions

I really don't want to have to put a workaround into this gem. I have finished my investigation and I wrote a detailed explanation of what is happening: https://github.com/rails/rails/issues/51002#issuecomment-1936054456 Takeaway:...