You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have several development environments (devel_foo, devel_bar, ...) because we develop on different local machines (OS X notebook, Linux server, Windows PC, ...) which all have subtle differences in configuration.
I would love if the environments where silent-postgres is enabled could be configured. Or, alternatively, if the plugin could determine whether Rails::Application.config.log_level is set to :debug, and only then enable itself. (Only during gem initialization, the Rails module is not yet defined).
Thanks :-)
The text was updated successfully, but these errors were encountered:
Hi, sorry for the late response, not sure how do you expect it to work, for example by putting in config/initializers/silent-postgres.rb something like:
# A list of environments in which silencing should take place
SilentPostgres.development_environments = ["devel_foo", "devel_bar"]
? I guess in your case you can't use just Bundler groups to achieve that effect?
Hi - sorry to leave this answer so long. In our "devel_online" and "staging" environments, I am using silent-postgres but it has no effect. I think this is because of if Rails.env.development? || Rails.env.test? in silent-postgres.rb - which doesn't fire when the environment is "devel_online".
Something like an initializer would be really great.
Hello,
I have several development environments (devel_foo, devel_bar, ...) because we develop on different local machines (OS X notebook, Linux server, Windows PC, ...) which all have subtle differences in configuration.
I would love if the environments where silent-postgres is enabled could be configured. Or, alternatively, if the plugin could determine whether Rails::Application.config.log_level is set to :debug, and only then enable itself. (Only during gem initialization, the Rails module is not yet defined).
Thanks :-)
The text was updated successfully, but these errors were encountered: