Introduction
Now that triggers have been implemented in the repository tools, we'd like to start sending e-mail on changes to the publicly available Vesta packages to provide an alternative to the RSS feeds on pub.vestasys.org.
We'll use the email-trigger.pl example to send e-mail to the vesta-devel mailing list. (We might change this to use a separate list in the future.)
System Administrators
You'll first need to upgrade to at least release/12.pre13/9 to get repository tools with triggers.
People running a Vesta peer repository to dev.vestasys.org may want to simply set it up in the system-wide vesta.cfg. (See the below section.)
Users
If you regularly make changes that would run the email trigger script, you should make sure that you can send outgoing e-mail from the machine where you run the Vesta commands and that your e-mail address can send e-mail to the vesta-devel mailing list. If you are already subscribed to vesta-devel from another e-mail address, you should subscribe the address your change e-mails will come from but set the options for that address to not receive any messages. To do that, first subscribe to the list and then:
- At the bottom enter your e-mail address and click on "Unsubscribe or edit options"
- Enter your password when prompted
- Scroll down to "Mail delivery" (the first item under "Subscription Options") and set it to "Disabled"
- Click on "Submit My Changes"
vesta.cfg setup
Either the system administrator can set up the triggers in the system-wide vesta.cfg, or users can set them up in their personal vesta.cfg.
Here's how you might configure this in vesta.cfg:
[vcheckin post trigger] 100mail = /vesta/vestasys.org/vesta/repos_ui/latest/examples/triggers/email-trigger.pl --to vesta-devel@lists.sourceforge.net --dir /vesta/vestasys.org --dir /vesta/beta.vestasys.org [vbranch post trigger] 100mail = /vesta/vestasys.org/vesta/repos_ui/latest/examples/triggers/email-trigger.pl --to vesta-devel@lists.sourceforge.net --dir /vesta/vestasys.org --dir /vesta/beta.vestasys.org [vcreate post trigger] 100mail = /vesta/vestasys.org/vesta/repos_ui/latest/examples/triggers/email-trigger.pl --to vesta-devel@lists.sourceforge.net --dir /vesta/vestasys.org --dir /vesta/beta.vestasys.org
Alternatively you might want to copy the email-trigger.pl script somewhere outside the repository and reference it there.
Timing of e-mail and URL Validity
Note that these triggers will send e-mail immediately on each vcreate/vbranch/vcheckin, but the URLs they include will point into the vestaweb for the public repository on pub.vestasys.org. That is updated by replication twice an hour, so the URL in the e-mail will not be valid immediately.