I have also arrived at this project, after discovering it is one of the few/only ways to do client-side bitcoin work with web browsers. I'm working on Coinpunk right now (
http://coinpunk.org) and I am seriously considering switching over to this code base. It seems logical to me, because I would mainly be plugging the "missing completed gui wallet service" gap in the bitcoinjs toolchain right now. But of course, I need to be able to determine it's feasible to do so.
I'm running into problems getting the server running as well. I've hit the memory wall on my 2GB VPS (which is a problem, because my requirements are that it has to run on a relatively cheap VPS), and was having problems with the blockchain download going slow (which I solved by having the client connect to a local bitcoind which has the full blockchain). But now I'm back to the memory problem again.
This is not a bitcoinjs-server specific problem, I had very similar problems with bitcoind. The way I solved it with bitcoind was to reduce the number of connections to a very small number (3). I'm not sure why this worked exactly, and I'm not sure this is the same problem. It would be helpful for my understanding of the problem if I knew why the server had to maintain so much memory state here. Is this a garbage collection issue, or does it actually need over 1.5GB at some point to process the blockchain?
Currently when I try to connect with bitcoinjs-lib the request hangs. I'm not sure if this is because I'm running it on 0.10 (I'm at latest on master) or because it's still downloading the blockchain. I'll give it another try when I have the blockchain up to latest (crash from memory, up arrow, return).
I'm planning on spending the summer on the Coinpunk project full-time. So if I decided to go the JS route I will definitely be able to help on this project! I'm not sure if I'm necessarily qualified to do a refactor of the database to improve performance or what needs to be done, but it sounds like an interesting project, and one that needs to be addressed.
Cheers!
-Kyle