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

Templates in public directory? #492

Closed
blowsie opened this issue Aug 7, 2017 · 2 comments
Closed

Templates in public directory? #492

blowsie opened this issue Aug 7, 2017 · 2 comments

Comments

@blowsie
Copy link

blowsie commented Aug 7, 2017

Excuse me for my lack of experience with Kraken but..

Today I started using Kraken and noticed the templates are pushed to the ./build folder, and as a result the templates are accessible from the browser.

Is there a reason for this? I tried looking in existing issues but could not find any answer.
The closest discussion i could see was this.
#335

Ultimately my concern here is that source code (OK, only templates.. but still..) is being exposed to the public.

Is there a way to prevent this?

@grawk
Copy link
Member

grawk commented Aug 7, 2017

Presumably you are using a generator-generated application?

You can control where, and if, templates are built to the .build directory via the grunt task configurations.

The reason they are put there, and accessible as static assets, is that you may want to render views on the client side. It's a fairly common use case.

@blowsie
Copy link
Author

blowsie commented Aug 8, 2017

@grawk Yes i used the yo generator. Thanks for the info ill change my configs.

@blowsie blowsie closed this as completed Aug 8, 2017
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