Currently the `db:migrate` rake task runs `dump` at the end which dumps the
database structure to `schema.rb` / `structure.sql`. This will be useful in
development environment but I can't see a reason why this should run in
production environment. Removing this step in production would make
deploym
I agree. Just yesterday, I wrote a separate task that only did migrations
for deploy.
Allen Madsen
http://www.allenmadsen.com
On Fri, Jan 31, 2014 at 1:13 PM, Emil S wrote:
> Currently the `db:migrate` rake task runs `dump` at the end which dumps
> the database structure to `schema.rb` / `stru
I occasionally run diff's on the production schema.rb or structure.sql
against what is in git to be sure development environments are staying in
sync with production.
On Fri, Jan 31, 2014 at 10:13 AM, Emil S wrote:
> Currently the `db:migrate` rake task runs `dump` at the end which dumps
> the
Dear Rails Core,
I believe I have identified a bug related to passing a format block to a mail()
method call (I identified this on Rails 3.2.14, have not tried other versions
of Rails). Contrary to what is documented here
http://guides.rubyonrails.org/action_mailer_basics.html, I was not able
What I meant to write here was "In OS X Mail interface it opens to the Plain
text alternative and if you 'switch to Plain text' you see the HTML version".
In Gmail it also shows the Plain-text version when it should be showing the
HTML version, and there is no option to switch to any other ve
Hi,
I don't know if this is an allowed design in rails, but it seems to me that
it should be. I'll first describe the models and then explain the (what I
feel is, but want confirmation) error. An example repo with instructions on
how to reproduce this can be found here:
https://github.com/sergioca
