See the example here https://github.com/rails/rails/issues/16206
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rubyonrails-core+unsubscr...@googlegroups
Ah, I see what you mean now. Yeah, that seems reasonable.
On Monday, July 28, 2014 at 10:27 AM, Pete wrote:
> Hi,
>
> maybe there was a slight misunderstanding - I think SSL should be set
> application-wide once config.force_ssl = true is set.
>
>
>
> On Monday, July 28, 2014 4:13:46 PM
Hi,
maybe there was a slight misunderstanding - I think SSL should be set
*application-wide* once config.force_ssl = true is set.
On Monday, July 28, 2014 4:13:46 PM UTC+2, Geoff Harcourt wrote:
>
> Hi Pete,
>
> I don’t think it’s necessary to require SSL in development, so even if
> enabling
Hi Pete,
I don’t think it’s necessary to require SSL in development, so even if enabling
SSL by default in production environments is a good idea (which I’m not
convinced is necessary), I think requiring it in development is overkill, and
makes the path to getting started on an app more complic
If we apply the logic "specify as much as possible on the highest level
possible", then config.force_ssl = true should also set SSL for
ActionMailer (and its url helpers), meaning application-wide and by
default).
The following requirement should then be a thing of the past:
# development.rb c
On 28-07-2014 09:40, Xavier Noria wrote:
I think this motivation can be summarized as: #prepend has use cases,
in particular for singleton classes.
I don't see this in AS. AS is defined as a fine balance:
* Ruby extensions key for Rails core development.
* Ruby extensions experience p
I think this motivation can be summarized as: #prepend has use cases, in
particular for singleton classes.
I don't see this in AS. AS is defined as a fine balance:
* Ruby extensions key for Rails core development.
* Ruby extensions experience proves to be really really
helpful/comm
Sometimes we'd like to monkey patch some classes/modules from external
libraries for many reasons including bug fixes until a new library
version is released or maybe we need to change the default behavior of
some class. For instance, the active_record_migrations gem will allow
migrations to be
