|Version 5 (modified by hinojosa, 5 years ago)|
SourceForge.net provides each project web space and services (separate from the pages on the SourceForge.net web site) that may be used to serve project-related content.
The SourceForge.net project web services permit project teams to share information among developers and end-users in ways not otherwise supported by the features of the SourceForge.net web site.
Project web space may be used for:
- Content related to the project
- Housing applications used by the project
- Testing and demos of web-based projects
SourceForge.net now offers many facilities projects used to install themselves, via the Hosted Apps offering.
The Project Web servers are configured as follows:
These details provide an overview of how the SourceForge.net project web service operates, and are useful when determining whether the project web servers meet your particular needs.
- The project web server is running an updated version of CentOS 5 distribution of Linux.
- Apache 2.2.3 web server
- PHP 5.2.6
- Perl 5.8.8
- Python 2.4.3
- Ruby 1.8.5
- Tcl 8.4.13
Bandwidth Throttling: Data (i.e. files) served from the project web servers may be throttled in order to optimize serving HTML and image content. As result, access to larger files in project web space may be orders of magnitude slower than access to smaller files. Large file content likely belongs in the File Release System.
Rate Limiting: The traffic to and from the project web servers is rate limited. Rate limits have been established to limit abuse of the project web services and to reduce the possibility of traffic spikes which could greatly increase our bandwidth costs. The rate limits are not expected to impact common, acceptable project web access.
PHP Configuration: PHP support is provided through the use of the mod_php Apache module. You can see our PHP configuration by creating a phpinfo.php file in your project web directory with the following content, and then viewing the page with your web browser:
You will note that the configuration includes some items which are non-functional, such as LDAP, IMAP and Postgres. These items are included in the build to keep with a stock configuration and to allow applications that require these functions to load for testing. However, the services themselves are not provided and outbound traffic is blocked from the project web server, so actually trying to use these functions to access outside servers would fail.
HTTP Pipelining: Keepalive (HTTP 1.1 Pipelining)]] support is not enabled in our configuration.
Include link to project DB and custom VHOST services.
Cover the fact that this is a shared hosting environment.
Cover outbound access from the web heads.
Note that there is no quota.
Basically go through http://alexandria.wiki.sourceforge.net/Project+Web%2C+Shell%2C+VHOST+and+Database+Services and harvest feature details, then take a pass to give it logical flow and keep it succinct. Link to subpages as needed.
Cover management of project web content. Link off to interactive shell. Also link to document about file management interface (may not have a doc yet).
Give sample URL for project web.
Note menu path to get to the project web site via the site.
Service-specific terms of service
Include a cleaned-up rundown on the service specific terms.
Cover regular backup of project web content using rsync vs. the file management interface. Reference rsync backups doc.
Dupe this doc, amend for developer web-specific changes wrt management, access, backups and use case.