From: Bruce Fitzsimons <bwooce@gm...> - 2004-12-01 22:19:54
I'm working on a photo-album type system that I want to run on my
site. I'm a little stuck though as I need two different DB instances
attached to one yaws instance.
I can only run one copy of yaws as I only have one public IP address,
so I'm using http 1.1 named based hosting to differentiate the
websites. I really want to be able to throw multiple new webapps in,
but I'm running into the following problems:
1. Mnesia is node orientated -- one DB per node. I'm not complaining
about that, but it does mean I either add tables for different apps
willy-nilly or break out the DBs into DB server nodes. The former
option isn't pretty.
2. I have to throw the .beams for any appmods into the one directory,
or add the ebin directory for each app to the startup script and
restart yaws. Neither option is good.
I could have one clean (empty) version on yaws sitting out the front
doing proxying by tcp port but thats complicated to configure (I've
done it with Apache before) and I have to draw diagrams to make sense
of it. I'm never sure what kind of proxy I need.
Has anyone crossed this bridge?
I can think of a few architectural changes that would allow me to have
a lightweight central server which passed off requests to other named
nodes natively after identifying which one it should be. I'm not sure
that it would have much use outside solving this problem though.