具有独立设计和布局的多个导轨叉
我有一个 Rails 项目，它基本上是一个针对会员制组织的简单 Web 应用程序。我们已将 Web 应用程序的 Github 上的代码开源，以便其他人可以使用它，但原始组织将使用的许可设计/布局。此布局无法开源。我想知道其他人是否遇到过这样的情况：您有一个非操作系统设计的开源 Rails 应用程序。
我最初的想法是将 app/views 放在 .gitignore 中，并让任何分叉代码的人添加自己的视图目录，也许包括带有 web-app-theme 布局的 app/views_default 目录或其他让人们运行的目录。这是最好的选择吗（意识到布局附带的其他文件，如 JavaScript、CSS 等也必须被忽略）。
有人对此有一些好的想法或建议吗？
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?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Hoopla - Git 的 svn:externals.
您可以将非开源内容推送到其他地方，并将开源代码推送到 github 上，而不是使用 git:ignore。使用hoopla 来管理外部。
http://6brand.com/git-svn-externals-rails-plugins。 html
Hoopla - svn:externals for Git.
Instead of git:ignore, you can push the non-open-source stuff somewhere else, and your open-source code on github. Use hoopla to manage the externals.
http://6brand.com/git-svn-externals-rails-plugins.html
Rails Theme_Support 插件： http://github.com/aussiegeek/theme_support （也有分支） 。您可以创建一个包含多个主题的主题目录，并在 ApplicationController 中以编程方式加载主题。这将允许任何人使用该应用程序，并且只需在主题目录中提供自己的主题，并且允许该项目有一个“默认”主题作为示例。
Rails Theme_Support plugin: http://github.com/aussiegeek/theme_support (There are forks as well). You can create a theme directory with multiple themes, and load the theme programmatically in ApplicationController. This would allow anyone to use the application, and simply supply their own theme in the themes directory, and would allow the project to have a "default" theme which would serve as an example.