Comment 6 for bug 563484

2010-06-29 00:54 EEST: Fabián Rodríguez:
> According to Etherpad.org there is a package which is the preferred method to install (not the above as presented by Mikko):
> http://doc.etherpad.org/ep/pad/view/ro.lRwwt2zukr/latest

The method I presented was the only (easy) method available in that
time. Obviously, if you don't care about the latest source code, using a
repository is the easiest way to get automatic updates.

The package from repository should always match master branch of
git://github.com/ether/pad.git so if you build your own package, the
actual installed files should be identical.

The actual development happens in various forks. See
http://github.com/ether/pad/network for visualization (requires flash
plugin). Usually the most recent code can be found from repository
git://github.com/redhog/pad.git

However, the current package is far from ideal. See message #3 for
details. Basically the etherpad package contains extra copy of various
libraries that should be in separate packages.

> I have tested both (Mikko's and etherpad.org's package) on 10.04LTS VMs
> and both resulted in a usable but only locally accessible install. When
> trying to reach the Etherpad install from another host I got an error
> about reaching www.false.com:9000. It seems a superdomains variable
> needs to be set but I haven't found clear documentation about this.

The Debian package installation scripts should automatically prompt for
the domain (among other things) and automatically generate correct
configuration file at /etc/etherpad/etherpad.local.properties

If that does not happen, you should submit a new bug at
http://github.com/ether/pad/issues (search for existing bug first and if
one exists, enter extra information there instead of opening a new one).
Please, spend some time to specify exact steps to reproduce the problem.
If you can reproduce the problem with Ubuntu Live CD, it will make it
simpler for others to reproduce (in that case, the software environment
is identical for all testers).

> You may also encounter memory error and the only way I could start the server was to reboot and then:
> 1- cd /usr/share/etherpad
> 2. sudo ./bin/run.sh

sudo /etc/init.d/etherpad restart
should work also.

Could you elaborate about the "memory error"?