Rails 3.1 - sharing precompiled assets across servers?

The answer to this is probably to share the assets manifest file between apps. This file contains mappings for raw filenames to the ones with fingerprints in them This is at public/assets/manifest. Yml by default.

I suggest that when you deploy App 2 you add a task to grab the asset manifest from App 1, and assuming that App 2 does not have any compiled assets (because you have changed the host) just use that for the app. You would have to set the config to make App 2 think it has compiled assets.

The answer to this is probably to share the assets manifest file between apps. This file contains mappings for raw filenames to the ones with fingerprints in them. This is at public/assets/manifest.

Yml by default. I suggest that when you deploy App 2 you add a task to grab the asset manifest from App 1, and assuming that App 2 does not have any compiled assets (because you have changed the host) just use that for the app. You would have to set the config to make App 2 think it has compiled assets.

Woohoo, awesome! Thanks so much. I spent half a day searching on this and never saw a mention of this.

Good thinkin'! – 99miles Sep 30 at 15:39.

App 2 has precompiled assets and everything works great. Now App 1 wants to use the same CSS file as App 2 that resides on server B. Is there a way to make this work?

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions