Sourceforge files upload

SCP
User jsmith seeks to put file.zip to the Rel_1 directory of his project, fooproject:

scp file.zip jsmith,fooproject@frs.sourceforge.net:/home/frs/project/f/fo/fooproject/Rel_1

Rsync
User jsmith seeks to put file.zip to the Rel_1 directory of his project, fooproject:

rsync -e ssh file.zip jsmith,fooproject@frs.sourceforge.net:/home/frs/project/f/fo/fooproject/Rel_1/

SFTP
User jsmith seeks to put file.zip to the Rel_1 directory of his project, fooproject:

$ sftp jsmith,fooproject@frs.sourceforge.net
Connecting to frs.sourceforge.net…
jsmith,fooproject@frs.sourceforge.net’s password:
sftp> cd /home/frs/project/f/fo/fooproject/Rel_1
sftp> put file.zip
Uploading file.zip to /home/frs/project/f/fo/fooproject/Rel_1/file.zip
ws 100% 1573 1.5KB/s 00:00
sftp>

SSH

cd /home/frs/project/f/fo/fooproject

SourceForge Interactive Shell Service – SSH

Interactive Shell Service

Project developers can access an Interactive Shell if they have been granted shell access for the project. The Interactive Shell provides a command line interface that can be used to manage the following:

  • Project web content
  • Developer web content
  • Project uploads
  • CVS repositories

Features

The Interactive Shell supports the following features:

  • SSH shell access to project content; access to data for other users and projects not provided
  • Comprehensive set to command line tools
  • 4 hour shell life – shells are automatically terminated after 4 hours.
  • Password or SSH keys authentication
  • CVS repository administration

The Interactive Shell does not support the following features:

  • Cron service
  • File management service

Management

Project members must be granted shell access by a project administrator. Project administrators can grant Shell Access to project members on the project membership page (select Membership in the Project Admin menu).

Access

Interactive Shell sessions persist for 4 hours once created. Authorized developers that have been granted shell access for a project can create/connect to an Interactive Shell with:

ssh -t USER,PROJECT@shell.sourceforge.net create

NOTE: Be sure to substitute your SourceForge.net login username for USER, and the respective SourceForge.net project UNIX name for PROJECT.

If you do not have an active Interactive Shell session a help page can be viewed with:

ssh USER@shell.sourceforge.net

Accessing Project web content

Users who are a member of a project and want to access their Project web content need to use the above method to connect and then change to the appropriate directory (replacing with your own Project Name):

/home/project-web/<span style="color: #ff0000;">ProjectName</span>/htdocs/

Accessing Developer Web Content

Users who are a member of a project and want to access their Developer web content need to use the above method to connect and then change to the appropriate directory (replacing with your own Username):

/home/user-web/<span style="color: #ff0000;">Username</span>/htdocs/

PuTTY client

For those using the PuTTY SSH client, set the following settings for the PuTTY session:

Note: In Windows Vista or Windows 7, it may be necessary to run PuTTY in Windows XP compatibility mode.

Session Host Name: “shell.sourceforge.net
Session Connection Type: “SSH
Connection > SSH Remote command: “create
Connection > Data Auto-login username: “USER,PROJECT
  • Open the session and provide your password at the prompt.

Note: If you get disconnected after shell creation, in Connection > SSH > TTY uncheck the box for “Don’t allocate a pseudo-terminal”

SSH Key Authentication

If a user has set up SSH keys, they can be used to authenticate to an Interactive Shell session. Please see the following for more information on setting up SSH keys:

Use the ‘-i’ option to pass your private key file to the ssh command:

ssh -i PATH-TO-PRIV-KEY -t USER,PROJECT@shell.sourceforge.net create