Always initialize assets environment in rake task

[josh]

#220 causes a slight regression but brings up this weird issue again.

If config.assets.compile = false in production.rb than you can't even do rake assets:precompile.

This is a little work around to force the environment to build even in this case.

@rafaelfranca the environment weirdness between rake assets:precompile has always bugged me. Given 3.x can have backwards incompatible changes, have any idea for directions we can move into to make this more clear?

I really wish rake assets:precompile would work no matter what and always minified the assets even in RAILS_ENV=development. Would like to make it easier for people who compile assets in an isolate environment and upload them to a CDN. This sometimes happens locally on there machine and othertimes in production like environments that might not have a db.

[rafaelfranca]

I really wish rake assets:precompile would work no matter what and always minified the assets even in RAILS_ENV=development.

Yeah, I'd like too but there are some configuration that still changes between environment like the assets prefix and the assets host. I don't have any idea on how change this to not use environment information.

[josh]

Yeah, I dunno either :/

I think at least this compile direction will at least allow rake assets:precompile to do something.

The other issue I'm still worried about is building against an uninitialized app. Is there any flag thats set after initialize! is called? It'd be nice to check app.initialized? (maybe that already works) then maybe print a warning saying, hey, you attempted to compile assets against an non-initialized app, some settings might be wrong, etc.

[rafaelfranca]

It'd be nice to check app.initialized? (maybe that already works) then maybe print a warning saying, hey, you attempted to compile assets against an non-initialized app, some settings might be wrong, etc.

Yeah, initialized? already exists, and a warning would be great.

[josh]

Yeah, initialized? already exists, and a warning would be great.

Bah, so app.initialized? does work but app.initialized? == false inside the config.after_initialize block.

[josh]

A little hacky, just allowing the after_init callback to skip the warning.