OGSA-DAI Source Forge Infrastructure
Outline
These are notes on the setting up and use of the Source Forge infrastructure being used by the OGSA-DAI project.
Main Source Forge page
Currently antonioletti, rmbaxter, allyhume and mikej888 are project admins.
piwiki (web analysis)
Tells us who is accessing the Source Forge account - a bit like google analytics if you are familiar with that.
Project Web
Provided with a web page:
To access one can sftp, scp, rsync content:
sftp USER,PROJECT@web.sourceforge.net password: sftp> cd htdocs sftp> put *.html sftp> quit
NOTE: if you do upload material please ensure that the group has write permissions after you have uploaded the files otherwise no one else will be able to update these if required. After you have uploaded a set of files login using the shell command as below and:
cd /home/groups/o/og/ogsa-dai/htdocs/... chmod -R 775 NameOfYourDirectory
This will give files execute permissions but if you don't do this there is a danger that directories will no longer be accessible as they will not be executable.
One is required to have a source forge logo (see service restrictions). Also, there is a form of the logo that also counts the number of hits we get on the page. More on the transfer protocols: sftp, rsync and scp.
Error logs are available from:
/home/persistent/e/er/error_logs
For debugging purposes. Access logs are not available for privacy reasons.
Shell access
Can have shell access to your user account and the ogsa-dai project account by doing:
ssh -t USER,ogsa-dai@shell.sourceforge.net create
Will persist for 4 hours. This will drop you in the user file space. The user file space currently has the following structure:
home:
uploads:
userweb:
cgi-bin:
htdocs:
persistent:
Project space (for OGSA-DAI) lives in:
/home/groups/o/og/ogsa-dai/
This has the structure:
cgi-bin
htdocs
persistent
The htdocs directory has read-only versions of the web pages uploaded (see below). See the following for information on the persistent directory.
For more information on using the shell service see:
TRAC
WordPress (blog)
The content from the old blog has been migrated to:
and the old blog has been deprecated. Note that if you use https scheme then trying to access the page will ask for credentials.
Services
Releases
Instructions on releasing files through source forge.
http://apps.sourceforge.net/trac/sourceforge/wiki/Release%20files%20for%20download
Not entirely clear so have created my own creating a release notes.
Trackers
Aim to use the TRAC ticketing system instead of this.
Forums
Mailing Lists
The following email lists have been created:
- ogsa-dai-announce@… - Public list for project announcements
- ogsa-dai-committers@… - Private list for internal project communications
- ogsa-dai-users@… - Public list for users and developers of OGSA-DAI
- ogsa-dai-svn-commits@… - Public list to which SVN commit messages will eventually go to
Nobody should post to the ogsa-dai-svn-commits list other than through the SVN - can't find a way of enforcing this.
With the respective administrative interfaces:
- https://lists.sourceforge.net/lists/admin/ogsa-dai-users/
- https://lists.sourceforge.net/lists/admin/ogsa-dai-announce/
- https://lists.sourceforge.net/lists/admin/ogsa-dai-committers/
- https://lists.sourceforge.net/lists/listinfo/ogsa-dai-svn-commits
Mario/Mike/Rob have the administrative passwords for these lists.
Subversion (SVN)
Using hook scripts to send commit messages to the gsa-dai-svn-commits@… mailing list for interested parties. This is also archived.
It is also important to read the documentation on the layout of the OGSA-DAI SVN structure.
Backups
Can back-up hosted applications via this forms interface:
In general though each component used has its own backup method.
| Component | Backup Method |
| SVN | rsync |
| Trac | hosted back-up app |
| Wordpress | hosted back-up app |
| Mailing lists | mbox files |
