Changes between Version 59 and Version 60 of Release files for download
- Timestamp:
- 12/01/10 21:05:50 (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Release files for download
v59 v60 10 10 ---- 11 11 12 = Upload Quick Start Guide =13 14 12 '''''Note:''''' Allowed characters for files and directories are: -_ +.,=#~@!()[]a-zA-Z0-9 (including " " - space). Disallowed characters are: &:%?/*$ Filenames may not start with a space or dot ("."), and may not end with a space (" "). 15 13 16 You must be a project admin or have the "release technician" permission to manage files for a project. 14 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: 17 15 18 = = File Manager (Web) ==16 = File Manager (Web) = 19 17 20 18 Select `Files` from the Project menu. This is both the file manager (for admins) and the file browser (for visitors). … … 32 30 * "Default download for" controls which file is the recommended download for visitors, based on their OS. If not set for any file in the project, heuristics are used to automatically pick a recent upload with an appropriate file extension for the OS. 33 31 34 = = SCP ==32 = SCP = 35 33 36 34 User `jsmith` seeks to put `file.zip` to the `Rel_1` directory of his project, `fooproject`: … … 40 38 }}} 41 39 42 = = Rsync ==40 = Rsync = 43 41 44 42 User `jsmith` seeks to put `file.zip` to the `Rel_1` directory of his project, `fooproject`: … … 48 46 }}} 49 47 50 = = SFTP ==48 = SFTP = 51 49 52 50 User `jsmith` seeks to put `file.zip` to the `Rel_1` directory of his project, `fooproject`: … … 63 61 }}} 64 62 63 = SSH = 64 65 Developers may use the [wiki:"Shell service"] to manage existing files and folders. 66 67 Log into the [wiki:"Shell service"] then your change directory based on your project UNIX name (Example project named "fooproject"): 68 69 {{{ 70 cd /home/frs/project/f/fo/fooproject 71 }}} 72 65 73 ---- 66 74 67 The file you have uploaded will be available for download from the worldwide mirror network, shortly after upload has been completed. 75 [wiki:"File management service"] 68 76 69 = = Release notes ==77 = Release notes = 70 78 71 79 The File Manager allows a file to be set as the release note of a release. Once set, the release note will be viewable by clicking on the release note icon in the "Notes/Subscribe" column on the Files page. How the file is displayed will vary dependant on the type of file: … … 76 84 Release notes are set by [wiki:"Release files for download#EditingFileDetails" setting a file as a release note, then associating a file/folder to it]. 77 85 78 [wiki:"File management service"] 86 = Known limitations = 79 87 80 == Accessing Releases via Shell == 88 Moving files and creating of symlinks may be accomplished via the shell, but cannot be done with the web file manager. 81 89 82 Developers may use the [wiki:"Shell service"] to manage file releases and the file release structure. 90 = Migration from package/release system = 83 91 84 Log into the [wiki:"Shell service"] then your change directory based on your project UNIX name (Example project named "fooproject"): 92 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. 85 93 86 {{{ 87 cd /home/frs/project/f/fo/fooproject 88 }}} 94 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. 89 95 90 == Migration of existing files and known issues ==91 92 For projects that had existing files available for download at the time of the change to the File Manager facility, those files will be migrated to logical folders. This is based upon the package & release names.93 94 In addition to the folders created for migrated package and releases, an "!OldFiles" folder is 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.95 96 The following features may be accomplished via the shell for release folders:97 98 * Creation of symlinks.99 100 These functions may not be achieved using the file manager.101 96 102 97 = Getting Help =
