The new website directory

[Mark Atwood]

Hi Eric, everyone:

The website canonical repo is the one on gitlab.  I asked Amar to use the
gitlab push hooks so that pushes to that repo would rebuild the HTML and
put the results on the web server.

We had to move our web pages off GitHub Pages to our own web server, to
solve the problem of bricking someone's browser against our site if they
manually typed "https://ntpsec.org".

I myself find it useful to have WAF rebuild the HTML, because I don't have
asciidoc installed on every machine I may be using when editing the site.

Plus I was noticing random changes in the site stemming from me having
slightly different versions of asciidoc installed than other team members.
Changing it to being built via the push hooks solved that problem.

Open a bug on the issue tracker about the favicon, and Amar will be able to
fix it.

Thanks!

..m

On Sun, Nov 22, 2015 at 7:41 PM Eric S. Raymond <esr at snark.thyrsus.com>
wrote:

> You wrote this:
>
> >I converted the WWW repo to waf and put it on oldtimer in
> >
> >  /data/git/www-asciidoc.git
> >
> >I will hookup buildbot to build and then install to www.ntpsec.org after
> every
> >commit.
> >
> >Please take a look at the repo to make sure it works for everyone here.
> It
> >should.  Usage is simple:
> >
> >  # waf configure --prefix=/path/to/www/
> >  # waf install
> >
> >You don't need to install it to view it just go to the build/ dir and open
> >index.html it will work fine.
>
> And then this:
>
> >In order to see the site add:
> >
> >140.211.9.65   www.ntpsec.org  nwww
> >
> >To your hosts file.
> >
> >The source is built and installed after every commit via Buildbot:
> >
> >  https://buildbot.ntpsec.org/#/builders/13
> >
> >I will enable it after I'm given the all-clear.  This will fix our SSL
> issues.
>
> You didn't specify an URL to clone from.  I had to figure out that it
> was ssh://esr@oldtimer.ntpsec.org/data/git/www-asciidoc.git
>
> One I cloned it, I found that the README still said
>
> >Edit cycle:
> >
> >1. Modify the asciidoc.
> >
> >2. Run 'rebuild' to generate HTML from the masters.
> >
> >3. Commit everything, then push.
> >
> >The github.io site ignores the .txt files and makes the HTML visible.
> >
> >The HTML is normally write-locked to remind you not to modify it.
>
> even though there is no rebuild script there any more.  Your change
> may have been well-intentioned, but because you failed to document
> it properly you have changed a setup I knew how to use into a setup
> I don't know how to use.
>
> I am left with the following questions:
>
> 1. If I modify a .txt file and push it, will the corresponding *.html
>    file be created and published?
>
> 2. If not, what rebuild step must I perform?
>
> 3. Why did the site favicon stop being displayed?  What can be done to
>    fix that?
>
> 4. Why is waf involved at all?
>
> 5. What problem was this solving?  Why were you making apparently
>    gratuitous changes to the website publishing machinery when what
>    0.9.1 most needs from you is for all the unit tests to work?
> --
>                 <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
>
> The right of self-defense is the first law of nature: in most
> governments it has been the study of rulers to confine this right
> within the narrowest limits possible.  Wherever standing armies
> are kept up, and when the right of the people to keep and bear
> arms is, under any color or pretext whatsoever, prohibited,
> liberty, if not already annihilated, is on the brink of
> destruction."
>         -- Henry St. George Tucker (in Blackstone's Commentaries)
> _______________________________________________
> devel mailing list
> devel at ntpsec.org
> http://lists.ntpsec.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ntpsec.org/pipermail/devel/attachments/20151123/bbe4496d/attachment.html>