|
|
|
@ -71,14 +71,3 @@ ensures your `public/` is "clean" and doesn't contain any random junk that might |
|
|
|
|
> _or_ make my own `os.CopyFS`...but with Blackjack...and...and Hookers. |
|
|
|
|
|
|
|
|
|
After that when you work on the templates it'll sync them over and rebuild your public for you. |
|
|
|
|
|
|
|
|
|
In this example I've removed the comment. Once you do that `ssgod` will then __remove your |
|
|
|
|
public/__ directory on each run, but recreate it from the `static/` and `pages/` directory. This |
|
|
|
|
ensures your `public/` is "clean" and doesn't contain any random junk that might mess up your build. |
|
|
|
|
|
|
|
|
|
> __NOTE__: This is a valid reason to do this, but the technical reason is that Go's `os.CopyFS` |
|
|
|
|
> will error out when the target file exists. Not sure what kind of Nanny-State bullshit is going |
|
|
|
|
> on over at Google but the only viable solution is to just remove the directory that's the target, |
|
|
|
|
> _or_ make my own `os.CopyFS`...but with Blackjack...and...and Hookers. |
|
|
|
|
|
|
|
|
|
After that when you work on the templates it'll sync them over and rebuild your public for you. |
|
|
|
|