This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
system:system_administration_rules_of_the_road_this_box [2007-05-14T02:11:36+0000] 198.144.194.236 typo fixes |
system:system_administration_rules_of_the_road_this_box [2015-11-25T10:36:30+0000] michael_paoli |
||
---|---|---|---|
Line 25: | Line 25: | ||
their priority (or at least approximate priority), with highest priority | their priority (or at least approximate priority), with highest priority | ||
(most important) first. | (most important) first. | ||
+ | Also, first, bit of "policy" update ... but may be more theoretical (e.g. conflicts with physical | ||
+ | reality & resources available at the time of this writing) - and may also, to fair extent, be relatively SF-LUG specific: | ||
+ | <file> | ||
+ | Date: Tue, 24 Nov 2015 22:10:12 +0000 | ||
+ | From: jim <jim@well.com> | ||
+ | |||
+ | Policies: | ||
+ | * The host of the sf-lug web site is a Linux machine or virtual machine | ||
+ | dedicated to running the sf-lug web site only. A "different host" may | ||
+ | refer to another VM running on the same physical host as that which | ||
+ | supports the sf-lug web site. | ||
+ | * the sf-lug web site itself should be static, with no interactive | ||
+ | software, for ease of maintenance and security; it is essentially an | ||
+ | internet-accessible yellow page style advertisement. | ||
+ | * The sf-lug web site can include links to interactive web pages, | ||
+ | although properly such interactive pages should be hosted on some | ||
+ | different host other than that which hosts the sf-lug web site (for | ||
+ | easy maintenance and security). | ||
+ | * the sf-lug web site host should be open to sf-lug supporters for | ||
+ | whatever they want to try out. "Trust is efficient." We assume no user | ||
+ | will alter work done by other users. We assume users will make mistakes, | ||
+ | even hork the host itself, and that users will use sudo rather than | ||
+ | the root account to make changes (exceptions to this include Michael | ||
+ | Paoli and Jim Stockford and whoever else can get Jim or Michael to | ||
+ | approve). Preferably users should experiment on a host other than that | ||
+ | which runs the sf-lug web site itself. | ||
+ | * Jim wishes to deprecate PHP on the host that supports the sf-lug web | ||
+ | site. Jim has no power to enforce this. Jim prefers shell scripts, C, | ||
+ | and Python. Jim's authority derives from his paying for domain name, | ||
+ | electrical power, bandwidth, and other costs. To the extent that | ||
+ | other people pay such costs, they derive authority. | ||
+ | </file> | ||
***High availability server** - to the extent feasible, this system should be treated as a server intended to be of rather to quite high availability. E.g. groups (such as [[http://www.sf-lug.org/|SF-LUG]] and [[http://www.balug.org/|BALUG]]) are or may be rather to quite dependent upon its availability, and generally would prefer the system be up and available as much as feasible. | ***High availability server** - to the extent feasible, this system should be treated as a server intended to be of rather to quite high availability. E.g. groups (such as [[http://www.sf-lug.org/|SF-LUG]] and [[http://www.balug.org/|BALUG]]) are or may be rather to quite dependent upon its availability, and generally would prefer the system be up and available as much as feasible. | ||
***Downtime and maintenance (system outages)** - to the extent feasible, when such outages are necessary or appropriate, they should be targeted to off-peak hours (usage logs may provide useful guidelines as to what days/times would best meet "off-peak" criteria), and should be scheduled in advance and with [[system:appropriate outage notification]]. | ***Downtime and maintenance (system outages)** - to the extent feasible, when such outages are necessary or appropriate, they should be targeted to off-peak hours (usage logs may provide useful guidelines as to what days/times would best meet "off-peak" criteria), and should be scheduled in advance and with [[system:appropriate outage notification]]. |