server

It's actually called Etherpad Lite but i hate that spelling.

This will be a copy-paste of http://mclear.co.uk/2011/08/01/install-etherpad-lite-on-ubuntu/ except for a few things taken from https://github.com/Pita/etherpad-lite#readme and workarounds when things do not go as planned.

This is the once per server or computer setup required for Deploying the Agaric Way.

Requirements

To ease deployment the remote rake tasks from Vlad the Deployer are used. Before using it the following software must be installed:

Stefan figured out how to include the config/deploy.rb from somewhere else.

Usually the ruby load path includes something like /usr/local/lib/site_ruby/1.8//. You can verify that by typing "puts $LOAD_PATH" in an irb session.

Just move the config folder into it.

This should be done by cloning the central git repository of this folder:

cd /usr/local/lib/site_ruby/1.8/x86_64-linux/
git clone -o agaric git.agariclabs.org:/srv/git/agaric/vlad.git vlad

Apache will also log errors to:

syslog

Stefan notes: in case of panic you can try to grep -R in /var/log for PHP Fatal error

Benjamin Doherty says this is covered in the DGD7 environment chapter.

As root:
aptitude
Find drush under PHP.

At the bottom of the information about the drush package, there's an i that means installed next to 2.0 and a p that means no packages or config files or anything are present next to drush 3.3.

Type + when the drush 3.3 line is highlighted.

Then type g to upgrade (twice, first it takes us to a confirmation page).

Note: On Agaric's servers the package list is updated daily by a cron job, but updating the package list can be invoked by hitting u if necessary.

I originally posted the problem to the Bubbletimer module issue queue, Unable to save (pressing Save button has no effect).

The error can be seen be seen on the server by looking at the Apache error log:

sudo tail -f /var/log/apache2/error.log

Try to submit the 20 activity form, and nothing happens on the Drupal /bubbletimer page, but this error shows up in the log:

Blocked and receiving an error "ssh: connect to host" "port 22: Connection refused", Stefan added the IP address where this was not working to the hosts allow file, and explained the system.

There's two relevant files: /etc/hosts.allow and /etc/hosts.deny

/etc/hosts.deny is updated by the denyhosts package based on attacks and suspicious behaviour. it can be overridden by /etc/hosts.allow

An entry consists of a service, such as ssh, and a number of IP addresses.

Creating a public key

The user to be added (we'll call him Andrew) types this in his terminal:

ssh-keygen

Then he sends his public key to the person acting as sysadmin at the moment. As an e-mail attachment is fine. For users not used to the command line it can be hard to find the public key in a hidden .ssh folder, but it is possible to use scp to put it on a server both the user and the acting sysadmin have access to.

Adding the user to the server

The sysadmin then logs into the test server and uses standard Debian commands: