This is an old revision of the document!
Bay Area Linux Users Group (BALUG) webmaster
webmaster care and feeding - editing of BALUG web pages - production and non-production, etc.
the short version :-)
One will want to also carefully read the information/documentation further below, but
high-level reminder/synopsis points:
access (e.g. via sudo - shouldn't log into it directly) id balugwm1 on webmaster.balug.org (e.g.:
$ ssh -atx -l your_login webmaster.balug.org. 'umask 077 && cd / && exec sudo su - balugwm1'
key production areas:
/var/www/www.balug.org/ (main production area, see also production synchronization further below, serves at least:
/var/www/www.archive.balug.org/ (archival/historical content - generally also "too big" (at least in total) to replicate across all www.balug.org server(s))
.balug.org/ (production staging/preview
area - does not automagically replicate to production, but very handy for previewing content (e.g. at http://www.new.balug.org/
) before promoting to production
production synchronization (rsync)
CAUTION - THIS IS A WORK-IN-PROGRESS EDIT - MUCH MORE INFORMATION STILL NEEDS TO BE ADDED TO THE ABOVE AND BELOW
production (www.balug.org, etc.)
The normal way production is edited/updated, one should
have sudo access to the id balugwm1 (access to the group balugwm1 likely also provides much, but probably not all of the needed access)
on host balug-sf-lug-v2.balug.org (a.k.a. webmaster.balug.org, a.k.a. new.balug.org).
On that host, the various Name-based Virtual Host DocumentRoots
are located at/under:
/var/www/www.balug.org/ contains master production for http://www.balug.org/
Note that for various reasons (mostly historical and attempts to preserve/retrieve various historical content),
balugwm1 doesn't have absolute full reign over all content under
but does have full reign over most content in/under that location.