[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] [572] proofread
From: |
ineiev |
Subject: |
[Savannah-cvs] [572] proofread |
Date: |
Thu, 9 Feb 2023 06:16:24 -0500 (EST) |
Revision: 572
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=572
Author: ineiev
Date: 2023-02-09 06:16:23 -0500 (Thu, 09 Feb 2023)
Log Message:
-----------
proofread
Modified Paths:
--------------
trunk/sviki/DNS.mdwn
trunk/sviki/FrontEndHostRedirection.mdwn
trunk/sviki/ManuallyInstalledPackages.mdwn
trunk/sviki/MigrationChecklist.mdwn
trunk/sviki/https.mdwn
Modified: trunk/sviki/DNS.mdwn
===================================================================
--- trunk/sviki/DNS.mdwn 2023-02-09 10:50:55 UTC (rev 571)
+++ trunk/sviki/DNS.mdwn 2023-02-09 11:16:23 UTC (rev 572)
@@ -1,5 +1,4 @@
-DNS
----
+# DNS
DNS entries for savannah.gnu.org and savannah.nongnu.org may be
modified on the mgt0.savannah.gnu.org server.
@@ -23,7 +22,7 @@
Then `dig` or `nslookup` or `host` or whatever can be used to verify the
change, if desired.
-## entries format
+## Entry format
Always use *relative* domain names in savannah's `savannah.footer` file.
Use the following syntax:
Modified: trunk/sviki/FrontEndHostRedirection.mdwn
===================================================================
--- trunk/sviki/FrontEndHostRedirection.mdwn 2023-02-09 10:50:55 UTC (rev
571)
+++ trunk/sviki/FrontEndHostRedirection.mdwn 2023-02-09 11:16:23 UTC (rev
572)
@@ -3,8 +3,8 @@
Savannah handles three types of hosts redirection:
-1. shortcut URL to full URL (e.g. `*.sv.gnu.org` => `*.savannah.gnu.org`).
-2. `*.gnu.org` <=> `*.nongnu.org`, depending on project's type.
+1. Shortcut URL to full URL (e.g. `*.sv.gnu.org` => `*.savannah.gnu.org`).
+2. `*.gnu.org` <=> `*.nongnu.org`, depending on group type.
3. automatic-login to both `savannah.gnu.org` and `savannah.nongnu.org`
4. attachment requests from old URLs to dedicated domain
(`savannah.gnu.org/file/*` => `file.savannah.gnu.org/file/*`,
@@ -15,8 +15,8 @@
Shortcut URL redirection
------------------------
-Shortcur URL redirection (.e.g `*.sv.gnu.org` => `*.savannah.gnu.org`)
-is handled entirely in the apache configuration.
+Shortcurt URL redirection (.e.g `*.sv.gnu.org` => `*.savannah.gnu.org`)
+is handled entirely in the Apache configuration.
This would've been simple, if it were't for two complications:
@@ -87,7 +87,7 @@
FIXME: If there's a better configuration, please write to
savannah-hackers-public@gnu.org .
-FIXME: Document the apache setup for the production website, which use:
+FIXME: Document the Apache setup for the production website, which use:
sites-enabled/000-vhosts-gnu.org.conf -> ../sites-available/vhosts-gnu.org
sites-enabled/vhosts-nongnu.org.conf ->
../sites-available/vhosts-nongnu.org
@@ -127,31 +127,30 @@
Include sites-available/sv.inc
-
GNU/NONGNU redirection
----------------------
-gnu/nongnu redirection is handled entirely in thePHP code, based on
-whether the viewed project belongs to gnu or not (sometimes refers
+gnu/nongnu redirection is handled entirely in the PHP code, based on
+whether the viewed group belongs in GNU or not (sometimes referred
to as 'brother' site in the code/config files).
-Example: when a user visits <https://savannah.nongnu.org/projects/coreutils>
-she will be redirected to <https://savannah.gnu.org/projects/coreutils>
-because coreutils is an official gnu package.
+Example: when users visit <https://savannah.nongnu.org/projects/coreutils>
+they are redirected to <https://savannah.gnu.org/projects/coreutils>
+because coreutils is an official GNU package.
### Enabling/Disabling redirection
In `.savane.conf.php`, setting the boolean variable
-`$sys_debug_nobasehost` to `true` disable redirection completely -
+`$sys_debug_nobasehost` to `true` disables redirection completely -
useful for [[FrontEndDevelopmentSite]].
-### Project's based redirection
+### Group-based redirection
-When page is visited (if it relates to a hosted project), the
+When a page is visited (if it relates to a hosted group), the
function `$project->getTypeBaseHost()` is called and returns the host
-that is relevant to the viewed project (baed on the project's type).
+that is relevant to the viewed group (based on the group type).
The values on the production site are:
@@ -218,8 +217,6 @@
}
-
-
Auto-login to 'brother' site
----------------------------
@@ -265,7 +262,7 @@
$sys_brother_domain="jsmith.frontend0.savannah.gnu.org";
$sys_incdir="/home/jsmith/savannah/etc/savane/content/nongnu-content";
-The apache configuration must be set appropriately for each domain.
+The Apache configuration must be set appropriately for each domain.
See `SAVANE_CONF` settings above.
*NOTE*:
@@ -278,7 +275,6 @@
with cookie authentication (you'll see an error message saying
"Savane thinks your cookies are not activated for XXX" from `login.php`).
-
The 'brother' login sequences is used in two files:
`./frontend/php/account/login.php` and `./frontend/php/account/su.php`
(`su` implements "become superuser" feature for admins).
Modified: trunk/sviki/ManuallyInstalledPackages.mdwn
===================================================================
--- trunk/sviki/ManuallyInstalledPackages.mdwn 2023-02-09 10:50:55 UTC (rev
571)
+++ trunk/sviki/ManuallyInstalledPackages.mdwn 2023-02-09 11:16:23 UTC (rev
572)
@@ -1,3 +1,5 @@
+# Manually installed packages
+
Normally, packages are installed from Debian repositories:
- apt-get update
Modified: trunk/sviki/MigrationChecklist.mdwn
===================================================================
--- trunk/sviki/MigrationChecklist.mdwn 2023-02-09 10:50:55 UTC (rev 571)
+++ trunk/sviki/MigrationChecklist.mdwn 2023-02-09 11:16:23 UTC (rev 572)
@@ -19,13 +19,12 @@
* `/usr/src/infra/git/sv_cgit.pl`
-* Check for special permissions for gnu webmasters?
+* Check for special permissions for GNU webmasters?
see "GNU webpages repository access for www members"
section in [[UserAuthentication]] and also here:
<http://lists.gnu.org/archive/html/savannah-hackers-public/2016-05/msg00031.html>
-
Remaining setup tasks - Download0
---------------------------------
@@ -42,7 +41,7 @@
* Also grant MySQL access to 'downloads' (and other hosts which run perl
backend
scripts from savane).
-* verify mailing list creating works (with SSH to lists.gnu.org).
+* Verify mailing list creating works (with SSH to lists.gnu.org).
Wiki and Documentation
@@ -64,11 +63,11 @@
* Update the "libnss-mysql" section in [[UserAuthentication]] page,
based on updated setup on `vcs0`.
-* on `vcs0`, explain 'nice/timeout' scripts in /usr/local/bin.
+* On `vcs0`, explain 'nice/timeout' scripts in /usr/local/bin.
-* on `vcs0`, explain rsync (xinetd + rsyncd.conf)
+* On `vcs0`, explain rsync (xinetd + rsyncd.conf)
See Also
--------
-'TO DO Items' and 'FIXME' in [[SavannahHosts]].
\ No newline at end of file
+'TO DO Items' and 'FIXME' in [[SavannahHosts]].
Modified: trunk/sviki/https.mdwn
===================================================================
--- trunk/sviki/https.mdwn 2023-02-09 10:50:55 UTC (rev 571)
+++ trunk/sviki/https.mdwn 2023-02-09 11:16:23 UTC (rev 572)
@@ -1,12 +1,12 @@
HTTPS Certificates
==================
-This page describes the HTTPS configuration for Savannah's
+This page describes the HTTPS configuration for Savannah
new servers (e.g. `download0`, `frontend0`, `vcs0`, `mgt0`).
The current ('old') servers use a wildcard SSL certificate from GANDI.net.
The new servers use [Let's Encrypt](https://letsencrypt.org/) certificates.
-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).
@@ -13,10 +13,10 @@
* [[SavannahHosts]] - Configuration of the new servers
(i.e. mgt0, vcs0, frontend0, internal0, download0).
-Further reading about Savannah's web UI:
+Further reading about Savannah web UI:
-* [[FrontEnd]] - Notes about the current frontend setup (git,cvs).
-* [[FrontEndDevelopmentSite]] - Setting up development sites for savannah.
+* [[FrontEnd]] - Notes about the current frontend setup (git, cvs).
+* [[FrontEndDevelopmentSite]] - Setting up development sites for Savannah.
EFF's CertBot
@@ -25,7 +25,7 @@
[EFF's CertBot](https://certbot.eff.org/) is a program that registers
and renews "Let's Encrypt" certificates.
-Savannah's configuration uses the `webroot` method (aka `certonly`) in
+Savannah configuration uses the `webroot` method (aka `certonly`) in
which the web server exposes a specific directory over HTTP. Certbot
writes the authentication files to this directory and communicates
with the "Let's Encrypt" certificate authority to register/renew
@@ -46,7 +46,7 @@
described below.
-Savannah's non-root certbot installation
+Savannah non-root certbot installation
----------------------------------------
On Savannah we have installed a modified `certbot` recipe which allows
@@ -243,9 +243,9 @@
# Many more SSL-specific configuration
-### Frontend0's apache configuration
+### Frontend0 apache configuration
-The majority of the Apache's configurations are in
+The majority of the Apache configurations are in
`/etc/apache2/sites-available/sv.inc`. However this file does *not*
contain SSL configuration - as it is included twice in other files
(once for gnu, once for nongnu).
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Savannah-cvs] [572] proofread,
ineiev <=