Project Web and Developer Web Server Configuration Details

SourceForge.net provides project web and developer web services based on a common platform. Here are the technical details of that platform, provided to help you deploy pages and applications under these services.

SourceForge.net uses a shared environment for the project and developer web services. You should assume that all files uploaded to our servers may be viewed by other users.

Bandwidth Throttling

Data (i.e. files) served from the web servers may be throttled to optimize serving HTML and image content. As a result, access to larger files in web space may be much slower than access to smaller files. Large file content belongs in the File Release System.

File management

Files for project web and developer web may be managed using the file management service or interactive shell service.

Quotas

Service usage is not restricted by hard disk quotas, but we may contact you for cleanup if sizes are too large.

File releases should be placed in the File Release System (FRS) rather than being placed in webspace.

Web space permissions

If you make a file/directory group writable, it is writable by your project's web applications (but not by other projects' apps). You should set as few files/directories as possible to be group-writable, as that helps to protect against security exploits of your project's web apps being able to modify your web files.

You should remove the world-readable bit from a file that contains secrets, such as DB passwords. As long as the file is group-readable, it can be used by your web apps.

You don't need to worry about file ownership between your project's users, because we use a special filesystem that grants all authorized project members the same rights to change your project files. So, feel free to chmod, edit, etc., regardless of the file's owner. See [Project Web Filesystem Permissions] for full details.

Index pages

The index page for a website loads on default into a browser when no specific filename is specified (i.e. https://foo.sourceforge.io and https://foo.sourceforge.io/index.html are the same page, the index.html file loads by default).

If no index page is found, we will redirect the user to the project's SourceForge page.

Related Services

• Project Web Services
• Developer Web Services
• Custom VHOST services allow projects to have our web servers answer traffic for domain names they register.