I've now been living in Finland for two years, and I'm pondering a small project to translate my main website into Finnish.
Obviously if my content is solely Finnish it will become of little interest to the world - if my vanity lets me even pretend it is useful at the moment!
The traditional way to do this, with Apache, is to render pages in
multiple languages and let the client(s) request their preferred version
Accept-Language:. Though it seems that many clients are terrible
at this, and the whole approach is a mess. Pretending it works though
we render pages such as:
Then "magic happens", such that the right content is served. I can then do extra-things, like add links to "English" or "Finnish" in the header/footers to let users choose.
Unfortunately I have an immediate problem! I host a bunch of websites
on a single machine and I don't want to allow a single site compromise
to affect other sites. To do that I run each website under its own Unix
user. For example I have the website "steve.fi"
running as the "
s-fi" user, and my blog runs as "
s-blog", or "
root@www ~ # psx -ef | egrep '(s-blog|s-fi)'
s-blogfi /usr/sbin/lighttpd -f /srv/blog.steve.fi/lighttpd.conf -D
s-blog /usr/sbin/lighttpd -f /srv/blog.steve.org.uk/lighttpd.conf -D
s-fi /usr/sbin/lighttpd -f /srv/steve.fi/lighttpd.conf -D
There you can see the Unix user, and the per-user instance of
which hosts the website. Each instance binds to a high-port on
localhost, and I have a reverse proxy listening on the public IP address
to route incoming connections to the appropriate back-end instance.
I used to use
thttpd but switched to
lighttpd to allow CGI scripts
to be used - some of my sites are slightly/mostly dynamic.
It seems my simplest solution is to switch from having lighttpd on the back-end to running apache2 instead, but I've not yet decided which way to jump.
Food for thought, anyway.