One will want to also carefully read the information/documentation further below, but
high-level reminder/synopsis points:

• production:
  • 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:
      • http://www.balug.org/
      • https://secure.balug.org/ (http://secure.balug.org/ "forces" (HTTP 301 redirects) to https)
        )
    • /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))
    • /var/www/www.new.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)
    • content from /var/www/www.balug.org/ may or may not be automagically replicated to http://www.balug.org/ server(s)!
    • to update/refresh http://www.balug.org/ content from /var/www/www.balug.org/:
      • as user id balugwm1 on webmaster.balug.org, run the command:
        $ www.balug.org_rsync
      • note that:
        • the command referenced above may, or may not, be scheduled to automagically run periodically via crontab (see balugwm1's crontab)
        • content placed in /var/www/www.balug.org/ may or may not be visible or immediately visible at http://www.balug.org/, but is not guaranteed to be visible accross all http://www.balug.org/ until the noted www.balug.org_rsync command has been successful executed.
        • contents under /var/www/www.balug.org/ must be readable by id balugxfr (e.g. world readable) to successfully replicate and be visible across http://www.balug.org/ site(s).
• non-production:
  • rather analogous to production, id balugwm2 has rather to quite full access to most or all non-production web areas on webmaster.balug.org. Note also that group balugwm2 may also share much of that access, and other id(s) may also have some or much access to certain non-production areas.
  • access (e.g. via sudo - shouldn't log into it directly) id balugwm2 on webmaster.balug.org, e.g.:
    $ ssh -atx -l your_login webmaster.balug.org. 'umask 077 && cd / && exec sudo su - balugwm2'
  • key non-production areas:
    • /var/www/www.beta.balug.org/ - beta test area http://www.beta.balug.org/
    • /var/www/www.test.balug.org/ - (alpha / proof-of-concept) test area http://www.test.balug.org/
    • /var/www/www.php.test.balug.org/ PHP test area http://www.php.test.balug.org/

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/
most notably:
/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
/var/www/www.balug.org/
but does have full reign over most content in/under that location.