Brian J. Watson
2005-04-28 18:59:21 UTC
For a long time, the OpenSSI and CI websites have been under CVS
control. The standard practice for making changes has been to edit the
appropriate files on the web server (which immediately changes what
users see on the website), then commit (checkin) the changes to CVS.
This was not necessarily the best practice, but it was convenient.
SourceForge has recently made a change preventing "developer" CVS
checkouts from being done on their web servers. Only "anonymous"
checkouts are allowed. What this means is that CVS is now strictly
read-only on the web servers, so we should no longer directly make
changes there.
Instead, each of us should checkout a local copy of the website on our
own computers under our own developer accounts. Whenever we need to make
changes, do them in this local copy then commit the changes. After that,
login to the web server using the openssi-web account (you already know
the password if you need it) and do a `cvs update' on the website to
place your latest changes online.
In the next few days, I'll figure out how to add a cron job to
automatically update the website every 15 minutes or so. Then you'll
only need to manually update it if you want to see your changes online
immediately.
Also, there are a lot of unknown and modified files on the OpenSSI
website that were never properly checked in. In the next few days, I'll
commit them to CVS through my own local checkout of the website.
Regards,
Brian
control. The standard practice for making changes has been to edit the
appropriate files on the web server (which immediately changes what
users see on the website), then commit (checkin) the changes to CVS.
This was not necessarily the best practice, but it was convenient.
SourceForge has recently made a change preventing "developer" CVS
checkouts from being done on their web servers. Only "anonymous"
checkouts are allowed. What this means is that CVS is now strictly
read-only on the web servers, so we should no longer directly make
changes there.
Instead, each of us should checkout a local copy of the website on our
own computers under our own developer accounts. Whenever we need to make
changes, do them in this local copy then commit the changes. After that,
login to the web server using the openssi-web account (you already know
the password if you need it) and do a `cvs update' on the website to
place your latest changes online.
In the next few days, I'll figure out how to add a cron job to
automatically update the website every 15 minutes or so. Then you'll
only need to manually update it if you want to see your changes online
immediately.
Also, there are a lot of unknown and modified files on the OpenSSI
website that were never properly checked in. In the next few days, I'll
commit them to CVS through my own local checkout of the website.
Regards,
Brian