What we do when adding new users
This page lists stuff we should be doing when we add new accounts to the
system. If we can automate as much as possible, it'd be fab. Otherwise, once
we've settled this, I'll turn it into a checklist.
Service logins
Things users should be given logins on some or all of (we need to decide which
by default):
- Zope
- Webmin
- Mailman
- WebDAV?
dj - none by default IMO
Mailing lists
All users with email accounts should be added to [email protected].
Those with shell accounts should be added to [email protected].
We should do similar for zopeusers, etc. - anything which we need
to make announcements about.
dj - everyone on [email protected] + a seperate list for [email protected]
The admins need to be on admin(s)@j-colo.net, not to mention
postmaster, hostmaster etc.
Home dirs
Home dirs should contain:
- Aliases files for each of a user's domains
- Symlinks to each of a user's vhost roots
- For shell/expert users: symlinks to zone files for their own domains
or webmin accounts
- dj - mail directory
- choccy on the pillow
vhosts and domains
- vhost dirs should live somewhere near the top, like /www (symlinked if
necessary). They should contain:
- htdocs/
- cgi-bin/ (i.e. not letting it live in htdocs/)
- logs/
- cgi-perl/ (the mod-perl dir - but not by default!)
- should be chowned to the user
- should be named after the domain, without the "www."
- directory indexing - on or off by default?
- we should have a default front page: "This J-Colo host has not been set up
yet. In the meantime, here is some light music."
- would be really really neat if we could mount Zope spaces here too, as
filesystems
- Mail aliases file to live there too?
- Mail aliases should come with catch-all set by default to the owner
- web interface to mail aliases?
look at webmin for this?
- what about mailing lists (i.e. can we easily let users create their
own?)
dj - simple mailing list in qmail is done by doing [email protected] is a list of addresses in a .qmail file.
Grouping configurations
Users (those who pay) can have multiple entries in config files on the system,
such as multiple vhosts in httpd.conf or multiple logins in /etc/passwd. These
should be grouped by user and delimited by hashed comments in the file.
Non-shell accounts
Shell in /etc/passwd should be set to /usr/bin/passwd. FTP
access should be chrooted to the user home.