The media server is used to server big files. This is done to reduce the load of the main server (www.tuhh.de) which is created from the download of bigger files.

How can I use the Media-Server?

If your Institute wants to use the media server send an email to the Service Desk of the computer center and name a functional account to which the files should belong to.

Upload or Delete Files

You can upload files with the functional account to the ssh server ssh.rz.tuhh.de. You can either use the scp command or an sftp client. If your are working with Windows you need to install a program for example WinSCP. For Linux the command-line utilities are usally installed by default, most file managers allow to upload file via scp, too.

After the start of the programm, connect the functional account to the server ssh.rz.tuhh.de and change into the assigned directory an. The pathname on the ssh server is: /nfs/media/htdocs/sign. Upload your file there and the files will be ready to download from media.tuhh.de/<sign>/<path>/<filename>.

The deletion of the file works in the same way.

Request Filequota

• Command on the ssh server:

  quota -m username

http://media.tuhh.de/sign/directory/file

Examples

If the computer center would like to share a file named "example.zip" on the media server, the URL would be:

http://media.tuhh.de/rzt/example.zip

If the the computer center moves the file to the subfolder "XYZ-Folder" than the the URL would be:

http://media.tuhh.de/rzt/XYZ-Folder/example.zip

Everybody can download files form the media server. If you want to restrict access to files on the media server, you can do it with .htaccess files, with that the computer center will not help.

.htaccess-Examples

The .htaccess files are effective for the directory and its subdirectories it lies in. If in a subdirectory lies another .htaccess file, the file overrules (or suplements) the .htaccess files for this directory and its subdirectories.

• Access from the TUHH network:

Require ip 134.28

• Access from the TUHH network including FHH:

Require ip 134.28 141.91

• It is possible to restict the networks with netmasks. There are two options:

Require ip 134.28.0.0/24
Require ip 134.28.0.0/255.255.0.0

• Access restriction with password (LDAP):

AuthBasicProvider ldap
AuthType Basic
AuthName "LDAP protected Site"
AuthLDAPURL ldaps://ldap.rz.tu-harburg.de:636/ou=People,dc=tu-harburg,dc=de?uid??(ou=RZ*)
Require valid-user

In this example all users of the computer center are allowed to access the directory. To change the filter you just have to change the (ou=RZ*) in the row with "AuthLDAPURL" to the own ou, but you can use any filter.

You can use any string with AuthName, this will be displayed when the password is required.

• Access to all:

  Require all granted

• Deny access to anyone:

  Require all denied

• It is possible to use more than one Require in a .htaccess file, this means that if any of the directives would allow access, the access will be granted (logical or).

No, even if the name are very similar, the concepts behind both service are quite different. The media server serves large files, while the mediasite is used to stream or server lectures.