Infrastructure

it does autostart etherpad on reboot (via an @reboot cronjob) - but as bug #119 mentioned: it needs restarting after mysql restart.
Bitten by this today again. the persistent connection to mysql is gone and the result is non-working etherpad. went dead at around 12:00, reported 7 hours later...

But this persistent connection might be used for the monitoring. If there is no process for user "etherpad" in mysql's processlist, then etherpad is dead/needs to be restarted.

Etherpad is supervised by supervisord, this should be documented

Florian Effenberger wrote:

Need feedback from Beluga about his recent changes

npm i ep_copy_paste_images
npm i ep_comments_page
npm i ep_tables2
npm i ep_foot_note

Where do we stand wrt. this?
All bits should be in place, we "just" need to get the documentation written
Maybe some volunteer can do that based on my ODT and Beluga's notes, and put things into RST format?

After some interdependencies occured on kermit we need to re-setup etherpad in a vm during the migration of kermit to VMs, and will document it during that process.

With the new Etherpad setup, do we now have proper documentation and can close this ticket?

Florian Effenberger wrote:

With the new Etherpad setup, do we now have proper documentation and can close this ticket?

Ping?

I have Brett's notes in the list of things to cleanup, convert to RST and commit to infra-docs

Guilhem Moulin wrote:

I have Brett's notes in the list of things to cleanup, convert to RST and commit to infra-docs

Any updates on that?