Matt Sergeant wrote:
Yes, it makes you have to think before deploying. I like that the
default port is 2525.
Funny, but that was exactly the reason I was going to say I liked the
status quo...
Here's my standard deployment strategy:
1) Check out the machine specific configuration from my SVK mirror into
a new directory next to the existing running configuration.
2) Set the IP address but not the PORT env/ variables and run the code
in a shell (i.e. without logging).
3) Send a variety of messages (both successes and failures, e.g. virus
infected) from several different IP addresses including one on my
internal blacklist to make sure all features work.
4) Stop the code running in the shell and test the logging directory
manually.
5) Set the PORT env/ file to 25.
6) rm /service/qpsmtpd
mv /var/qmail/qpsmtpd /var/qmail/qpsmtpd.old
(existing service will continue to happily run).
7) mv /var/qmail/qpsmtpd.new /var/qmail/qpsmtpd
cd /var/qmail/qpsmtpd
ln -s $PWD /service
(existing service still happily running; new service unable to start
because it cannot bind to port 25).
8) cd /var/qmail/qpsmtpd.old
svc -dx . ./log
(old service will stop and new service will start up in < 5 seconds)
It's not quite like replacing all the parts in a 747 while still in
flight, but it works with minimum downtime. ;-)
HTH
John
