[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] [105] web server restarts, rm dead frontpage links, other
From: |
karl |
Subject: |
[Savannah-cvs] [105] web server restarts, rm dead frontpage links, other tweaks |
Date: |
Thu, 06 Nov 2014 00:32:36 +0000 |
Revision: 105
http://svn.sv.gnu.org/viewvc/?view=rev&root=administration&revision=105
Author: karl
Date: 2014-11-06 00:32:24 +0000 (Thu, 06 Nov 2014)
Log Message:
-----------
web server restarts, rm dead frontpage links, other tweaks
Modified Paths:
--------------
trunk/sviki/FrontEnd.mdwn
trunk/sviki/FrontPage.mdwn
trunk/sviki/HowToAdminThisWiki.mdwn
Modified: trunk/sviki/FrontEnd.mdwn
===================================================================
--- trunk/sviki/FrontEnd.mdwn 2014-11-01 00:27:22 UTC (rev 104)
+++ trunk/sviki/FrontEnd.mdwn 2014-11-06 00:32:24 UTC (rev 105)
@@ -1,14 +1,25 @@
-The Savane front-end is installed in the 'frontend' virtual machine, in
-`/usr/src/savane/` .
+Savannah front-end
+==================
+The Savane front-end is installed on the 'frontend' virtual machine, in
+`/usr/src/savane/`, which pulls from the `administration/savane.git`
+repository.
Some of the content is configurable, using text files that are stored in
-the webcvs repository.
+the webcvs repository for `administration`.
<http://web.cvs.savannah.gnu.org/viewvc/administration/content/?root=administration>
+The live CVS checkout is at `frontend:/etc/savane/content`.
-When that CVS repository is updated, there was a commit hook to update
-the live installation, but with the move from VServer to Xen, we don't
-have bind mounts anymore. So now any change to the files requires
-logging in to frontend and doing a cvs update: the live CVS checkout is
-at /etc/savane/content.
+After committing changes in either of those repositories, to make the
+changes live, it is necessary to log in to frontend and manually `git
+pull` or `cvs update` in the live checkout directory. There are no
+automated updates of the live checkouts (and thus they often lag behind
+the repository; if you see this, please deal with it).
-`/usr/src/savane` pulls from the `administration/savane.git` repository.
+Web server restarts
+-------------------
+To restart the web server (on any of the hosts running one), the usual
+`service apache2 restart` should do it, or `service apache2 reload` if
+you wish. Of course you should check the sites before and after
+restarting, to make sure things are working. There are no
+password-protected SSL keys on Savannah, so that the web servers can
+come up unattended at boot.
Modified: trunk/sviki/FrontPage.mdwn
===================================================================
--- trunk/sviki/FrontPage.mdwn 2014-11-01 00:27:22 UTC (rev 104)
+++ trunk/sviki/FrontPage.mdwn 2014-11-06 00:32:24 UTC (rev 105)
@@ -111,7 +111,6 @@
- [[AudioVideo]]
- [[Backup]]
- [[Bzr]]
- - [[BzrFAQs]]
- [[UsingBzr]]
- [[Compromise2010]]
- [[CvS]]
@@ -134,13 +133,9 @@
- [[DataExport]]
- [[FrontEnd]]
- - [[VServer]]
-
- [[GNUArch]]
- - [[ArchZoom]]
- [[Git]]
- - [[Basic]]
- [[UsingGit]]
- [[CvsDisabling]]
@@ -161,7 +156,6 @@
- Subversion
- [[SvN]]
- - [[BerliOS]]
- [[CvSToSvN]]
- [[CvsDisabling]]
- [[SavaneSvkBranch]]
@@ -169,7 +163,6 @@
- [[AdminSvnImport]]
- [[TlS]]
- - [[CAcert]]
- [[ZWiki]]
- [[ZopeBackup]]
@@ -190,12 +183,9 @@
- [[TasksList]]
- [[MonoToNe]]
- [[SavaneTasks]]
- - [[SavaneRewrite]]
+ - [[SavaneRewrite]]
- [[SvNTasks]]
- - [[WikiSpam]]
- - [[ZWikis]]
- - [[WebPages]]
- [[VPN]]
- [[VPNConfiguration]]
Modified: trunk/sviki/HowToAdminThisWiki.mdwn
===================================================================
--- trunk/sviki/HowToAdminThisWiki.mdwn 2014-11-01 00:27:22 UTC (rev 104)
+++ trunk/sviki/HowToAdminThisWiki.mdwn 2014-11-06 00:32:24 UTC (rev 105)
@@ -22,15 +22,18 @@
Using Git
---------
-The respository is an Subversion repository. It is possible to access
-Subversion repositories using Git through git-svn. The git-svn
-conduit is an optional addition to the git suite of tools.
+The repository is an Subversion repository. It is possible to access
+Subversion repositories using Git through `git-svn`, which
+is an optional addition to the git suite of tools.
0. git svn clone --stdlayout svn+ssh://svn.savannah.gnu.org/administration
+
0. Run `git commit` to commit to the local git repository.
-0. Run `git svn dcommit` to publish the results to the public Subversion
repository.
+0. Run `git svn dcommit` to publish the results to the public Subversion
+repository.
+
Wiki configuration
------------------
In the file `frontend:~sviki/ikiwiki.setup`. At present, we are using
@@ -38,7 +41,7 @@
That file is in RCS, for simplest version control. Anyone in the
`staff` group can edit it, which should be anyone with shell access to
-the machine. (All Savannah administrators are welcome to have shell
+the machine. (Savannah administrators are welcome to have shell
logins, but Savannah users do not, for obvious security reasons.)
The web server configuration bits are in
@@ -55,7 +58,7 @@
For Savannah, we really wanted the source repository to be accessible in
the standard Savannah ways, that is, through the `administration`
project (<http://savannah.gnu.org/projects/administration>, which holds
-all the live Savannah stuff that is checked into version control). That
+all the live Savannah stuff which is checked into version control). That
way, access would be controlled just as to any other source repository.
We used the Subversion repository in `administration` as the wiki source
partly because it was otherwise unused and partly because Karl (who did
@@ -96,7 +99,7 @@
restart after a reboot. We could find no way of extracting the actual
text from the huge .fs files hanging around. Sigh.
-So we manually saved the HTML pages in the Wayback Machine, at
+So we manually saved the HTML pages from the Wayback Machine, at
<http://archive.org>. Fortunately there had been essentially no edits
since before the crack, and the pre-crack versions were available. Yay
for Wayback.
@@ -109,8 +112,9 @@
spaces in the names are probably broken links now, by the way.
We had previously decided to use ikiwiki, to avoid ever having to go
-through the agony of a cracked wiki again. So next, on frontend,
-we just install the basic Debian package; we don't need the very latest.
+through the agony of restoring a cracked wiki again. So next, on
+frontend, we just install the basic Debian package; we don't need the
+very latest.
apt-get install ikiwiki
@@ -143,7 +147,8 @@
ikiwiki --setup ikiwiki.setup
-Skip CGI for now (forever?).
+Skip CGI for now (forever?). People will just edit through their local
+vc checkout, not on the web.
Create `administration`'s svn repository (can do this anyway):
@@ -155,10 +160,10 @@
echo hi there > index.mdwn
svn commit
-(Well, the `svn co` command I actually ran was different from the above
-standard one, because I have a shell account on vcs and the other
-machines [[SavannahArchitecture]]. But that is an irrelevant detail
-here.)
+(Full disclosure: the `svn co` command I actually ran was different from
+the above standard one, because I have a shell account on vcs and the
+other machines [[SavannahArchitecture]]. But that is an irrelevant
+detail here.)
Back on frontend, ikiwiki will need to do updates, so:
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Savannah-cvs] [105] web server restarts, rm dead frontpage links, other tweaks,
karl <=