On 8 April 2010 23:23, Graeme Geldenhuys wrote: > > Our build servers can then scp or sftp the build status reports > (summary and complete) to the sourceforge tiopf website. This should > be the least amount of modification to our build servers.
I just tried that with the fpGUI project. I already use SSH keys so that I don't need to enter a password when communicating with SourceForge. Executing the following command successfully copied the test.txt file to the website location on SourceForge. $ scp test.txt graemeg,[email protected]:htdocs The file is immediately viewable by the public. http://fpgui.sourceforge.net/test.txt So the SCP (secure copy) idea will definitely work for the build servers. More details of SCP support for SourceForge. Obviously you can use rsync or sftp as well - whatever is easier for you to setup. http://sourceforge.net/apps/trac/sourceforge/wiki/SCP http://sourceforge.net/apps/trac/sourceforge/wiki/SFTP http://sourceforge.net/apps/trac/sourceforge/wiki/Rsync%20over%20SSH -- Regards, - Graeme - _______________________________________________ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ tiOPF-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tiopf-talk
