Multiple Rails forks with separate designs and layouts

Posted by mettadore on Stack Overflow See other posts from Stack Overflow or by mettadore
Published on 2010-06-01T04:51:36Z Indexed on 2010/06/07 16:42 UTC
Read the original article Hit count: 188

Filed under:
|
|

I have a Rails project that is basically a simple web app for a membership-based organization. We've open sourced the code on Github for the web app so that others can use it, but have a licensed design/layout that the original organization is going to use. This layout cannot be open sourced. I was wondering if others have run into the situation where you have an open-source Rails app with a non-OS design.

My initial thought is to put app/views in .gitignore, and to have anyone forking the code add their own views directory, perhaps including an app/views_default directory with a web-app-theme layout or something else to get people running. Is this the best option (realizing that there are other files such as JavaScript, CSS, etc that come with the layout that must also be ignored).

Does anyone have some good thoughts or pointers on this?

© Stack Overflow or respective owner

Related posts about ruby-on-rails

Related posts about design