keystonejs/keystone-classic

Make less files not publicly available

Open

#1,639 创建于 2015年9月2日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)JavaScript (14,656 star) (2,288 fork)batch import
bughelp wanted

描述

Every file under /public/styles/ is available through http when keystone is running.

Since *.less files could be considered as a part of the source code, could we move them to another location, e.g. /templates/styles/ to protect them from being available publicly?

It may be a good idea to keep /public/ folder only for files that are required during runtime, and keep source files elsewhere.

贡献者指南

技术栈
javascriptnodejscss
领域
securitybackend
议题类型
security
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Keystone file structureLess CSSNode.js static serving
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
65
研究方向
Investigate the current file structure under /public/styles/ and /templates/ to understand how Keystone serves static assets. Identify all references to style files in the application (e.g., in templates, layout files, or server configuration) that would need updating after the move. Check if there are any existing mechanisms to prevent public access to certain file types, and consider if a more general solution (like a .htaccess or middleware) is preferred. Review any comments on the issue for maintainer guidance on the desired approach.