Hi, if you want to use only HTTPS with all secure options, I recommend you
to uncomment the default production environment option in
config/environments/production.rb :
# Force all access to the app over SSL, use Strict-Transport-Security,
and use secure cookies.
# config.force_ssl = true
For a release there needs to be need. I.e. we won't just release the same code
over and over, there needs to be meaningful patches. It also takes coordination
and human power. Releasing is a non-trivial task. You can always use `github:
'rails/rails', branch: '4.2'` in your gemfile if you need m
What is the process for determining when to release the next in the 4.2
series (4.2.8)? Is there a generally expected timeframe between releases?
Or is it waiting on specific fixes?
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To uns
Your question was addressed here:
https://github.com/rails/rails/issues/25896
On Wed, Sep 7, 2016 at 5:05 AM, Chad Woolley
wrote:
> Hi,
>
> As you can see here:
>
> https://github.com/rails/rails/blob/5-0-0/activerecord/lib/active_record/
> transactions.rb#L214
>
> ...there's no docs, and it's n
Hi,
As you can see here:
https://github.com/rails/rails/blob/5-0-0/activerecord/lib/active_record/transactions.rb#L214
...there's no docs, and it's not mentioned in any of the guides.
Is this intentional, or an oversight?
Thanks,
-- Chad
--
You received this message because you are subscribe
