Skip to content
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

Best Practice / Example for "thave a separate manifest file for each section" #226

Open
shamelesshacker opened this issue Dec 17, 2014 · 1 comment

Comments

@shamelesshacker
Copy link

This paragraph from the READ.me alludes to precisely the issue.

If you find yourself having issues with conditionally including assets your best bet may be to break apart
your manifest files into sections that make sense for your application. For example, if your application is
silo'ed into admin section and user section then it probably makes sense to have a separate manifest
file for each section.

Specifically, I need guidance on the best way to isolate both the "admin" and "front end" sections of my site. If anyone has solved this in an elegant way, the advice would be appreciated.

@kticka
Copy link

kticka commented Feb 25, 2015

Well, you can have two directories in your assets folder. For example 'frontend' and 'backend'. Each of them should have different manifest file, which you can include by javascript_include_tag(). For example javascript_include_tag('backend/manifest') or javascript_include_tag('frontend/manifest'). I my app I have organized assets not exact, but in quite similar way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants