Recent changes to Release Files for Download

Release Files for Download modified by Dave Brondsema

Dave Brondsema — Wed, 14 Jan 2026 18:54:04 -0000

--- v20
+++ v21
@@ -1,4 +1,4 @@
-SourceForge.net provides a [File Manager](Files) as a means for projects to make files available for download by their users. In addition to the web-based File Manager, SourceForge provides an [interactive-shell service](Shell Service) for managing files. The File Manager and the interactive shell service provide different methods to manipulate the same files and folders. See Accessing Releases via Shell later in this document for more information.
+SourceForge.net provides a [File Manager](Files) as a means for projects to make files available for download by their users. In addition to the web-based File Manager, SourceForge provides access via SFTP, SCP, and Rsync protocols to manipulate the same files and folders. 

 [TOC]

Release Files for Download modified by Guillermo Cruz

Guillermo Cruz — Wed, 13 Aug 2025 22:00:33 -0000

--- v19
+++ v20
@@ -44,12 +44,12 @@
 #[Rsync](rsync)
 Example: user jsmith seeks to put file.zip to the release1 directory of his project, fooproject.  Replace the underscore parts with your details:

-rsync -e ssh file.zip jsmith@frs.sourceforge.net:/home/frs/project/fooproject/release1
+rsync -e ssh file.zip jsmith@frs.sourceforge.net:/home/frs/project/fooproject/release1

 #[SFTP](SFTP)
 Example: user jsmith seeks to put file.zip to the release1 directory of his project, fooproject.  Replace the underscore parts with your details.

-$ sftp jsmith@frs.sourceforge.net
+$ sftp jsmith@frs.sourceforge.net
 Connecting to frs.sourceforge.net...
 jsmith@frs.sourceforge.net's password: 
 sftp> cd /home/frs/project/fooproject/release1

Release Files for Download modified by Guillermo Cruz

Guillermo Cruz — Wed, 13 Aug 2025 21:53:28 -0000

--- v18
+++ v19
@@ -39,7 +39,7 @@
 #[SCP](SCP)
 Example: user jsmith seeks to put file.zip to the release1 directory of his project, fooproject.  Replace the underscore parts with your details:

-scp file.zip jsmith@frs.sourceforge.net:/home/frs/project/fooproject/release1
+scp file.zip jsmith@frs.sourceforge.net:/home/frs/project/fooproject/release1

 #[Rsync](rsync)
 Example: user jsmith seeks to put file.zip to the release1 directory of his project, fooproject.  Replace the underscore parts with your details:

Release Files for Download modified by Dave Brondsema

Dave Brondsema — Tue, 21 Jan 2025 18:49:40 -0000

--- v17
+++ v18
@@ -59,24 +59,11 @@
 sftp>

Note: your project directory (/home/frs/project/fooproject) is available, even if you cannot see it listed.
-#SSH
-Developers may use the Shell service to manage existing files and folders.
-
-Log into the Shell service then your change directory based on your project UNIX name (Example project named "fooproject"):
-
-

cd /home/frs/project/fooproject

#Release notes
The file browser will show any README file it finds in the current folder (or parent folder) below the file listing. This is useful to provide release notes, download instructions, etc. and it is highly recommended you make this available to your end-users. README files must have "readme" in the filename (case-insensitive) and can be plain text, markdown, reStructuredText, or textile formats, using the corresponding filename extension. They are limited to 64KB in size.

-Old per-file release note associations are still accessible by clicking on the "i" icon.

#Known limitations
* Individual files larger than 10 GB will not replicate out to our mirrors and can not be downloaded.
- Moving files may be accomplished via the shell, but cannot be done with the web file manager.
+ Moving files between directories may be accomplished via [SFTP], but cannot be done with the web file manager.
Note: download statistics are based on path and filename, so stats for moved files will be reset. Your total project download count will include the previous name's stats.
-
-#Migration from package/release system
-For projects that had releases available for download at the time of the change to the File Manager facility (July 2009), those files were migrated to logical folders. This is based upon the package & release names.
-
-In addition to the folders created for migrated packages and releases, an "OldFiles" folder was also created which contains files that were previously hidden.

Release Files for Download modified by Dave Brondsema

Dave Brondsema — Tue, 07 Jan 2025 21:48:51 -0000

--- v16
+++ v17
@@ -72,7 +72,7 @@
 Old per-file release note associations are still accessible by clicking on the "i" icon.

 #Known limitations
-* Individual files larger than 8 GB will not replicate out to our mirrors and can not be downloaded. 
+* Individual files larger than 10 GB will not replicate out to our mirrors and can not be downloaded. 
 * Moving files may be accomplished via the shell, but cannot be done with the web file manager.
 **Note**: download statistics are based on path and filename, so stats for moved files will be reset. Your total project download count will include the previous name's stats.

Release Files for Download modified by Dave Brondsema

Dave Brondsema — Mon, 11 Nov 2024 16:50:07 -0000

--- v15
+++ v16
@@ -5,7 +5,7 @@
 #Release Files for Download (FRS)
 Files released using the File Release System (FRS) are automatically distributed to our worldwide network of download mirrors, ensuring file availability, and providing great download performance to users.

-All file releases should be a single file. Multiple files for the same release should be archived together (tar, deb, zip, etc.). We recommend using rsync for all uploads over 20 megabytes in size, as rsync allows for resuming canceled or interrupted transfers.
+All file releases should be a single file. Multiple files for the same release should be archived together (tar, deb, zip, etc.). We recommend using rsync for all uploads over 100 megabytes in size, as rsync allows for resuming canceled or interrupted transfers.

 You must be a project admin or have the "release technician" permission to manage files for a project. There are several ways to manage your files:

@@ -72,11 +72,11 @@
 Old per-file release note associations are still accessible by clicking on the "i" icon.

 #Known limitations
-* Individual files larger than 7 GB will not replicate out to our mirrors and can not be downloaded. 
+* Individual files larger than 8 GB will not replicate out to our mirrors and can not be downloaded. 
 * Moving files may be accomplished via the shell, but cannot be done with the web file manager.
 **Note**: download statistics are based on path and filename, so stats for moved files will be reset. Your total project download count will include the previous name's stats.

 #Migration from package/release system
 For projects that had releases available for download at the time of the change to the File Manager facility (July 2009), those files were migrated to logical folders. This is based upon the package & release names.

-In addition to the folders created for migrated packages and releases, an "OldFiles" folder was also created which contains files that were previously hidden. The "OldFiles" folder is not visible to users downloading files from your project. If you wish to make a file visible, simply move it to a different folder.
+In addition to the folders created for migrated packages and releases, an "OldFiles" folder was also created which contains files that were previously hidden.

Release Files for Download modified by Dave Brondsema

Dave Brondsema — Tue, 16 Apr 2024 14:57:11 -0000

--- v14
+++ v15
@@ -60,7 +60,7 @@

 Note: your project directory (/home/frs/project/fooproject) is available, even if you cannot see it listed.
 #[SSH](SSH)
-Developers may use the Shell service to manage existing files and folders.
+Developers may use the [Shell service](Shell Service) to manage existing files and folders.

 Log into the Shell service then your change directory based on your project UNIX name (Example project named "fooproject"):

Release Files for Download modified by Dave Brondsema

Dave Brondsema — Thu, 25 May 2023 17:24:48 -0000

--- v13
+++ v14
@@ -72,7 +72,7 @@
 Old per-file release note associations are still accessible by clicking on the "i" icon.

 #Known limitations
-* Individual files larger than 6 GB will not replicate out to our mirrors and can not be downloaded. 
+* Individual files larger than 7 GB will not replicate out to our mirrors and can not be downloaded. 
 * Moving files may be accomplished via the shell, but cannot be done with the web file manager.
 **Note**: download statistics are based on path and filename, so stats for moved files will be reset. Your total project download count will include the previous name's stats.

Release Files for Download modified by Dave Brondsema

Dave Brondsema — Mon, 30 Jan 2023 17:53:53 -0000

--- v12
+++ v13
@@ -72,7 +72,7 @@
 Old per-file release note associations are still accessible by clicking on the "i" icon.

 #Known limitations
-* Individual files larger than 5 GB will not replicate out to our mirrors and can not be downloaded. 
+* Individual files larger than 6 GB will not replicate out to our mirrors and can not be downloaded. 
 * Moving files may be accomplished via the shell, but cannot be done with the web file manager.
 **Note**: download statistics are based on path and filename, so stats for moved files will be reset. Your total project download count will include the previous name's stats.

Release Files for Download modified by SourceForge Support

SourceForge Support — Wed, 06 Apr 2022 20:23:46 -0000

--- v11
+++ v12
@@ -1,4 +1,4 @@
-SourceForge.net provides a [File Manager](Files) as a means for projects to make files available for download by their users. In addition to the web based File Manager, SourceForge provides an [interactive-shell service](Shell Service) for managing files. The File Manager and the interactive shell service provide different methods to manipulate the same files and folders. See Accessing Releases via Shell later in this document for more information.
+SourceForge.net provides a [File Manager](Files) as a means for projects to make files available for download by their users. In addition to the web-based File Manager, SourceForge provides an [interactive-shell service](Shell Service) for managing files. The File Manager and the interactive shell service provide different methods to manipulate the same files and folders. See Accessing Releases via Shell later in this document for more information.

 [TOC]

@@ -30,7 +30,7 @@
    * "Download button" allows you to change the label on the download button seen by your visitors.

 * To rename a file or folder, click the "i" icon and edit the name.
-**Note**: download statistics are based on file name, so stats for this file will be reset. Your total project download count will include the previous name's stats.
+**Note**: download statistics are based on the file name, so stats for this file will be reset. Your total project download count will include the previous name's stats.

 * To delete a file or folder, click the "-" icon
 Note: Users are responsible for backing up all of their files. SourceForge.net will not restore individual files.
@@ -67,7 +67,7 @@
 cd /home/frs/project/fooproject

 #Release notes
-The file browser will show any README file it finds in the current folder (or parent folder) below the file listing. This is useful to provide release notes, download instructions, etc. and it is highly recommended you make this available to your end users.   README files must have "readme" in the filename (case-insensitive) and can be plain text, markdown, reStructuredText, or textile formats, using the corresponding filename extension.  They are limited to 64KB in size.
+The file browser will show any README file it finds in the current folder (or parent folder) below the file listing. This is useful to provide release notes, download instructions, etc. and it is highly recommended you make this available to your end-users.   README files must have "readme" in the filename (case-insensitive) and can be plain text, markdown, reStructuredText, or textile formats, using the corresponding filename extension.  They are limited to 64KB in size.

 Old per-file release note associations are still accessible by clicking on the "i" icon.

@@ -79,4 +79,4 @@
 #Migration from package/release system
 For projects that had releases available for download at the time of the change to the File Manager facility (July 2009), those files were migrated to logical folders. This is based upon the package & release names.

-In addition to the folders created for migrated package and releases, an "OldFiles" folder was also created which contains files that were previously hidden. The "OldFiles" folder is not visible to users downloading files from your project. If you wish to make a file visible, simply move it to a different folder.
+In addition to the folders created for migrated packages and releases, an "OldFiles" folder was also created which contains files that were previously hidden. The "OldFiles" folder is not visible to users downloading files from your project. If you wish to make a file visible, simply move it to a different folder.