sourceforge: IdeaTorrent

Written by xiaomao5 the 21 Dec 10 at 01:16.

Upgrade the Ruby to newest and install Ruby on Rails

Upgrade the Ruby to newest and install Ruby on Rails

Written by jwzumwalt1 the 20 Dec 10 at 20:56.

Enable the built in PHP PDO support for sqlite

Enable the built in PHP PDO support for sqlite

Written by lcawte-wikia the 23 Nov 10 at 18:19.

SVG rendering or ImageMagick needs to be installed/configured.

SVG rendering or ImageMagick needs to be installed/configured.

Written by zazi the 30 Oct 10 at 14:07.

Please enable mod_headers for Apache (http://httpd.apache.org/docs/2.0/mod/mod_headers.html) to make CORS (http://enable-cors.org/) possible.

Please enable mod_headers for Apache (http://httpd.apache.org/docs/2.0/mod/mod_headers.html) to make CORS (http://enable-cors.org/) possible.

Written by ak2ps the 19 Aug 10 at 15:01.

See title

See title

Written by lcawte-wikia the 30 Jul 10 at 22:46.

Enable a special directory with in the /home/groups folder of the project where apache or lighttp (whichever sf.net currently uses) so in that directory you have /blog and /wiki, it looks at them and calls /blog blog.myproject.sourceforge.net or /wiki wiki.myproject.sourceforge.net. Then someone could CNAME them so they can have custom subdomains, use sf.net's facilities and still have a great looking url!

Enable a special directory with in the /home/groups folder of the project where apache or lighttp (whichever sf.net currently uses) so in that directory you have /blog and /wiki, it looks at them and calls /blog blog.myproject.sourceforge.net or /wiki wiki.myproject.sourceforge.net. Then someone could CNAME them so they can have custom subdomains, use sf.net's facilities and still have a great looking url!

Written by theonlypwner the 9 Oct 11 at 03:19.

You can also define rules to rewrite the URL for subdomains.

However, this is not a permanent solution.

You can also define rules to rewrite the URL for subdomains. However, this is not a permanent solution.

Written by theonlypwner the 9 Oct 11 at 04:22.

For each VHost, also allow a directory path (default is /)

Then for each VHost, allow 20 subdomains under it, each with its own path option.

Also, allow wild-cards for subdomains.

For each VHost, also allow a directory path (default is /) Then for each VHost, allow 20 subdomains under it, each with its own path option. Also, allow wild-cards for subdomains.

Written by squalldesu the 12 Jul 10 at 11:48.

Under the project's "Project Admin" tab, there could be an option to manage its webpage. This link would take you to a file manager where you could upload files and edit text/html documents.

Under the project's "Project Admin" tab, there could be an option to manage its webpage. This link would take you to a file manager where you could upload files and edit text/html documents.

Written by astei the 22 Jul 10 at 03:27.

Other providers do it; why don't we? I agree that that this solution I have is not the solution (user must make the file locally) but will speed up the progress.

Other providers do it; why don't we? I agree that that this solution I have is not the solution (user must make the file locally) but will speed up the progress.

Written by lcawte-wikia the 25 Jun 10 at 15:00.

Implement svnroot.project.sourceforge.net for cname

Implement svnroot.project.sourceforge.net for cname

Written by freemant the 21 May 10 at 03:11.

make the apache access log available just like what you do with the error log. Or, provide official support for maven repository.

make the apache access log available just like what you do with the error log. Or, provide official support for maven repository.

Written by rfarahbod the 31 Mar 10 at 00:04.

Please configure Apache server(s) to support redirection of 'svn' and 'wiki' aliases similar to what we have for 'cvs' CNAME records.

Please configure Apache server(s) to support redirection of 'svn' and 'wiki' aliases similar to what we have for 'cvs' CNAME records.

Written by s_hoffmann the 6 Mar 10 at 18:05.

Download RoR from http://rubyonrails.org/ and install it to the server.

Download RoR from http://rubyonrails.org/ and install it to the server.

Written by nickols_k the 24 Feb 10 at 16:25.

I have idea to keep access (during year or longer) to the new project pages after renaming of project. For that is far enough to keep old project URL or provide readdress service from old URL on NEW project pages or just publish such html on old URL:



This project was renamed and may be access through:
http://new-project-name.sourceforge.net

I have idea to keep access (during year or longer) to the new project pages after renaming of project. For that is far enough to keep old project URL or provide readdress service from old URL on NEW project pages or just publish such html on old URL: <HTML> <BODY> This project was renamed and may be access through: <A HREF="http://new-project-name.sourceforge.net">http://new-project-name.sourceforge.net</A> </BODY> </HTML>

Written by assem_ch the 23 Feb 10 at 01:06.

the last stable release is 2.6.4,update to it or another 2.6.x release and make it rich of small well known libraries

releases 3.x are specials and the scripts written on 2.x don't run on it

http://www.python.org/download/releases/2.6.4/
http://www.python.org/download/releases/3.1.1/

the last stable release is 2.6.4,update to it or another 2.6.x release and make it rich of small well known libraries releases 3.x are specials and the scripts written on 2.x don't run on it http://www.python.org/download/releases/2.6.4/ http://www.python.org/download/releases/3.1.1/

Written by mtnyogi the 5 May 10 at 20:20.

If you are concerned that upgrading from Python 2.4 to Python 2.6 may break other python scripts running on your system (e.g., that are part of CentOS), may I suggest that you install Python 2.6 alongside Python 2.4 by leaving the python 2.4 installation intact (so as not to disrupt python scripts that are part of CentOS), and install python 2.6 using the "make altinstall" mechanism. This is described in the README file in the Python sources:

"If you have a previous installation of Python that you don't
want to replace yet, use

make altinstall

This installs the same set of files as "make install" except it
doesn't create the hard link to "python" named "python" and
it doesn't install the manual page at all."

The two versions will then happily coexist on the same system! Executing "python" gives your current Python 2.4 unmolested. While running "python2.6" gives you the current version of Python.

(BTW, I am not familiar with CentOS, but ubuntu has prepackaged Python 3 versions available that you can just install. These packages use the same mechanism to install python 3 alongside the default python 2.6. Perhaps CentOS already has a python 2.6 package like this?)

If you are concerned that upgrading from Python 2.4 to Python 2.6 may break other python scripts running on your system (e.g., that are part of CentOS), may I suggest that you install Python 2.6 alongside Python 2.4 by leaving the python 2.4 installation intact (so as not to disrupt python scripts that are part of CentOS), and install python 2.6 using the "make altinstall" mechanism. This is described in the README file in the Python sources: "If you have a previous installation of Python that you don't want to replace yet, use make altinstall This installs the same set of files as "make install" except it doesn't create the hard link to "python<version>" named "python" and it doesn't install the manual page at all." The two versions will then happily coexist on the same system! Executing "python" gives your current Python 2.4 unmolested. While running "python2.6" gives you the current version of Python. (BTW, I am not familiar with CentOS, but ubuntu has prepackaged Python 3 versions available that you can just install. These packages use the same mechanism to install python 3 alongside the default python 2.6. Perhaps CentOS already has a python 2.6 package like this?)

Written by nicka101 the 2 Dec 09 at 19:21.

I believe that the best solution would be to add asp functionality to project web space and allow developers almost free reign over their space and their project space.

I believe that the best solution would be to add asp functionality to project web space and allow developers almost free reign over their space and their project space.

Written by eslusorenko the 16 Feb 11 at 14:42.

Download and Install Mono and Mod_mono

Download and Install Mono and Mod_mono

Written by rzorzorzo the 22 Nov 09 at 09:18.

enabling webdav for write access for the project owner may also be a further alternative to the existing access per sftp

enabling webdav for write access for the project owner may also be a further alternative to the existing access per sftp

Written by slicer the 9 Nov 09 at 15:16.

sf.net already uses OpenID authentication for users. Start offering OpenID provider services, and allow this to be used both from project web pages and the rest of the net.
Doing so would allow any project associated with sourceforge to securely authenticate users to their matching sf.net username, no matter where their webpages are hosted.

sf.net already uses OpenID authentication for users. Start offering OpenID provider services, and allow this to be used both from project web pages and the rest of the net. Doing so would allow any project associated with sourceforge to securely authenticate users to their matching sf.net username, no matter where their webpages are hosted.

Written by slicer the 9 Nov 09 at 15:24.

Just like the hosted applications, set up https for the project webpages hosted on *.sourceforge.net (using a wildcard cert) and authenticate against the sf.net user database. This will give project pages hosted on sf.net access to the username.
To avoid user confusion, set up the 401 authentication error page to show a short error message and redirect to the non-https equivalent. It probably also makes sense to reject spiders to the https pages, to avoid these ending up in search engines.

Just like the hosted applications, set up https for the project webpages hosted on *.sourceforge.net (using a wildcard cert) and authenticate against the sf.net user database. This will give project pages hosted on sf.net access to the username. To avoid user confusion, set up the 401 authentication error page to show a short error message and redirect to the non-https equivalent. It probably also makes sense to reject spiders to the https pages, to avoid these ending up in search engines.

Written by dergraaf the 29 Oct 09 at 23:19.

I am working with doxygen 1.5.8 here which has none of the described problems.

I am working with doxygen 1.5.8 here which has none of the described problems.

Written by ewl the 26 Oct 09 at 07:58.

Pretty easy: install the bzr command like all other version controlling systems.

Pretty easy: install the bzr command like all other version controlling systems.

Written by necoro the 18 Sep 09 at 17:24.

There is a module for Apache named mod_wsgi ( http://code.google.com/p/modwsgi/ ), which works similar to mod_php for PHP. Adding this to the apache installation should deal with the problems given.

There is a module for Apache named mod_wsgi ( http://code.google.com/p/modwsgi/ ), which works similar to mod_php for PHP. Adding this to the apache installation should deal with the problems given.

Written by aristedes the 7 Sep 09 at 02:34.

There is a workaround: http://weacemethod.sourceforge.net/wiki/index.php/HowToInstallRubyGemsSF.NET

But that is somewhat awkward. A better approach provided by SF would be much nicer.

There is a workaround: http://weacemethod.sourceforge.net/wiki/index.php/HowToInstallRubyGemsSF.NET But that is somewhat awkward. A better approach provided by SF would be much nicer.