Hi Greg, I've not seen that site be for, looks pretty interesting.
Building the docs is a quick 1 minute task. I build a number of projects every night with cron jobs. With a few script lines, anyone could build the html. Could also add commit hooks directly too the BerliOS repo. However, transferring the docs to physics.princeton.edu/pulsar/K1JT requires web-server access, which most of us don't have. A simple solution, create a workstation daily task (cron); Add cron job, use whatever time ya like (say, nightly @ 0115 local); 15 1 * * * /path/to/build/sync-script.sh In the script: * svn export .. .. /wsjtx/doc # only need wsjtx/doc/ * cd ./wsjtx/doc && ./build-doc.sh toc2 * rm -rf source/ Then, I'd use rsync between workstation and the web-server: * rsync -azvr wsjtx/doc/ /path/to/web-server/wjtx/doc/ You could use scp, sftp or any number of alternatives, but rsync keeps the file count down, and only transfers incremental diffs. The whole process would not take more than a couple minutes tops. 73's Greg [email protected] On 01/27/2014 05:36 PM, Greg Troxel wrote: > I'm sure Joe can explain how he manages things now, but there is a long > list of tasks that happens at the upstream developer level in preparing > source code for distribution. Writing and building the documentation is > just one of those steps. Unless Joe as a hook of some kind to build and > push the docs to the web-server, I'd imagine this is a manual task after > he tags a revision for public release. > > I am not super familiar with this site, but it appears intended to ease > the work of having a hosted version of built documentation by having > their site watch a public VCS and do triggered builds: > > https://readthedocs.org/ > > > 73 de n1dam > _______________________________________________ Wsjt-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/wsjt-devel
