The reason for asset precompilation in production environments isn't just
caching and speed on the first request, it's also that you don't want to
have to have a JS environment (e.g. TheRubyRacer) in production.
2014-11-23 18:32 GMT-05:00 Bráulio Bhavamitra brau...@eita.org.br:
Hello all,
For
On Nov 22, 2014, at 5:03 PM, Sunny Juneja jr.su...@gmail.com wrote:
Hey everyone,
I've obviously done a bad job of explaining this :). Let me try to elaborate.
Suppose I've ran xyz = Model.where(attribute: true)
A SQL query is created and executed. The results are saved to xyz as an
And another reason for pre-compilation is that it can happen on district asset
host boxes or even be pushed to a CDN which the apps use for an asset host.
- Ken
On November 24, 2014 at 10:09:54 AM, James Coleman (jtc...@gmail.com) wrote:
The reason for asset precompilation in production
pushed to a CDN which the apps use for an asset host
I recommend not doing this. You can set up your CDN to pull instead which
is much more sane and less error prone:
https://devcenter.heroku.com/articles/using-amazon-cloudfront-cdn. Source:
hundreds of Heroku support tickets.
assets
Sent from my iPhone
On 24 Nov 2014, at 16:43, richard schneeman richard.schnee...@gmail.com
wrote:
pushed to a CDN which the apps use for an asset host
I recommend not doing this. You can set up your CDN to pull instead which
is much more sane and less error prone:
Likely because you do not have an asset/sprockets cache configured.
http://blog.alexmaccaw.com/faster-deploys
On November 24, 2014 at 11:58:40 AM, Jonathan Lozinski
(jonathan.lozin...@gmail.com) wrote:
It's interesting that you mention that. In development mode (with debug assets
off) the
Hello Richard,
We fix that by making a warm up request just after the server load. See
https://gist.github.com/brauliobo/11298486
cheers,
bráulio
On Mon, Nov 24, 2014 at 1:43 PM, richard schneeman
richard.schnee...@gmail.com wrote:
pushed to a CDN which the apps use for an asset host
I
BTW, new Rack support warm up.
On Mon, Nov 24, 2014 at 2:01 PM, Bráulio Bhavamitra brau...@eita.org.br
wrote:
Hello Richard,
We fix that by making a warm up request just after the server load. See
https://gist.github.com/brauliobo/11298486
cheers,
bráulio
On Mon, Nov 24, 2014 at 1:43
Hello Ken,
This is not good enough as the rails server is going to be reached for each
asset request. You want nginx or another server to serve assets.
cheers,
bráulio
On Mon, Nov 24, 2014 at 2:00 PM, Ken Collins k...@actionmoniker.com wrote:
Likely because you do not have an asset/sprockets
Serving in milliseconds
This is because sprockets doesn't generate hashes, remove whitespace,
compress javascript, or compile all JS to one file.
If you don't need any of those things then don't use the asset pipeline,
store your assets in `/public` and serve them individually.
Likely because
I use turbo-sprockets (requires a custom buildpack) on Heroku on my Rails 3 app
and it works great. Deploys are very fast.
-Jason
On Nov 24, 2014, at 12:15 PM, richard schneeman richard.schnee...@gmail.com
wrote:
Serving in milliseconds
This is because sprockets doesn't generate
Sent from my iPad
On 24 Nov 2014, at 17:15, richard schneeman richard.schnee...@gmail.com
wrote:
Serving in milliseconds
This is because sprockets doesn't generate hashes, remove whitespace,
compress javascript, or compile all JS to one file.
If you don't need any of those things
12 matches
Mail list logo
