This is an automated email from the ASF dual-hosted git repository.
sebb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/whimsy.git
The following commit(s) were added to refs/heads/master by this push:
new 4ac0ed43 Stale references [skip ci]
4ac0ed43 is described below
commit 4ac0ed43085d10d5355b0520080f11ef5291a675
Author: Sebb <[email protected]>
AuthorDate: Tue Sep 17 23:52:00 2024 +0100
Stale references [skip ci]
---
DEPLOYMENT.md | 4 ++--
DEVELOPMENT.md | 5 +++--
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/DEPLOYMENT.md b/DEPLOYMENT.md
index 4965b8dd..28cd0f0c 100644
--- a/DEPLOYMENT.md
+++ b/DEPLOYMENT.md
@@ -49,7 +49,7 @@ that management of Whimsy code and tools is a PMC
responsibility.
<a name="puppetnode"></a>
The **puppet definition** is contained in the following files (these are
private files and need a login):
- *
https://github.com/apache/infrastructure-p6/blob/production/data/nodes/whimsy-vm6.apache.org.yaml
(Includes modules, software, vhosts, ldap realms, and httpd.conf)
+ *
https://github.com/apache/infrastructure-p6/blob/production/data/nodes/whimsy-vmN.apache.org.yaml
(Includes modules, software, vhosts, ldap realms, and httpd.conf)
*
https://github.com/apache/infrastructure-p6/tree/production/modules/vhosts_whimsy/lib/puppet/functions
(macro functions used above)
@@ -98,7 +98,7 @@ and running - these are only needed for a new deployment.
* `curl -N localhost:34234` - should produce 'curl: (52) Empty reply from
server' or similar
* if curl replies with something else, check that the service is still
running (and has not just been restarted)
* if the syslog contains a message of the form:
- 'Sep 24 13:09:07 whimsy-vm6 ruby[3435205]: what(): Encryption not
available on this event-machine'
+ 'Sep 24 13:09:07 whimsy-vmN ruby[3435205]: what(): Encryption not
available on this event-machine'
then it will be necessary to re-install the gem eventmachine
If the service still does not start, try stopping and starting it:
`sudo systemctl stop/start board-agenda-websocket.service`
diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md
index d7bd0f55..830013fb 100644
--- a/DEVELOPMENT.md
+++ b/DEVELOPMENT.md
@@ -336,7 +336,7 @@ User authentication for any CGI script is provided by the
http server's
LDAP module, and can be done by adding the path to the CGI in the
deployment descriptor for the server under the appropriate `authldap` realm:
-https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/whimsy-vm4.apache.org.yaml#L127
+https://github.com/apache/infrastructure-p6/blob/production/data/nodes/whimsy-vm7.apache.org.yaml#L251
Note that the LDAP module does not currently handle boolean conditions
(example: members **or** officers). The way to handle this is to do
@@ -367,7 +367,8 @@ server subscribe to the list.
- Subscribe _listname_@whimsy-_server_vmname_.apache.org to the desired
mailing list (see also [Deployment instructions](DEPLOYMENT.md#manual-steps))
-- Add your _listname_ to the `:apache_mailmap:` entry in
[puppet](https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/whimsy-vm4.apache.org.yaml#L63)
+- Add your _listname_ to the `:apache_mailmap:` entry
+ in
[puppet](https://github.com/apache/infrastructure-p6/blob/production/data/nodes/whimsy-vm7.apache.org.yaml#L107)
- Note that tools/deliver.rb will dump all mail locally (it does not
currently get cleaned out) where it can be used by ASF::Mail
