The rest of the URL should be the path to the artifact relative to the base of the Apache distribution directory.įor example, for artifact foo-1.0.0.tar.gz contained in bar/foo, use /bar/foo/foo-1.0.0.tar.gz The download script substitutes the correct base URL for the variable. See the content to generate that page here.Ī variable URL links to downloadable artifacts. There are a number of elements that a good project download page should contain. download.cgi and release.html will not work.There is no requirement to name the script download.cgi and the download release page download.html, but the name of the script must correspond to the name of the download page. When you link to the project page (for example, from the rest of the project documentation), it is important to target these links at the script address (and not the html page address). This URI takes the path to the page as an input and passes it to a. To use a project-specific download script, create a project page containing information for the user about the release to download, together with variables the script populates with the appropriate values.Īssuming you have called your download page download.html, you can invoke our global download script by using the URI download.cgi. Please read about best practices for download pages. Note: there is some information which every project should include on the download page (e.g. If the artifact is foo-5.5.1.zip and it is located in bar/foo relative to, then the link provides the link for downloading.Īs an alternative, you can generate a direct download link using the following syntax: Pass in the relative path from the distribution root to the artifact as a parameter.Alter the page so the download link points to a.The starting point for using the generic a script is a download page in your project's standard documentation which describes the releases. A project-specific script, which in the end calls a integrated with a page created in the normal way for the project and uses the project's standard document look and feel.The project documentation links to it (rather than integrating it). The a download script is quick to set up.You'll find below a standard mechanism to let you easily create scripts that comply with the ASF distribution policy. Using the a download script ¶Īpache project download pages must use a a script. You can use this for release directories or individual files (if multiple releases are present in a single directory). To remove an old release from the release area, use a command of the form: Once your project no longer recommends public use of a particular release, delete it from /dist/ by removing it from, and removing the link to it from your download page. It is rarely necessary to touch this site, except during a reorganization. This site automatically contains all the content that has ever appeared on /. Older releases that you no longer recommend to the general public still appear on /dist/. Place current, official releases that the PMC has approved for end-users on the main public release site. Move them to one of the two software distribution sites:Ĭurrent public releases appear on /. ) as the KEYS, signatures, and any verification instructions for your release would be missing from the top-level script.ĭo not keep software distributions on your project's website. must not include a link to the top level a utility (e.g.For this you can include a link to the Apache documentation on verification. should have instructions on how to verify downloads.must have a link to the KEYS file for your project on the Apache distribution server.These links must use direct links to the Apache distribution server. must have a link to the checksum for the current release.(Note: the mirrors.cgi and closer.cgi scripts have been deprecated. must have at least one link to the current release.milestones, alphas, betas) in a timely fashion once the project releases the final or GA version. Remove all official pre-releases (e.g.You should remove links to older releases that you no longer support. You may continue to link to recent releases, as well as the latest one, from the download page, as a convenience for the user community. All releases are automatically archived.All links to checksums, detached signatures and public keys must reference the main Apache web site and should use (SSL).Use a, the standard mechanism to distribute Apache downloads.It may include links to binary distributions. The download page must include a link to the source distribution.Your project's download page can only link to release artifacts that your PMC has approved.the policy on release distribution if you are unsure of the best way to use the project download page.This page describes how a release manager can put such a page together. Your project's release download page is where people can download your product's latest release(s).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |