Great work Simon. This is going to make things a lot easier for us. Does Cargo support this same doc generation step easily?
jack. On Thu, Aug 7, 2014 at 6:56 AM, Simon Sapin <simon.sa...@exyr.org> wrote: > Hi all, > > http://doc.servo.org/ is now live! It’s the rustdoc documentation for > Servo master, including all submodules and Rust, at the specific versions > that are being used. Time to write some doc-comments! > > It’s hosted by GitHub Pages in a dedicated repository: > https://github.com/servo/doc.servo.org > (For a while it was in the servo repository but I dislike having generated > files in the source repo, even on an independent branch.) > > Every time we push to servo master, Travis-CI re-generates the > documentation as part of its build and pushes it to doc.servo.org. An > "orphan" branch is created and force-pushed every time, so there is not > history of generated files. (If needed, they can be re-created from the > history of the source repository.) > > You can generate docs locally with 'make doc' (for everything), or 'make > doc-<name>' for a only a given submodule or Servo crate. The results go > into a 'doc' directory directly in the build directory. > > > http://servo.org/ is now also on GitHub Pages, backed by > https://github.com/servo/servo.org/ . For now it only redirects to the > GitHub repository, but that can change easily when we have something to put > there more interesting that what’s already in the README. ( > http://www.servo.org/ redirects to http://servo.org/) > > > By the way, the way to request changes to the DNS configuration is to file > a bug in bugzilla, in the "mozilla.org" product and "Server Operations" > component. > > Cheers, > -- > Simon Sapin > _______________________________________________ > dev-servo mailing list > dev-servo@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-servo > _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
