tknerr
commented
8 years ago :+1: good idea
As we only have a static site this should be very easily doable. I would probably go for a travis-ci / circleci / z-hosted-teamcity automated build (we want that anyway :-))
- run tests
- run dist build
- publish output of dist build as a build artifact
This should give us a viewable version of the generated site for every commit / feature branch / pull request for free.
I'm doing something similar here:
- for hosting the generated html test report: https://circleci.com/gh/tknerr/linus-kitchen/69#artifacts
- for hosting a build output (tar.gz in that case: https://circleci.com/gh/Zuehlke/cookbook-elk-stack/21#artifacts
You get the idea...
We discuss a lot of thinks here, but we can't try them out and present a new version. It would be immediately live. I think we would benefit from a staging area. Could we implement such a thing easily?
What about a staging branch with a comparable structure as the master branch. Then we could advice interested parties to checkout this branch and assess the result with Firefox. they could even download a zip of this branch. They wouldn't need the toolchain to get involved.
@tknerr , @michaelschnyder: What do you think?