Disabling sending data in development environment

[wjessop]

What's the recommended way of setting the gem up for Rails? I'm looking for:

• Not sending data in development mode (ideally logging instead)
• Making the posthog client available to Ruby code in the app (controllers, models etc.). I see one guide recommends assigning the client to $posthog, but does this work in forking threaded servers such as Puma?

[pauldambra]

hey @wjessop long time no see

saw this issue while i was here doing something else 👋

I only recently added a before_send function to posthog web sdk. so added the same here just in v2.11.0

so now in dev mode you could log the event and return nil

I see one guide recommends assigning the client to $posthog, but does this work in forking threaded servers such as Puma?

@rafaeelaudibert is probably better placed to answer than I am

we should at a minimum have a playground/examples folder like the websdk

would love to have more framework specific advice/sdks though (in the web world as well as here and python etc etc etc 😅)