Commit fa99e428 authored by Salvatore Bonaccorso's avatar Salvatore Bonaccorso

Document changes on the setup on soriano for the git migration

parent c0f1f95b
......@@ -4,25 +4,28 @@ Tracker setup on soriano.debian.org
(This is internal documentation, in case things need to be fixed.
It is not relevant to day-to-day editing tasks.)
The code and data is organized via
https://salsa.debian.org/security-tracker-team/
Relevant files and directories
------------------------------
The tracker runs under the user ID "sectracker". Most of its files
are stored in the directory /srv/security-tracker.debian.org/website:
bin/cron invoked by cron once every minute
bin/cron-hourly invoked by cron once every hour
bin/cron-daily invoked by cron once every day
bin/read-and-touch invoked by ~/.procmailrc
bin/start-daemon invoked by cron at reboot
bin/cron invoked by cron once every minute
bin/cron-hourly invoked by cron once every hour
bin/cron-daily invoked by cron once every day
bin/read-and-touch invoked by ~/.procmailrc
bin/start-daemon invoked by cron at reboot
secure-testing Subversion checkout
secure-testing/bin/* main entry points, called bin bin/cron
secure-testing/stamps/* files which trigger processing by bin/cron
security-tracker Git checkout
security-tracker/bin/* main entry points, called bin bin/cron
security-tracker/stamps/* files which trigger processing by bin/cron
~sectracker/.procmailrc invokes bin/read-and-touch to create stamp
files, which are then picked up by bin/cron. This is done to serialize
change events in batches (e.g., commits originated from git-svn).
change events in batches (e.g., commits originated from git).
<sectracker@soriano.debian.org> is subscribed to these mailing lists to
be notified of changes:
......@@ -88,15 +91,9 @@ The PTS fetches bug counts from this URL:
Code updates
------------
Updates to the Subversion checkout only affect the directory
/srv/security-tracker.debian.org/website/secure-testing/data.
Code changes need to be applied manually, using "svn update",
and a service restart (see above).
Subversion repository mirror
----------------------------
Updates to the Git checkout only affect the directory
/srv/security-tracker.debian.org/website/security-tracker/data. Code
changes need to be applied manually by inspecting the changes done in
the security-tracker.git.
The Subversion repository is mirrored (including history) using
svnsync, to the /srv/security-tracker.debian.org/subversion-backup
directory. The sectracker crontab contains an entry which runs
svnsync periodically.
After that a service restart is needed (see above)
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment