Set up automation for rust-by-example

[brson]

There's significant desire for rust-lang to maintain rustbyexample.com. This will require setting up automation to build, test and publish. Should be similar to that for the guidelines.

Also need to deal with the DNS for rustbyexample.com. May just want to redirect to rust-lang.org/doc/rust-by-example or somesuch.

[steveklabnik]

We can just host on github pages, and it would be pretty trivial. I can implement in an hour or two if that's of interest.

[steveklabnik]

Oh, but not if we want language changes to require updating R4E too. I was thinking a nightly rust-ci buikd would be acceptable.

[strega-nil]

@steveklabnik I think that's good. It doesn't take very much upkeep at all to keep this working, as long as you figure out that it's broken. It's taken me maybe half an hour each of the last times.

Also, the difference between documentation and a tutorial is great; it's much more difficult to automatically build tutorials.

[brson]

@steveklabnik Hosting on github pages is fine (that's where it's currently hosted), at least as long as we want to access it via rustbyexample.com, and not under rust-lang.org/doc. For testing i suppose we can keep using Travis (currently seems broken though), maybe add to http://buildbot.rust-lang.org/travis/travis.html to keep it monitored. Do you have a way to automatically update github pages when PR's are merged?

[steveklabnik]

Do you have a way to automatically update github pages when PR's are merged?

Yes, Travis has deploy hooks, so after a successful build, you can run a script. This script can then do the generation and a git push.

I'll whip something up and show you.

[brson]

This is done, using Travis.

[steveklabnik]

🎊