Development Server Support

[platinummonkey]

This PR adds a few features

1. Adds Development server support via bzl run
2. Adds @ryanrf-ac s archetypes support 881a1bf
3. Makes the relative_path a little more accomodating see Excessively restrictive requirements on source layout #25 master...DataDog:master#diff-2e74d1b13ce9b7645c011139fc5931fdR15-R16
4. Fixes the example site hugo theme
5. Includes generated file support @nitnelave 56a29b8 Add support for generated files #26

[pcj]

Thanks @platinummonkey I'll try this out!

[pcj]

Some good changes in this, but the development server appears to reload on changes to files in the output tree. I don't see an easy way to propagate changes back to the source tree... Was it intended?

An alternative approach would be to use ibazel //site:site in conjunction with a static files server.

[platinummonkey]

Some good changes in this, but the development server appears to reload on changes to files in the output tree. I don't see an easy way to propagate changes back to the source tree... Was it intended?

An alternative approach would be to use ibazel //site:site in conjunction with a static files server.

That's the intent and the workflow I use ibazel $target :)

[pcj]

So then if I understand correctly, using the hugo server here is not to facilitate hot regeneration of outputs, but rather just as a 'hugo-aware' webserver that gets restarted every time ibazel recompiles?

[platinummonkey]

correct, I'll be looking at another iteration where I can hint to ibazel when the runfiles for the hugo generation change explicitly to orchestrate the hot reloading steps

[pcj]

OK, I'll have another look using ibazel. Documentation for the PR should be updated to suggest this workflow.

[f110]

This PR is really useful for me. I appreciated your work!
When I built my site with your PR, I needed to make small changes.

f110@a263d59
This patch makes relative_path to return correctly path if src is top-level.
Without this path, for example, content will be copied to ontent.

[pcj]

Sounds like we should put a little more effort into getting this merged. @platinummonkey what is your status on this? Any other changes planned? Do you want to apply @f110 patch?

[platinummonkey]

@f110 's patch is included now 👍

[platinummonkey]

also getting new files added even with ibazel has this issue: bazelbuild/bazel-watcher#135 so unfortunately this is about as far as we could take it without pushing this issue upstream for add/remove of files. It does detect runfile files that are modified.

[ryanrf-ac]

I don't use ibazel, so I'm not sure if this is out of line for this PR, but I've submitted another PR that allows the use of local theme files, instead of pulling from github, should anyone be interested in merging that with this PR (assuming it's in line with 'development server support').

My workflow is using hugo itself for local development, then having bazel build everything using the same files I've used for local development. This does mean you need to check the theme files into the running bazel, but I think it makes it slightly more deterministic in the long run.

[platinummonkey]

I don't use ibazel, so I'm not sure if this is out of line for this PR, but I've submitted another PR that allows the use of local theme files, instead of pulling from github, should anyone be interested in merging that with this PR (assuming it's in line with 'development server support').

My workflow is using hugo itself for local development, then having bazel build everything using the same files I've used for local development. This does mean you need to check the theme files into the running bazel, but I think it makes it slightly more deterministic in the long run.

happy to include it :) will update this PR by end-of-day

[platinummonkey]

@ryanrf-ac included now 👍

[pcj]

LGTM, thanks @platinummonkey, @f110, @ryanrf-ac.