Comment 7 for bug 563484

@Mikko it's not that I don't care about the source code but this bug is about having a working package. Being able to quickly + easily test that beats building it from scratch having to install dependencies as each try fails repeatedly.

I see a few problems with the current package:

- It depends on sun-java6-jdk which is non-free and requires the partners' repository. I saw instructions on etherpad.org to use openjdk but I didn't have time to try that.

- Starting / stopping it using init.d gave no indications on errors (in fact it reports nothin if you are missing java, for example).
Most online docs wrongly indicate one needs to use this command to start the server:
/usr/share/etherpad/etherpad/bin/run-local.sh

It only runs as sudo and I needed to use the memory parameter to prevent an error (see below), as my VMs use 512M by default and Etherpad wanted 1G (another requirement not mentioned in any docs):
/usr/share/etherpad/etherpad/bin/run-local.sh 384M

The error message I referred to was :
Error occurred during initialization of VM
Could not reserve enough space for object heap

This did it, you may need the above memory parameter workaround (CTRL-C stops it gracefully):
sudo /usr/share/etherpad/bin/run.sh

I had to dpkg -L to find the above paths, once again that's missing information from the current docs. I tried to edit the current pad at etherpad's website but couldn't find a way to do so.

I lack the time to open the appropriate bugs upstream as I wouldn't be able to follow up on them. I am glad re-testing this in some time but right now I can't dedicate more time to it.

@Brian thank you, such information should be on etherpad's site, I could not find a way to update anything there.