Set up ejabberd backups (files and PostgreSQL db) #6

New Issue

greg · 2019-01-02T22:35:40Z

greg commented

2019-01-02 22:35:40 +00:00

Extracted from https://gitlab.com/kosmos/chef/issues/22

greg self-assigned this 2019-01-02 22:36:20 +00:00

raucao commented

2019-01-03 01:06:58 +00:00

The HTTP uploads are stored in /var/www/xmpp.kosmos.org now. Added that a couple days ago.

(It's actually possible to write custom upload services, so we could do sth with RS in the long term.)

The HTTP uploads are stored in `/var/www/xmpp.kosmos.org` now. Added that a couple days ago. (It's actually possible to write custom upload services, so we could do sth with RS in the long term.)

greg commented

2019-01-24 18:29:02 +00:00

I have added backups as part of #9. Backups are running on Andromeda (no changes have been made to the existing ejabberd setup)

raucao commented

2019-01-25 03:39:38 +00:00

I have added backups as part of #9. Backups are running on Andromeda (no changes have been made to the existing ejabberd setup)

Does that mean you're already running that PR code against the current server? Because if yes, that seems kind of dangerous, and if no, then how do we have backups before/in order so we can run the PR code without potentially losing anything?

> I have added backups as part of #9. Backups are running on Andromeda (no changes have been made to the existing ejabberd setup) Does that mean you're already running that PR code against the current server? Because if yes, that seems kind of dangerous, and if no, then how do we have backups before/in order so we can run the PR code without potentially losing anything?

greg commented

2019-01-25 14:32:37 +00:00

Does that mean you’re already running that PR code against the current server? Because if yes, that seems kind of dangerous, and if no, then how do we have backups before/in order so we can run the PR code without potentially losing anything?

I have only executed the backup recipe on andromeda. The kosmos-ejabberd::default recipe has to be added to the run list of andromeda for the rest of the code to be executed. The PR code will have to be executed on an another server first, since it also updates ejabberd to 18.12

> Does that mean you’re already running that PR code against the current server? Because if yes, that seems kind of dangerous, and if no, then how do we have backups before/in order so we can run the PR code without potentially losing anything? I have only executed the backup recipe on andromeda. The `kosmos-ejabberd::default` recipe has to be added to the run list of andromeda for the rest of the code to be executed. The PR code will have to be executed on an another server first, since it also updates ejabberd to 18.12

raucao commented

2019-01-26 02:14:20 +00:00

Ah, got it. Good idea.

raucao commented

2019-03-14 01:34:15 +00:00

I thought backups are already in place for ejabberd? (Said in the last call.)

greg closed this issue

2019-05-16 09:22:07 +00:00

Sign in to join this conversation.

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/chef#6