EnigmaCurry/blogofile

Build error default behaviour

Opened this issue · 2 comments

As I symlink the _site build directory on the document root of the web server, every build error that I do makes the user trying to access my site via the web address on its browser get the default index page of the web server, with nothing interesting there.

Could blogofile at least build one index page to acknowledge the administrator did something wrong, instead of the current behaviour (empty the _site directory at all), or should I configure the web server to detect that and do something on its side?

A more typical deployment strategy is to build the site offline to confirm that it builds cleanly and then copy or sync the results into the public location. There are lots of ways to automate the latter part of that workflow: shell scripts, tools like fabric, mercurial/git hooks, etc.

Indeed it seems like a better pratice. It should be on the docs as a reccomendation.
What i did was building the site and telling the script to copy the files to the webserver directory only in the case of a sucessfull build.