Konstantin Khomoutov wrote:
On Fri, 29 Mar 2013 09:10:48 -0400
>
I'd like to point out this is not at all a "source forge version".
This is just a regular SF project created by someone -- see for
yourself [1]. To my knowledge, SF does not provide Fossil hosting.
SF doesn't provide it, but it's easy to do yourself.
Steps:
0. Create a SF account, SF project, and set up your ssh keys so that you
can log into their shell service.
1. connect to the SF shell service, and navigate to the project web
directory for your project:
$ ssh -t myproject,myu...@shell.sourceforge.net create
....
Welcome to sourceforge!
-bash-3.2$ cd /home/project-web/myproject
2. Obtain a fossil binary. Unfortunately the ones from the download
page on fossil-scm.org are built against a newer version of linux than
SF's servers and so will not run there, but you can build a compatible
older version yourself. (Or some kind person could put of a fossil
binary that will run on a 2.6.18 kernel). Put that fossil binary in
the project-web directory.
[get fossil somehow]
-bash-3.2$ ./fossil
Usage: ./fossil COMMAND ...
or: ./fossil help -- for a list of common commands
or: ./fossil help COMMMAND -- for help with the named command
-bash-3.2$
3. create a folder for your fossil repository that is writable by the
web server.
-bash-3.2$ mkdir repo
-bash-3.2$ ls -ld repo
drwxrwx--x 2 myuser apache 4096 Mar 29 16:45 repo
-bash-3.2$
4. put your fossil repo in that directory, or create a new repo
-bash-3.2$ ../fossil new myproject.fsl
project-id: 1e70588abb440a6ff839f6897d5397107df3a044
server-id: 1962ad62f3e973014df28323a1c9f59c8b7f6f50
admin-user: myuser (initial password is "08324d")
-bash-3.2$
5. make the repository writable by the web server
-bash-3.2$ chmod g+w myproject.fsl
-bash-3.2$
6. create the cgi frontend
-bash-3.2$ cd /home/project-web/myproject/cgi-bin
-bash-3.2$ cat > myproject.fsl
#!/usr/bin/env /home/project-web/myproject/fossil
repository: /home/project-web/myproject/repo/myproject.fsl
^D
bash-3.2$ chmod +x myproject.fsl
7. connect to your new fossil repository
http://myproject.sourceforge.net/cgi-bin/myproject.fsl
8. do normal fossil setup tasks - set project name, design, etc.
SF has a policy that you should include the sourceforge logo on your
project-web hosted pages, so go to your sourceforge project page, select
project admin > analytics, and go to the "Displaying the sourceforge.net
logo" page; pick the appropriate logo and change the fossil logo in the
"header setup" admin page from
<div class="logo">
<img src="$baseurl/logo" alt="logo">
<br><nobr>$<project_name></nobr>
</div>
to
div class="logo">
<a href="http://sourceforge.net/projects/myptoject";><img
src="http://sflogo.sourceforge.net/sflogo.php?group_id=12345678&type=16";
width="150" height="40" border="0" /></a>
<br><nobr>$<project_name></nobr>
</div>
(for whichever logo you happened to choose)
9. Set up your project web homepage to point to your fossil repo.
-bash-3.2$ cd /home/project-web/myproject/htdocs
-bash-3.2$ cat > index.php
<?php header("Location:
http://myproject.sourceforge.net/cgi-bin/myproject.fsl/home";) ?>
^D
-bash-3.2$
10. clone your fossil repository from elsewhere, make changes, etc.
$ fossil clone http://myproject.sourceforge.net/cgi-bin/myproject.fsl
myproject.fsl
....
By the way, my opinion on the matters is that ideally someone would
convince any of big players (like SF, advogato, bitbucket, berlios,
google code etc) to provide Fossil hosting as part of their existing
architecture. Otherwise, I reckon, Fossil hosting will remain a niche
activity and will still have zero visibility as it has today.
You could try upvoting this ideatorrent post:
https://sourceforge.net/apps/ideatorrent/sourceforge/ideatorrent/idea/603/
But I'm they don't use it any more, and feature requests are just done
through their forge project:
https://sourceforge.net/p/forge/feature-requests/
-J
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
