-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recompiling on reach request #55
Comments
Reverting to 0.3.0 seems to fix the problem. |
What filename was in the link-to-asset, and what filenames existed on the system? Is this the same problem from #9 (comment)? If so, I think we should look at a documentatin fix. |
Okay, I don't believe this is related to #9. Even with a patched version of 0.4.0, Dieter with FYI: I'm not precompiling, just having it compile at run time. |
Is it possible this is also fixed in the |
I intended :production to be used with precompilation - I didn't consider that it might compile once and cache. I think. I'll definitely take a patch for this. Thanks! |
Ah, that makes sense. I think precompilation is the better long-term solution for most projects anyway. Perhaps its behavior is simply worth documenting. Many of us (me included) come from Rails' asset pipeline, which, if it cannot find cached assets in production at runtime, it makes them. I'm still too unfamiliar with Dieter's internals, so I'd be happy to document the behavior, and perhaps submit a patch when I can navigate the code a bit better... |
I don't mean to be such a pest; I'm just struggling to understand the workflow. I set If I change There's either a bug, or I'm missing something simple. I'd be happy to patch up documentation for other noobs like me. |
Can you post your dieter-options? Do you have |
In production it's recompiling the assets with each request:
The timestamp changes with each request. I'm using
link-to-asset
as instructed.Am I missing something?
The text was updated successfully, but these errors were encountered: