Summary
Here (https://www.reddit.com/r/cms/comments/1uim2dt/first_peek_at_instatic_fully_opensource/) you mention someone could grab the static files from the UPLOADS folder and this is a great idea for small projects!
I tried this and noticed the path to the CSS generated in the header starts with "/" which means it looks for the root folder. Is there a reason it needs to be that? Couldn't it just start with the path with no slash, if it makes no difference to instatic admin
NOW:
<link rel="stylesheet" href="/_instatic/css/style-3c327afa746e.css">
SUGGESTED:
<link rel="stylesheet" href="_instatic/css/style-3c327afa746e.css">
I suppose the only issue then is that "posts" are in a subfolder at the same level as _instatic.
So why not just put the css folder in the root folder too?
This way the static files can be used anywhere
Just a thought!
Summary
Here (https://www.reddit.com/r/cms/comments/1uim2dt/first_peek_at_instatic_fully_opensource/) you mention someone could grab the static files from the UPLOADS folder and this is a great idea for small projects!
I tried this and noticed the path to the CSS generated in the header starts with "/" which means it looks for the root folder. Is there a reason it needs to be that? Couldn't it just start with the path with no slash, if it makes no difference to instatic admin
NOW:
<link rel="stylesheet" href="/_instatic/css/style-3c327afa746e.css">SUGGESTED:
<link rel="stylesheet" href="_instatic/css/style-3c327afa746e.css">I suppose the only issue then is that "posts" are in a subfolder at the same level as _instatic.
So why not just put the css folder in the root folder too?
This way the static files can be used anywhere
Just a thought!