<div dir="ltr">yes, post-receive hook </div><div class="gmail_extra"> <div class="gmail_quote">On Wed, May 4, 2016 at 9:33 AM, Markus Seeber <<a href="mailto:markus.seeber@spectralbird.de" target="_blank">markus.seeber@spectralbird.de</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'd go with the hook variant then. This allows me to drop the _site dir from the repository entirely, avoiding the hassle of committing it. This is implemented as a "post-receive" hook I guess? <div class="HOEnZb"><div class="h5"> On 05/04/2016 01:49 PM, Paul Davis wrote: > For <a href="http://ardour.org" rel="noreferrer" target="_blank">ardour.org</a> and <a href="http://community.ardour.org" rel="noreferrer" target="_blank">community.ardour.org</a>, we mirror the git repo to the > webserver and make it rebuild the page(s) after a receiver. It works pretty > easily - edit, commit, push ... gets mirrored automatically, website is > rebuilt. > > But I'm fine with any approach, really. It is true that the > rebuild-on-server thing does make slightly more of a demand on the > webserver config. > > > On Wed, May 4, 2016 at 5:04 AM, Markus Seeber <<a href="mailto:markus.seeber@mailbox.org">markus.seeber@mailbox.org</a>> > wrote: > >> I will think about that since that could solve some other problems too, >> like being able to insert build date or commit hash or a tag into the >> generated page. >> >> Would you prefer the webserver to rebuild the page after a push? This >> would require jekyll to be available on the webserver in the required >> version (maintenance effort). >> The other possibility would be to have discrete releases where _site is >> rebuilt and tags are created, which would not require jekyll on the >> webserver. >> Depends on how you or anyone else maintaining the hosting would like to >> have that handled. >> >> If no decision is made, I'd rather tag discrete releases for now. >> >> On 05/03/2016 08:48 PM, Paul Davis wrote: >>> Well, either that or there needs to be post-pull hook that rebuilds _site >>> ... >>> >>> On Tue, May 3, 2016 at 2:37 PM, Markus Seeber < >> <a href="mailto:markus.seeber@spectralbird.de">markus.seeber@spectralbird.de</a> >>>> wrote: >>>> This is correct. It is in sync with the changes I mentioned with the >>>> last "pull request mail". The reason for not rebuilding "_site" on every >>>> commit is, that changes to markdown files may generate a lot of changes >>>> in "_site" so I do not commit "_site" on every change. >>>> >>>> I can create tags in future to signal a release, would this be >> appropriate? >>>> On 05/03/2016 08:05 PM, Paul Davis wrote: >>>>> Markus - pulled the site, but the contents of the _site folder/dir do >> not >>>>> appear up to date ... >>>>> >>>>> On Wed, Apr 6, 2016 at 12:38 PM, Markus Seeber < >>>>> <a href="mailto:markus.seeber@spectralbird.de">markus.seeber@spectralbird.de</a>> wrote: >>>>> >>>>>> On 04/05/2016 03:38 PM, JoergSorge wrote: >>>>>>>> Do you think the software is in a state such that end users can >> build, >>>>>>>> install, configure and use it themselves? >>>>>>> That's a good question ;-) I know, I have a lot to do to make install >>>>>>> and docs user friendly... >>>>>>> Regards Jörg >>>>>>> >>>>>> I tracked your request anyway: >>>>>> <a href="https://github.com/jackaudio/jackaudio.github.com/issues/45" rel="noreferrer" target="_blank">https://github.com/jackaudio/jackaudio.github.com/issues/45</a> >>>>>> >>>>>> If you think it is worth sharing, I'll include it. >>>>>> >>>>>> Best regards >>>>>> Markus >>>>>> _______________________________________________ >>>>>> Jack-Devel mailing list >>>>>> <a href="mailto:Jack-Devel@lists.jackaudio.org">Jack-Devel@lists.jackaudio.org</a> >>>>>> <a href="http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org" rel="noreferrer" target="_blank">http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org</a> >>>>>> >> </div></div></blockquote></div> </div>