Author: assaf
Date: Fri Jun 27 17:18:47 2008
New Revision: 672437
URL: http://svn.apache.org/viewvc?rev=672437&view=rev
Log:
Added to documentation: file upload supports HTTP and file system in addition
to SFTP.
Modified:
incubator/buildr/trunk/doc/pages/packaging.textile
Modified: incubator/buildr/trunk/doc/pages/packaging.textile
URL:
http://svn.apache.org/viewvc/incubator/buildr/trunk/doc/pages/packaging.textile?rev=672437&r1=672436&r2=672437&view=diff
==============================================================================
--- incubator/buildr/trunk/doc/pages/packaging.textile (original)
+++ incubator/buildr/trunk/doc/pages/packaging.textile Fri Jun 27 17:18:47 2008
@@ -508,13 +508,16 @@
repositories.release_to = 'sftp://john:[EMAIL PROTECTED]/usr/share/repo'
}}}
-We're using the SFTP protocol, currently the only protocol Buildr uses for
-uploads. The URL contains the release server ("release"), path to repository
-("user/share/repo") and username/password for access. The way SFTP works, you
-specify the path on the release server, and give the user permissions to create
-directories and files inside the repository. The file system path is different
-from the path you use to download these artifacts through an HTTP server, and
-starts at the root, not the user's home directory.
+This example uses the SFTP protocol. In addition, you can use the HTTP
+protocol -- Buildr supports HTTP and HTTPS, Basic Authentication and uploads
+using PUT -- or point to a directory on your file system.
+
+The URL in this example contains the release server ("release"), path to
+repository ("user/share/repo") and username/password for access. The way SFTP
+works, you specify the path on the release server, and give the user
+permissions to create directories and files inside the repository. The file
+system path is different from the path you use to download these artifacts
+through an HTTP server, and starts at the root, not the user's home directory.
Of course, you'll want to specify the release server URL in the Buildfile, but
leave the username/password settings private in your local @buildr.rb@ file.
