Issue 83 - Upload area needed in tools/www
Summary: Upload area needed in tools/www
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Downloads (show other issues)
Version: current
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-11-02 08:54 UTC by Martin Hollmichel
Modified: 2003-12-06 14:52 UTC (History)
2 users (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Martin Hollmichel 2000-11-02 08:54:02 UTC
We need an upload area for the tools project, to provide some binary files. We 
expect that the level of access is low in comparision to source tarball 
downloads. I think we need ca. 150 MB Disk Space for thst.
Comment 1 Unknown 2000-11-02 19:41:53 UTC
refiling this under 'www' since it has nothing to do with OpenOffice itself.
Comment 2 Unknown 2000-11-02 20:04:27 UTC
I've set this up using the existing SSH upload capability on openoffice.org.

I created a tools subdir in ~upload for this purpose. Uploading files into
that directory in ~upload will make them available under
http://tools.openoffice.org/download/ (you must supply the full filepath
to the exact names of the files uploaded in order to retrieve them.
Directory indexing is disabled, therefore, you must have explicit links from the
tools.openoffice.org project home page to this page.)

Using your existing SSH certs for upload@openoffice.org, simply do

   scp <file> upload@openoffice.org:tools/.

now you can access the file just uploaded at URL
	http://tools.openoffice.org/download/<file>
Comment 3 michael.bemmer 2003-03-24 08:22:06 UTC
As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.
Comment 4 michael.bemmer 2003-03-24 08:26:35 UTC
As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.