whimsical-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From curc...@apache.org
Subject [whimsy] branch master updated: Call out where cron is configured
Date Thu, 05 Apr 2018 12:56:35 GMT
This is an automated email from the ASF dual-hosted git repository.

curcuru 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 e343c47  Call out where cron is configured
e343c47 is described below

commit e343c47814c92b7966778ee6bf0ef61128e28673
Author: Shane Curcuru <asf@shanecurcuru.org>
AuthorDate: Thu Apr 5 08:56:29 2018 -0400

    Call out where cron is configured
---
 DEPLOYMENT.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/DEPLOYMENT.md b/DEPLOYMENT.md
index e4ea83a..5cbb9b4 100644
--- a/DEPLOYMENT.md
+++ b/DEPLOYMENT.md
@@ -16,10 +16,10 @@ Configuration Locations
 ----
 Application developers may need to know where different things are configured:
 
-- Most **httpd config** is in the puppet definition whimsy-vm*.apache.org.yaml (below)
-- **SVN / git** updaters are in [repository.yml](repository.yml)
+- Most **httpd config** is in the [puppet definition whimsy-vm*.apache.org.yaml](#puppetnode)
+- **SVN / git** updaters and definitions of checkout directories are in [repository.yml](repository.yml)
+- **Cron jobs** are configured by whimsy_server/manifests/cronjobs.pp, which call various
Public JSON scripts
 - **Public JSON** generation comes from various www/roster/public_*.rb scripts
-  and is controlled by whimsy_server/manifests/cronjobs.pp
 - **Misc server config** is executed by whimsy_server/manifests/init.pp
 - **LDAP** configured in whimsy-vm*.apache.org.yaml
 
@@ -30,7 +30,7 @@ How Production Is Updated
   to define the 'whimsy-pubsub' service which runs [tools/pubsub.rb](tools/pubsub.rb)
 - pubsub.rb watches for any commits from the whimsy git repo at gitbox.apache.org
 - When it detects a change, it tells Puppet to update the VM as a whole
-- Puppet then updates various repositories, ensures required tools and setup 
+- Puppet then updates various svn/git repositories, ensures required tools and setup 
   is done if there are other changes to dependencies, and when needed restarts most 
   services that might need a restart
 - Puppet also does a `rake update` to update various gem or ruby settings

-- 
To stop receiving notification emails like this one, please contact
curcuru@apache.org.

Mime
View raw message