[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] [574] proofread
|
From: |
ineiev |
|
Subject: |
[Savannah-cvs] [574] proofread |
|
Date: |
Thu, 9 Feb 2023 07:16:40 -0500 (EST) |
Revision: 574
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=574
Author: ineiev
Date: 2023-02-09 07:16:39 -0500 (Thu, 09 Feb 2023)
Log Message:
-----------
proofread
Modified Paths:
--------------
trunk/sviki/BackEndSetup.mdwn
trunk/sviki/FrontEndDebuggingTips.mdwn
trunk/sviki/FrontEndNotificationEmails.mdwn
trunk/sviki/FrontEndSetup.mdwn
trunk/sviki/Nagios.mdwn
trunk/sviki/RunningSavaneLocally.mdwn
trunk/sviki/SqlQueries.mdwn
trunk/sviki/StatusMonitor.mdwn
Modified: trunk/sviki/BackEndSetup.mdwn
===================================================================
--- trunk/sviki/BackEndSetup.mdwn 2023-02-09 11:20:06 UTC (rev 573)
+++ trunk/sviki/BackEndSetup.mdwn 2023-02-09 12:16:39 UTC (rev 574)
@@ -1,17 +1,17 @@
Savannah BackEnd Setup
======================
-This page describes the configuration needed for savannah's
-new backend server and perl/python code (e.g. the scripts
+This page describes the configuration needed for Savannah
+new backend server and Perl code (e.g. the scripts
that run on `vcs0` which create new repositories for the projects
based on database updates from the frontend).
-Further reading about savannah's server:
+Further reading about Savannah server:
* [[SavannahArchitecture]] - overview of the current ('old') setup
(i.e. vcs, mgt, frontend, internal, vcs, download).
-* [[SavannahServices]] - services/daemons available on savannah's hosts.
-* [[SavannahInternals]] - Savannah's inner-workings.
+* [[SavannahServices]] - services/daemons available on Savannah hosts.
+* [[SavannahInternals]] - Savannah inner-workings.
* [[SavannahHosts]] - Configuration of the new servers
(i.e. mgt0, vcs0, frontend0, internal0, download0).
@@ -19,23 +19,23 @@
General information
-------------------
-Long ago, savannah's used a single server. This lead to
-the frontend code (php) and backend scripts (perl/python)
+Long ago, Savannah used a single server. This lead to
+the frontend code (PHP) and backend scripts (Perl)
to reside in the same repository, and rely on similar
configuration files.
Despite using the same repository, the frontend
-code does not use the Perl/python backend scripts, and the backend
-side (e.g. `vcs0`) does not use the frontend's php code.
+code does not use the Perl backend scripts, and the backend
+side (e.g. `vcs0`) does not use the frontend PHP code.
See [[FrontEndSetup]] for complimentary details about the frontend.
`vcs0` needs to run `sv_groups` to create new repositories for new projects
(or existing projects which enabled new repositories using the "Select
Features"
-menu option on the savannah web site).
+menu option on the Savannah web site).
`download0` needs to run `sv_groups` to create the 'download/releases'
directory
for projects.
`internal0` needs to run `sv_mailman`, `sv_reminder`,`sv_cleaner` as cronjobs.
-See [[SavannahInternals]] For more details about the scripts and cronjobs
+See [[SavannahInternals]] for more details about the scripts and cronjobs
(although they describe the setup on the current/old VMs, we aim to replicate
a similar setup on the new VMs).
@@ -49,7 +49,7 @@
cpan -i Mail::Send
As root, create the required directories.
-`/etc/savane` is temporarily created with write-access
+`/etc/savane` is temporarily created with write access
(for the 'make install' step as non-root user), and will be made
read-only after the installation is complete.
@@ -57,11 +57,10 @@
chgrp staff /opt/savannah /etc/savane
chmod g+ws /opt/savannah /etc/savane
-As non-root (e.g. agn), clone the savage repository.
-The `nextgen` branch holds the latest updates for the code on the new machines:
+As non-root (e.g. agn), clone the savane repository.
cd /opt/savannah
- git clone -b nextgen git://git.savannah.gnu.org/administration/savane.git
+ git clone https://git.savannah.gnu.org/administration/savane.git
cd savane/
./bootstrap
./configure --prefix=/opt/savannah/ --sysconfdir=/etc
@@ -77,7 +76,7 @@
drwxrwsr-x 3 agn staff 4096 Oct 19 21:09 savane
drwxrwsr-x 3 agn staff 4096 Oct 19 21:09 share
-Savannah's common backend scripts:
+Savannah common backend scripts:
$ ls /opt/savannah/bin
[...]
@@ -86,7 +85,7 @@
sv_homedirs
[...]
-Savannah's perl modules:
+Savannah Perl modules:
$ cd /opt/savannah/
$ find ./lib/ -type f
@@ -106,10 +105,10 @@
share/perl/5.18.2/Savane/Git.pm
[...]
-UGLY HACK: Symlink the `Savane` perl module to the server's sitelib.
-This alleviate the need to set custom PERL5LIB, while keep all of savannah's
+UGLY HACK: Symlink the `Savane` Perl module to the server sitelib.
+This alleviate the need to set custom PERL5LIB, while keep all of Savannah
custom code under `/opt/savannah`. Improving this is a desired TODO item
-(by either doing away with `Savane.pm` or changing the perl script
+(by either doing away with `Savane.pm` or changing the Perl script
to self-locate the required modules. See [[SavannahHackingIdeas]]).
ln -sf /opt/savannah/share/perl/5.18.2/Savane /usr/local/share/perl/5.18.2
@@ -117,7 +116,7 @@
Manually prepare configuration files (passwords copied from frontend0).
-The `.pl` file is used by perl scripts (e.g. `sv_groups`).
+The `.pl` file is used by Perl scripts (e.g. `sv_groups`).
The `.ini` file is used by python scripts (e.g. `sv_tmpgpg`).
NOTE: On `internal0`, set the HOST to `localhost` instead of `208.118.235.78`.
@@ -144,9 +143,9 @@
On `vcs0`,`download0`,`internal0` -
-lock permissions on the configuration/passwords files.
+lock permissions on the configuration files.
-NOTE: *DO NOT* run these commands on frontend0. Frontend0's
+NOTE: *DO NOT* run these commands on frontend0. Frontend0
files require special permissions to ensure apache can access
these files. See [[FrontEndSetup]] for detail.
@@ -154,10 +153,6 @@
chown root:staff savane.*
chmod 0640 savane.*
- # remove 'content' - it's only used by the frontend's php
- # DO NOT REMOVE IT ON frontend0...
- rm -r content
-
# ls -l /etc/savane/
total 16
-rw-r----- 1 root staff 8563 Oct 19 21:29 savane.conf.pl
@@ -169,11 +164,11 @@
-Test the scripts, ensuring the perl modules and DB are working:
+Test the scripts, ensuring the Perl modules and DB are working:
### This is equivalent to what OpenSSH is using to find the
### users' keys when they log with SSH to @vcs.sv.gnu.org .
- ### The users' keys are stored in savane's database.
+ ### The users' keys are stored in savane database.
$ cd /opt/savannah/bin
$ export PERL5LIB=/opt/savannah/share/perl/5.18.2
Modified: trunk/sviki/FrontEndDebuggingTips.mdwn
===================================================================
--- trunk/sviki/FrontEndDebuggingTips.mdwn 2023-02-09 11:20:06 UTC (rev
573)
+++ trunk/sviki/FrontEndDebuggingTips.mdwn 2023-02-09 12:16:39 UTC (rev
574)
@@ -1,9 +1,9 @@
-FrontEnd Debugging Tips
+Frontend Debugging Tips
=======================
-This page details tips about debugging savannah's frontend (PHP code and such).
+This page details tips about debugging Savannah frontend (PHP code and such).
-It is *highly* recommended to debug/develop new features on a
+It is *highly* recommended to debug new features on a
dedicated [[FrontEndDevelopmentSite]] or when [[RunningSavaneLocally]].
Avoid meddling with the real public website as much as possible.
@@ -11,7 +11,7 @@
PHP debugging
-------------
-### Showing PHP messages + SQL statements on the web-browser
+### Showing PHP messages + SQL statements in the web browser
In the `savane.conf.php` file, set (or uncomment) `$sys_debug_on=true`.
@@ -25,10 +25,10 @@
To print a variable, call `util_debug(print_r($VAR,TRUE));`.
-### Print messages to apache's log
+### Print messages to Apache log
-In the php code, call `error_log("hello world");` to send the message
-to apache's log (note: it will be the error log or php log, depending
+In the PHP code, call `error_log("hello world");` to send the message
+to Apache log (note: it will be the error log or PHP log, depending
on your configuration. See details below).
To print a variable, call `error_log(print_r($VAR,TRUE));`.
@@ -37,13 +37,13 @@
Dedicated Development Site
--------------------------
-For websites setup according to [[FrontEndDevelopmentSite]],
+For website setup according to [[FrontEndDevelopmentSite]],
the relevant locations are:
* access log: `/home/[USER]/savannah/var/[USER].access.log`.
* error log (STDERR): `/home/[USER]/savannah/var/[USER].error.log`.
* PHP error messages: `/home/[USER]/savannah/var/[USER].php-error.log`.
-* project registration submissions:
+* group registration submissions:
`/home/[USER]/savannah/var/www/submissions_uploads`.
* tracker file attachments:
`/home/[USER]/savannah/var/lib/savane/trackers_attachments`.
@@ -51,7 +51,6 @@
See [[FrontEndNotificationEmails]] for information about
setting up email notifications during development.
-
* cron jobs: (FIXME)
@@ -65,23 +64,22 @@
* access log:
* error log (STDERR):
* PHP error messages:
-* project registration submissions:
+* group registration submissions:
* tracker file attachments:
* mail logs: (not sent? depending on local PHP settings?)
* cron jobs: (no cron jobs)
-
Public website
--------------
-The following files/directories are used by the public
+The following files and directories are used by the public
website (which serves <https://savannah.gnu.org>).
* access log: `/var/log/apache2/access.log`.
* error log (STDERR): `/var/log/apache2/error.log` (FIXME: verify).
* PHP error messages: same as error log (no separate PHP log for public
website).
-* project registration submissions: `/var/www/submissions_uploads`.
+* group registration submissions: `/var/www/submissions_uploads`.
* tracker file attachments: `/var/lib/savane/trackers_attachments`.
* mail logs: `/var/log/mail.log` (see [[MailSystem]]).
* cron jobs: (FIXME)
Modified: trunk/sviki/FrontEndNotificationEmails.mdwn
===================================================================
--- trunk/sviki/FrontEndNotificationEmails.mdwn 2023-02-09 11:20:06 UTC (rev
573)
+++ trunk/sviki/FrontEndNotificationEmails.mdwn 2023-02-09 12:16:39 UTC (rev
574)
@@ -1,4 +1,4 @@
-Emails notifications from Savannah FrontEnd
+Email notifications from Savannah Frontend
===========================================
@@ -21,7 +21,7 @@
If the variable `$sys_debug_email_override_address` is set,
-all emails will be sent to its content (assumed to be a valid email address)
+all emails will be sent to its value (assumed to be a valid email address)
regardless of the original recipients for the notification email.
It is recommended to set it to `savannah-hackers-tests@gnu.org` to avoid
spamming the public mailing lists. When using this email address,
@@ -37,30 +37,27 @@
In both cases (variable set or unset), emails sent from the
development site originate from
`www-data@jsmith.frontend0.savnnah.org`. The first time emails are
-sent they will be held in moderation until reviewd by a human (all of
-savannah's mailing lists are moderated as an anti-spam measure).
+sent they will be held in moderation until reviewed by a human (all of
+Savannah mailing lists are moderated as an anti-spam measure).
It is recommended to send a test email early (e.g. when the
development site is first activated), and allow 24 hours for a human
moderator to approval this email address. This will save frustrations
later on if trying to troubleshoot email issues or adjust email
-message content.
+message text.
-
-
Email addresses in the database
-------------------------------
The PHP website sends notification emails for two types of events:
-1. Project registrations
-2. Project tracker submissions (new
+1. Group registrations
+2. Group tracker submissions (new
bugs/support/tasks/patches/cookbook/news items).
+For new group registrations:
-For new project registrations:
-
mysql> select type_id, name, admin_email_adress from group_type ;
+---------+------------------------------------+----------------------------------+
| type_id | name | admin_email_adress
|
@@ -74,7 +71,7 @@
5 rows in set (0.00 sec)
-For tracker submission in each project:
+For tracker submission in each group:
mysql> select group_id, unix_group_name,
new_bugs_address, new_patch_address,
@@ -111,10 +108,7 @@
new_cookbook_address:
-
-
-
-PHP Code
+PHP code
--------
@@ -122,26 +116,26 @@
The function `sendmail_mail` in
`<savane>/frontend/php/include/sendmail.php` behaves similarly to
-PHP's `mail` and is used to send email from all savane's php files.
+PHP `mail` and is used to send email from all savane PHP files.
It performs the following additional tasks:
-1. user and 'squad' expansion (e.g. if the recipient is `agn`, find the email
- associated with savannah user `agn`).
-2. processes exclude lists (defined in the configuration section
- for each project's tracker).
-3. adds additional SMTP headers (e.g. `X-Apparently-From:`
- with the logged-in user name and IP, `X-Savane-Server`,
+1. User and 'squad' expansion (e.g. if the recipient is `agn`, find the email
+ associated with Savannah user `agn`).
+2. Processes exclude lists (defined in the configuration section
+ for each group tracker).
+3. Adds additional SMTP headers (e.g. `X-Apparently-From:`
+ with the logged-in user name, `X-Savane-Server`,
`X-Savane-Project`, etc.).
-4. If the user has configuration a specific SUBJECT line,
- construct a customized message with the specific subject line
- and send it to this user.
- (on the website, click "My Account Conf"->"Edit Personal Notification
Settings"
+4. If the user has configured a specific SUBJECT line,
+ construct a customized message with it and send it to this user.
+ (on the website, visit
+ "My Account Conf"->"Edit Personal Notification Settings",
then see "Subject line" to set a custom one)
5. If the global variable `$sys_debug_email_override_address` is set,
emails will be sent to the address specified in it,
regardless of the original recipients. This can be used
- during development, to ensure emails do not spam
+ during development to ensure emails do not spam
public mailing lists or unsuspecting users.
FIXME: There's a variable called `$int_delayspamcheck` which affects
@@ -149,29 +143,27 @@
DB table `trackers_spamcheck_queue_notification` instead of being sent.
+### New group registration
-
-### new project registration
-
FIXME: What's going on??
-The file `<savane>/frontend/php/include/Group.class` contains:
+The file `<savane>/frontend/php/include/group.php` contains:
function getTypeAdminEmailAddress()
{ return $this->type_data_array['admin_email_adress']; }
-which returns the relevant 'new project' email address for each project type
-(the project type is selected by the submitter in the html form).
+which returns the relevant 'new group' email address for each group type
+(the group type is selected by the submitter in the html form).
the file `<savane>/frontend/php/register2/index.php` uses this function
-to send an email notification about new project registration
+to send an email notification about new group registration
(note: the `/register/` URL is aliased to the `/regster2/` directory in the
apache configuration)
$type_admin_email_address = $project->getTypeAdminEmailAddress();
But later on this variable is only used as the 'FROM:' field to
-send a message directly to the user who submitted the new project.
+send a message directly to the user who submitted the new group.
The comment in the code says:
@@ -178,8 +170,8 @@
# a mail for the moderators staff!
# Done automatically by the task tracker
-And new projects are treated as new tasks (i.e. stored in the
-tasks tracker) - but Savannah's administration project has
+And new groups are treated as new tasks (i.e. stored in the
+tasks tracker) - but Savannah administration group has
an empty value for the `news_tasks_address` - so how do emails
end up in `savannah-register-public@gnu.org`?
@@ -188,7 +180,7 @@
FIXME: these functions are not used anywhere ...
-The file `<savane>/frontend/php/include/Group.class` contains:
+The file `<savane>/frontend/php/include/group.php` contains:
function getNewBugAddress() {
return $this->data_array['new_bug_address'];
Modified: trunk/sviki/FrontEndSetup.mdwn
===================================================================
--- trunk/sviki/FrontEndSetup.mdwn 2023-02-09 11:20:06 UTC (rev 573)
+++ trunk/sviki/FrontEndSetup.mdwn 2023-02-09 12:16:39 UTC (rev 574)
@@ -1,35 +1,35 @@
Savannah Frontend Setup
=======================
-This page describes the configuration needed for savannah's
+This page describes the configuration needed for Savannah
new frontend web server and PHP code.
-In 2016, the FSF allocated new hardware for savannah's servers,
+In 2016, the FSF allocated new hardware for Savannah servers,
kicking off the server migration efforts. The existing server
(which hosts <http://savannah.gnu.org>) is called `frontend`
(`frontend.savannah.gnu.org`). The new server is currently
called `frontend0` (<https://frontend0.savannah.gnu.org>).
-Further reading about savannah's server:
+Further reading about Savannah server:
* [[SavannahArchitecture]] - overview of the current ('old') setup
(i.e. vcs0, mgt0, frontend0, internal0, download0).
-* [[SavannahServices]] - services/daemons available on savannah's hosts.
-* [[SavannahInternals]] - Savannah's inner-workings.
+* [[SavannahServices]] - services/daemons available on Savannah hosts.
+* [[SavannahInternals]] - Savannah inner-workings.
* [[SavannahHosts]] - Configuration of the new servers
(i.e. mgt0, vcs0, frontend0, internal0, download0).
-Further reading about savannah's web frontend:
+Further reading about Savannah web frontend:
-* [[RunningSavaneLocally]] - Running savannah's php code locally.
+* [[RunningSavaneLocally]] - Running Savannah PHP code locally.
* [[FrontEnd]] - Notes about the current frontend setup (git,cvs).
-* [[FrontEndDevelopmentSite]] - Setting up development sites for savannah.
+* [[FrontEndDevelopmentSite]] - Setting up development sites for Savannah.
General information
-------------------
-Savannah's web frontend (i.e. <https://savannah.gnu.org>)) is written in PHP.
+Savannah web frontend (i.e. <https://savannah.gnu.org>)) is written in PHP.
It uses a MySQL database running on `internal0`.
The code repository is called 'savane', available at
@@ -38,9 +38,9 @@
write-access: `git clone
<USER>@git.sv.gnu.org:/srv/git/administration/savane.git`).
-At the time of this writing (September 2016), 'savane' and
-Savannah not 'installed' in a standard way (e.g. 'make install').
-Instead, files and settings are copied from old servers (e.g. the old
+As of September 2016, 'savane' is not 'installed' in a standard way
+(e.g. 'make install'). Instead, files and settings are copied
+from old servers (e.g. the old
VM of 'frontend.sv.gnu.org' to the new VM 'frontend0'). The MySQL
database is not created from scratch, but is copied from existing
servers (e.g. DB on internal to internal0). The configuration files
@@ -48,7 +48,7 @@
are copied from existing servers, and tweaked until they 'just work'.
The PHP code runs directly from the cloned repository (i.e. if cloned
-into `$HOME/projects/savane`, Apache's php configuration should point to
+into `$HOME/projects/savane`, Apache PHP configuration should point to
`$HOME/projects/savane/frontend/php/`). The 'installation' above does
not touch the PHP part.
@@ -61,12 +61,11 @@
The configuration is in `frontend0:/etc/savane`.
-
Apache/PHP Configuration File Location
--------------------------------------
The environment variable `SAVANE_CONF` determines the location of the main
-PHP configuration file for savane. It could be set in Apache's configurations
+PHP configuration file for savane. It could be set in Apache configurations
file (`frontend0:/etc/apache2/sites-available/sv.inc`) or in an `.htaccess`
file (`/usr/src/savane/frontend/php/.htaccess`) with
`SetEnv SAVANE_CONF /etc/savane`
@@ -78,7 +77,7 @@
is referenced here:
`sites-available/sv.nongnu.inc:SetEnv SV_LOCAL_INC_PREFIX
/etc/savane/nongnu-conf`.
-** On current production savannah, none of these are defined for the gnu side
**
+** On current production Savannah, none of these are defined for the GNU side
**
The code in `init.php` falls back to:
@@ -87,24 +86,19 @@
include('/etc/savane/.savane.conf.php');
-Content files
--------------
+"Site-specific" files
+---------------------
-Several sections of the displayed HTML content
-on the savannah website are set by external content files.
+Several sections of the displayed HTML
+on the Savannah website are taken from files in frontend/site-specific/.
-See here for further details:
-<http://lists.gnu.org/archive/html/savannah-hackers-public/2016-09/msg00009.html>
+Savannah licenses list is also stored in one of those files.
-Savannah's licenses list are also stored in a content file,
-See this thread for more details:
-<http://lists.gnu.org/archive/html/savannah-hackers-public/2016-09/msg00001.html>
-
Mail messages
-------------
-Savannah's PHP code runs under apache as `www-data` user.
+Savannah PHP code runs under apache as `www-data` user.
Mail messages sent to `www-data` (cron and email errors)
are now aliased to `root`
(<http://lists.gnu.org/archive/html/savannah-hackers-public/2016-05/msg00058.html>).
Modified: trunk/sviki/Nagios.mdwn
===================================================================
--- trunk/sviki/Nagios.mdwn 2023-02-09 11:20:06 UTC (rev 573)
+++ trunk/sviki/Nagios.mdwn 2023-02-09 12:16:39 UTC (rev 574)
@@ -1,3 +1,5 @@
+# Nagios at Savannah
+
Overview
--------
@@ -21,9 +23,9 @@
Alerting
--------
-Nagios will send email alerts to users configured in
-\$NAG\_CONF/contacts.cfg. As well as individual users, the
-savannah-reports-private mailing list is configured as a contact.
+Nagios will send email alerts to users configured
+in \$NAG\_CONF/contacts.cfg. As well as individual users,
+the savannah-reports-private mailing list is configured as a contact.
Configuration
-------------
@@ -37,10 +39,10 @@
---------------------------
Any back-end checks that are global across all systems should have their
-checks in the host group. \_Services\_ that Savannah provides (Various
-VCS systems, WWW including static content and dynamic, DNS etc...)
-should be configured as a service and use the "virtual" host name of the
-system (EG: git.savannah.gnu.org is a CNAME for vcs.savannah.gnu.org)
+checks in the host group. \_Services\_ that Savannah provides (various
+VCS systems, WWW, DNS etc...) should be configured as a service and use
+the "virtual" host name of the system (e.g. git.savannah.gnu.org is
+a CNAME for vcs.savannah.gnu.org)
Adding a new host
-----------------
@@ -59,12 +61,12 @@
: /etc/init.d/nagios3 reload \# It will do a configtest and abort the
reload on failure
-Your new host should appear in Nagios under the host groups
+Your new host should appear in Nagios under the host groups.
-Adding a new Plugin
+Adding a new plugin
-------------------
-Plugins for Nagios are simply scripts/binaries that follow specific exit
+Plugins for Nagios are simply scripts and binaries that follow specific exit
codes and messages to stdout.
Custom plugins are located in /opt/administration/nagios/plugins. When
@@ -80,14 +82,14 @@
- RED - The script should exit with a code of 2 and print "CRITICAL -
extra text..." to stdout
-Once a new plugin has been created, it will need to be added as a
-command in Nagios. Custom commands should be added to
+Once a new plugin has been created, it will need to be added
+as a command in Nagios. Custom commands should be added to
\$NAG\_CONF/custom\_commands.cfg.
Once the new command has been created, a service can then be added that
uses this check\_command.
-Adding a new Service
+Adding a new service
--------------------
Services map a check command to a host/service group. Add services to
Modified: trunk/sviki/RunningSavaneLocally.mdwn
===================================================================
--- trunk/sviki/RunningSavaneLocally.mdwn 2023-02-09 11:20:06 UTC (rev
573)
+++ trunk/sviki/RunningSavaneLocally.mdwn 2023-02-09 12:16:39 UTC (rev
574)
@@ -1,7 +1,7 @@
-# Running Savane Locally - howto
+# Running Savane Locally
"Savane" is the code name for the server software that runs
-[GNU Savannah](http://savannah.gnu.org), among other things.
+[GNU Savannah](//savannah.gnu.org), among other things.
* Project page: <http://savannah.gnu.org/projects/administration>
@@ -111,8 +111,8 @@
$sys_dbuser="USERNAME";
$sys_dbpasswd="PASSWORD";
-Reloading the savannah web page on your local web browser should
-now 'just work' and display the savannah website (with dummy values).
+Reloading the Savannah web page on your local web browser should
+now 'just work' and display the Savannah website (with dummy values).
There is an admin user 'agn' in the demo database, with password '12345'.
@@ -121,7 +121,7 @@
As of 2023, Savannah requires **PHP version 5.4, 5.5, 5.6, 7.0, 7.2, 7.4, 8.0
8.1**. Newer versions aren't tested.
-## Other environments/distributions
+## Other environments
As long as you have PHP with MySQL, savane should mostly
work. If you don't have `autoconf/automake/gettext/perl/etc`, you can
@@ -185,7 +185,7 @@
</Location>
- # Uploads for new project registrations and bug-report attachments.
+ # Uploads for new group registrations and bug-report attachments.
# This directory must be writable by 'www-data' user.
# NOTE: Ensure this directory matches the '$sys_upload_dir' value
# in the custom savanne configuration file
@@ -246,4 +246,4 @@
* [[FrontEndDebuggingTips]] for log files and PHP debugging tips.
* [[FrontEndSetup]] - how the same PHP code is configured on
- savannah's servers.
+ Savannah servers.
Modified: trunk/sviki/SqlQueries.mdwn
===================================================================
--- trunk/sviki/SqlQueries.mdwn 2023-02-09 11:20:06 UTC (rev 573)
+++ trunk/sviki/SqlQueries.mdwn 2023-02-09 12:16:39 UTC (rev 574)
@@ -1,7 +1,6 @@
-SQL queries and info
---------------------
+# SQL queries and info
-Here are some queries to get a grip on the mysql databases for savannah:
+Here are some queries to get a grip on the MySQL databases for Savannah:
mysql savane # on the internal subhost
show databases; # show all databases in the installation
@@ -22,10 +21,10 @@
the third removes all posts in all trackers, plus forum posts.
This was all to deal with the overwhelming accumulated spam in news
-posts comments, sept 2011.
+posts comments, Sept 2011.
-Old stats
---------
+## Old stats
+
Some (old) stats, as of 20051217.
As you can see, we have actually few CVS users; most of our traffic is
Modified: trunk/sviki/StatusMonitor.mdwn
===================================================================
--- trunk/sviki/StatusMonitor.mdwn 2023-02-09 11:20:06 UTC (rev 573)
+++ trunk/sviki/StatusMonitor.mdwn 2023-02-09 12:16:39 UTC (rev 574)
@@ -1,7 +1,6 @@
-Savannah Health-check/status monitor
-====================================
+# Savannah health monitor
-If we ever build a status/health-check "dashboard" website
+If we ever build a health "dashboard" website
(e.g. <https://status.sv.gnu.org>), these are the suggested checks for
each of [[SavannahServices]].
@@ -8,8 +7,8 @@
TODO:
* instead of using hard-coded user 'agn', create a dedicated user
- on savannah and add ssh pubkeys to it.
-* create perl script with www-mechanize to test login on the php frontend.
+ on Savannah and add ssh pubkeys to it.
+* create Perl script with www-mechanize to test login on the PHP frontend.
* remove '0' suffix from server names below when migration is complete.
@@ -16,7 +15,7 @@
VCS0
----
-anonymous clones/checkouts (protocol-specific xinetd daemon)
+Anonymous checkouts (protocol-specific xinetd daemon)
git clone git://git0.sv.gnu.org/datamash.git
svn co svn://svn0.sv.gnu.org/texinfo/trunk
@@ -34,9 +33,8 @@
You tried to execute: ls
Sorry, you are not allowed to execute that command.
+VCS ssh access:
-source-control ssh access:
-
bzr branch bzr+ssh://agn@bzr0.savannah.nongnu.org/gnewsense/docs
git clone agn@git0.sv.gnu.org:/srv/git/grep.git
hg clone ssh://agn@hg0.sv.gnu.org/health
@@ -47,7 +45,7 @@
cvs -d:ext:agn@cvs0.sv.gnu.org:/web/zdl co zdl
cvs -d:ext:agn@cvs0.sv.gnu.org:/srv/cvs/web/zdl co zdl
-read-only anonymous rsync access:
+Read-only anonymous rsync access:
rsync -avhP rsync://git0.sv.gnu.org/git/datamash.git .
rsync -avhP rsync://svn0.sv.gnu.org/svn/texinfo .
@@ -76,13 +74,10 @@
https://hg0.savannah.gnu.org/hgweb/health/
-
-
-
download0
---------
-downloads/releases (directory listing, test also with http):
+Downloads (directory listing):
http://download0.savannah.gnu.org/releases/datamash/src/
https://download0.savannah.gnu.org/releases/datamash/src/
@@ -96,9 +91,8 @@
Connection: keep-alive
Location: http://nongnu.askapache.com/datamash/src/datamash-latest.tar.gz
+Test download area with no redirections:
-Test download/releases with no redirections:
-
http://download-mirror0.savannah.gnu.org/releases/datamash/
https://download-mirror0.savannah.gnu.org/releases/datamash/
@@ -113,7 +107,7 @@
ETag: "58191d60-1cde6a"
Accept-Ranges: bytes
-Mirror-check (see to where you'll be redirected):
+Mirror check (see where you are redirected):
$ curl https://download0.savannah.gnu.org/mirror-check/
GNU Savannah - mirror check
@@ -138,7 +132,7 @@
https://arch0.savannah.gnu.org/archives/
-read-only anonymous rsync:
+Read-only anonymous rsync:
rsync -avhP rsync://download0.sv.gnu.org/releases/datamash .
rsync -avhP rsync://download0.sv.gnu.org/audio-video/index.html .
@@ -154,4 +148,3 @@
rsync -avhP agn@download0.sv.gnu.org:/srv/download/datamash .
rsync -avhP agn@download0.sv.gnu.org:/srv/audio-video/ghm2009/ .
-
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Savannah-cvs] [574] proofread,
ineiev <=