Chris@1601: #!/bin/bash
Chris@1601: 
Chris@1601: set -e
Chris@1601: 
Chris@1601: # Print reminders of the things that we haven't covered in the deploy
Chris@1601: # scripts
Chris@1601: 
Chris@1601: cat <<EOF
Chris@1601: 
Chris@1601: *** APACHE SSL CONFIGURATION
Chris@1601: 
Chris@1601:     The provisioning scripts set up a simple HTTP site only. Refer to
Chris@1606:     code-ssl.conf for an example HTTPS configuration (you will of
Chris@1606:     course need to provide the key/cert files).
Chris@1606: 
Chris@1607: *** CRON SCRIPTS
Chris@1607: 
Chris@1607:     A number of cron scripts have been installed. It might be no bad
Chris@1607:     thing to prime and test them by running them all once now. Some of
Chris@1607:     the services tested by the smoke test script (below) may depend on
Chris@1607:     their having run. Use deploy/any/run-cron-scripts.sh for this.
Chris@1607: 
Chris@1606: *** SMOKE TEST
Chris@1606: 
Chris@1606:     There is a smoke test script in the deploy/test directory. That
Chris@1606:     is, a quick automated acceptance test that checks that basic
Chris@1606:     services are returning successful HTTP codes. Consider running it
Chris@1606:     against this server from another host, i.e. not just localhost.
Chris@1601: 
Chris@1601: *** EMAIL
Chris@1601: 
Chris@1601:     Outgoing email is required for notifications, but has not been
Chris@1608:     configured as part of this provisioning setup. You'll need to set
Chris@1608:     up the server's outgoing mail support and also edit the application
Chris@1608:     email settings in config/configuration.yml.
Chris@1601: 
Chris@1619: *** CRON EMAIL
Chris@1619: 
Chris@1619:     Ensure the MAILTO value in /etc/crontab is set to something real.
Chris@1619: 
Chris@1601: *** STATIC FRONT PAGE
Chris@1601: 
Chris@1601:     We have set up only the code/repository site -- if you want a
Chris@1601:     separate front page, remember to configure that!
Chris@1601: 
Chris@1601: EOF