[gst-cvs] CVS: www README.website,1.1,1.2 admin.php,1.2,1.3
Andy Wingo
wingo at users.sourceforge.net
Wed Oct 24 12:18:15 PDT 2001
Update of /cvsroot/gstreamer/www
In directory usw-pr-cvs1:/tmp/cvs-serv29576
Modified Files:
README.website admin.php
Log Message:
* documented web site layout in README.website
* there is now one password for gstreamer.net/admin.php that gets carried
down for all other admin pages
* more documentation on the web site administration scripts in the root admin page
Index: README.website
===================================================================
RCS file: /cvsroot/gstreamer/www/README.website,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- README.website 2001/10/13 19:51:04 1.1
+++ README.website 2001/10/24 19:17:27 1.2
@@ -1,22 +1,59 @@
+-*- text -*-
+
+The GStreamer web site is now in CVS. If you would like to make modifications,
+please check it out and do it on your local copy:
+
+$ cvs -z3 -d :ext:user at gstreamer.sf.net:/cvsroot/gstreamer co www
+
+[ modifications ]
+
+$ cvs -z3 commit -m 'my changes'
+$ ssh user at gstreamer.sf.net /home/groups/g/gs/gstreamer/www-update.sh
+
+This will update the web site to reflect current cvs. The site is *not*
+automatically updated, although if desired this could be done with crontabs.
+Please modify this file if you decide to auto-update the site.
+
+To administer the site, go to gstreamer.net/admin.php. The relevant passwords
+can be found in /home/groups/g/gs/gstreamer/htdocs/lib/db_setup.php. Using the
+online scripts, you can:
+ * add/remove/edit a news entry (which will update the NewsFlash if you are adding)
+ * add/remove/edit a faq item
+ * add/remove/edit the status table
+ * do some wiki administration stuff.
+
+All this from the top admin script. Slick, eh?
+
Policy for placing files in the website.
/
- This directory should be as empty as possible, since it has to have
- various pieces of junk anyway. index.shtml should be the only page
- based here.
+ various pieces of junk anyway. index.php and admin.php should be the only
+ pages based here.
+
+/apps/
+ - Applications based on GStreamer that are in the GStreamer cvs tree. Each
+ should have its own .php file (eg gstreamer.net/apps/gstmediaplay.php).
+ There should be links to all of the individual php files from the index.php
+ page, as well as a link to the applications status page and the applications
+ wiki node.
+/contact/
+ - Getting in touch with GStreamer developers. I couldn't figure out anywhere
+ better to put the mailing list page, and the directory's already made in cvs.
+
/dev/
- This contains information directed at developers, such as the policy used
to make modifications, and useful information sources.
/docs/
- - This contains general documentation for GStreamer, such as slides and
- presentations. It should also contain the latest versions of the
- documentation built from the CVS tree. (The documentation for particular
- releases being held under releases/<version>/)
+ - This contains general documentation for GStreamer. Slides and presentations
+ have been put in another directory (see below). Documentation pertaining to
+ particular releases goes in docs/$VERSION. Documentation built from CVS goes
+ in docs/cvs and is not included in the www cvs module.
-/examples/
- - This contains examples of usage of GStreamer.
+/download/
+ - Links to the sourceforge download page, links to the binary packages, etc...
/historical/
- This contains old files, of dubious utility. They are unlikely to
@@ -26,7 +63,8 @@
/images/
- Most images used by pages on the website should be placed here. Images
used by specific tools, or images which go with generated files (eg,
- documentation) are the exceptions which may be placed elsewhere.
+ documentation) are the exceptions which may be placed elsewhere. Most of
+ these images are in cvs except the directories of photos from digital cameras.
/info/
- This directory contains miscellaneous information pages. This is
@@ -34,24 +72,33 @@
if the page genuinely gives information about gstreamer, and doesn't
fit better anywhere else.
+/lib/
+ - Stuff used by all pages.
+
/lxr_icons/
- - This directory simply contains icons used by the lxr tool.
+ - This directory simply contains icons used by the lxr tool. Not in cvs.
/media/
- - This directory contains media samples, such as demo mpegs.
+ - This directory contains media samples, such as demo mpegs. This is *not* in cvs.
-/releases/
- - This directory is for information about, and documentation and
- packages of, particular releases. All files should be in
- subdirectories named with the version number of the release.
+/news/
+ - News, and GStreamer in the press.
+/releases/
+ - This directory is for information about, and documentation and packages of,
+ particular releases. All files should be in subdirectories named with the
+ version number of the release. These directories are in cvs, except for binary
+ packages. A few very old source packages are in cvs for posterity, but new
+ source tarballs should not be put in cvs. Debian packages go in releases/debian/.
+
/releases/<version>/
- - This should contain as many as possible of:
- index.shtml, which gives a brief intro to the release, and whatever
- links are relevant.
- notice.shtml, which gives the release notes.
- docs/, which contains the documentation for the release.
- download/, which contains the packages to download for the release.
+ - This should include the following:
+ * index.php, which gives a brief intro to the release, and whatever links are
+ relevant.
+ * notice.php, which gives the release notes
+
+/status/
+ - That nifty status table thing.
/wiki/
- This directory contains resource files for the wiki tool.
Index: admin.php
===================================================================
RCS file: /cvsroot/gstreamer/www/admin.php,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- admin.php 2001/10/15 04:46:30 1.2
+++ admin.php 2001/10/24 19:17:27 1.3
@@ -3,41 +3,68 @@
include ('lib/db_setup.php');
$top = get_header('GStreamer: Admin', '.');
-/*
- You can't do anything from here anyway, it's easiest if this has no password.
-
+
if(!isset($PHP_AUTH_USER)) {
- Header("WWW-Authenticate: Basic realm=\"gstreamer-admin\"");
- Header("HTTP/1.0 401 Unauthorized");
- echo $top, "<p>You must be an authorized user to access the GStreamer administration page. Sorry, holmes.</p>",
- get_footer();
- exit;
- } else {
- if (strcmp($PHP_AUTH_USER, $admin_user)!=0 ||
- strcmp($PHP_AUTH_PW, $admin_pass)!=0) {
Header("WWW-Authenticate: Basic realm=\"gstreamer-admin\"");
Header("HTTP/1.0 401 Unauthorized");
- echo $top, "<p>You must be an authorized user to access the GStreamer administration page. Sorry, holmes.</p>",
- get_footer();
+ echo $top;
+ echo <<<EOF
+<p>You must be an authorized user to access the GStreamer administration pages. Sorry.</p>
+EOF;
+ echo get_footer();
exit;
- } */
- echo $top;
-// }
-
+ } else if (strcmp($PHP_AUTH_USER, $admin_user)!=0 ||
+ strcmp($PHP_AUTH_PW, $admin_pass)!=0) {
+ Header("WWW-Authenticate: Basic realm=\"gstreamer-admin\"");
+ Header("HTTP/1.0 401 Unauthorized");
+ echo $top;
+ echo <<<EOF
+<p>
+ Bad password or user name. Check the values of <code>$admin_user</code> and
+ <code>$admin_pass<code> in <code>/home/groups/g/gs/gstreamer/htdocs/lib/db_setup.php</code>
+ to get the current user and password. This is pretty light security, you wouldn't exactly
+ have to be a l33t h4x0r to break it, so don't bother. Also, we have backups.
+</p>
+EOF;
+ echo get_footer();
+ exit;
+ }
+
$link = mysql_pconnect ($mysql_host, $mysql_user, $mysql_pass);
mysql_select_db ($mysql_database);
+ echo $top;
echo "<h1>GStreamer administration page</h1>\n";
?>
<p>
- From here, as an administrator, you have a few options, all of which require passwords.
+ From here, you have a few options.
<ul>
- <li><a href="./status/admin.php">Administer the status page</a></li>
- <li><a href="./wiki/admin.php">Administer the wiki</a></li>
- <li><a href="./news/admin.php">Administer the news page</a></li>
- <li><a href="./docs/admin.php">Administer the FAQ</a></li>
+ <li>
+ <a href="./status/admin.php">Administer the status page</a>:
+ add, edit, or remove status items.
+ </li>
+ <li>
+ <a href="./wiki/admin.php">Administer the wiki</a>:
+ lock or remove pages, make archives or snapshots... a 'dumps' directory has been
+ created that holds some backups. it has 777 permissions. The PhpWikiAdmin node has
+ most of the interesting admin funcitons.
+ </li>
+ <li>
+ <a href="./news/admin.php">Administer the news page</a>:
+ add, remove, or edit news entries. The latest entry will show us as the NewsFlash.
+ </li>
+ <li>
+ <a href="./docs/admin.php">Administer the FAQ</a>:
+ add, edit, or remove entries. Eventually I will divide the questions into categories...
+ </li>
</ul>
+</p>
+
+<p>
+ We have written up a little <a href="README.website">policy document</a> regarding the
+ layout of the www root. Your cooperation in following it is appreciated :-). Also, please
+ remember to set your umask to 002 in your .bash_profile.
</p>
<?php echo get_footer(); ?>
More information about the Gstreamer-commits
mailing list