search

cloudflare / Stout

A reliable static website deploy tool
MIT License
751 stars 29 forks source link

Deploy halts when JS library can't be found #18

Closed tazmaniax closed 8 years ago

tazmaniax commented 8 years ago

Hi, it looks like if a referred to JavaScript file can't be found then the deploy is halted. Is it possible to ignore this situation and continue with the deployment? I'm probably including more files than necessary but probably won't do any harm. Is there a way to exclude specific files or directories?

thanks

$ stout deploy --env staging panic: open app/bower_components/lodash/node_modules/platform/platform.js: no such file or directory

goroutine 1 [running]: panic(0x44fe40, 0xc8202f0e10) /usr/local/go/src/runtime/panic.go:481 +0x3e6 main.must(0x4e2b20, 0x0, 0x8949f8, 0xc8202f0e10, 0x0, 0x0) /Users/zack/s/Stout/src/utils.go:86 +0x57 main.hashFile(0xc82029d2c0, 0x3d, 0x0, 0x0, 0x0) /Users/zack/s/Stout/src/deploy.go:48 +0x1d4 main.hashFiles(0xc8202fa000, 0x2a, 0x40, 0x0, 0x0) /Users/zack/s/Stout/src/deploy.go:66 +0x11a main.Deploy(0x4f6120, 0x1, 0xc82001146c, 0x4, 0x4f62e8, 0x2, 0x0, 0x0, 0x7fff5fbffc7b, 0x7, ...) /Users/zack/s/Stout/src/deploy.go:572 +0x15f7 main.deployCmd() /Users/zack/s/Stout/src/deploy.go:626 +0x137 main.main() /Users/zack/s/Stout/src/cli.go:39 +0x3e3

zackbloom commented 8 years ago

Sorry, this is works as designed. A file which will fail with Stout would 404 if your site was actually deployed.

tazmaniax commented 8 years ago

But this is file that would never be called on the client side. Just happens to be included in the distribution package.

zackbloom commented 8 years ago

Ah, this generally happens when Stout is building HTML files you don't need it to be building. I would look into the files command line or config file option, which will allow you to have it ignore your bower_components folder.

tazmaniax commented 8 years ago

I thought had checked the config options but I'll check again, thx