You can use whatever initializer, it doesn't matter, but I would create new initializer to avoid mixing things.
El miércoles, 22 de febrero de 2017 3:03:32 (CET) Chee Chong Hwa escribió: > HI Sergio > > IN your excellent article at > https://github.com/activescaffold/active_scaffold/wiki/Speed-Up-Startup-Time > > ActiveScaffold setup can be delayed until is required, that is when > active_scaffold_config is called or an action is requested to that > controller. ActiveScaffold setup is not very slow but can be long if you > have many controllers using ActiveScaffold. Enabling delayed setup, config > block won’t run and actions modules won’t be included until is needed, > speeding up the booting of your app, mainly when there are many controllers > using ActiveScaffold. To enable this, add an initializer to > config/initializers with this line: > > ActiveScaffold.delayed_setup = true > > In Rails 5, there is a number of config/initializers files such as : > > *application_controller_renderer.rb > *assets.rb > backtrace_silencer.rb > cookies_serializer.rb > filter_parameter_logging.rb > inlections.rb > mime_types.rb > new_framework_default.rb > session_stores.rb > wrap_parameters.rb -- You received this message because you are subscribed to the Google Groups "ActiveScaffold : Ruby on Rails Gem" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/activescaffold. For more options, visit https://groups.google.com/d/optout.
