ruby - Separate assets repo for multiple Rails apps -

I am using Rail 3 and Ruby 2. I have the following apps:

1. App A
2. App b

Now through App A and App B API, each other Talk to It's SOA, as apps grow more, I found out that the application has CSS and Javascript which can be used again on all apps. I want to separate assets (CSS, JS) into separate repos (such as AppC) so that app A and B can use the same property repo.

These are my questions:

1. For deployment, app c should be precompiled and shortened, and app A and B should point to that repo. What are the options?
2. For development, app C should not be shortened, but how should app C and AC be used to make all changes to the CSS / JS in app?

I searched through Google, but could not find more results. Maybe my keywords were wrong Please feel free to name the rules / conventions used for this exercise.

If there are other better practices, please also give suggestions.

simple option to use one to share asset files between your two projects / applications Maybe for me.

Another option is to have your own gem files in those assets, and use that gem in both of your projects, this will require a little more work, but it is easy to manage the versions under the track (GIT Submissions need some additional manual steps so that you can change the subpload repository to keep things up to date).