| 10 Nov 2018 |
 Mathijs | first things first, I'll try to get synapse working | 16:50:38 |
 Marcus (old) | yes, sure! | 16:51:01 |
| Mathijs | but it's fun to think about all the possibilities | 16:51:18 |
| Marcus (old) | Coffee: twif tagged | 17:00:58 |
 Nico | Mathijs: Thanks for the list of all third-parties. | 17:01:54 |
| Nico | In reply to @mathijs:matrix.vgorcum.com
don't worry, I'm mostly kidding We're now at the place where we can decide things without having too much work. So if you think with docker it's all easier, we can go that way. | 17:02:40 |
| Nico | Other option I'm thinking about is using Ansible to script all that stuff, even if we just use it on one machine. | 17:03:02 |
| Nico | Because once the forum machine died and we made some inreversible changes requiring us to set up the machine from scratch. With the forum software that's easy, but with the Matrix setup Ansible would make this situation a lot easier. | 17:04:29 |
| Nico | Mathijs: Do you already have a plan for backups? | 17:04:43 |
| Mathijs | In reply to @nico:dorfbrunnen.eu
We're now at the place where we can decide things without having too much work. So if you think with docker it's all easier, we can go that way. sure, we could even decide to keep synapse, coturn and postgresql installed on bare metal | 17:07:19 |
| Mathijs | and just install docker to add new stuff as we go along | 17:07:31 |
| Mathijs | In reply to @nico:dorfbrunnen.eu
Mathijs: Do you already have a plan for backups? other than dumping the database regularly and backing up all relevant files every once in a while, not really | 17:07:56 |
| Mathijs | I'm mostly not sure where to push the backup to | 17:08:25 |
| Nico | I've updated the roadmap in the admin issue to include TURN and dimension: https://gitlab.com/fdroid/admin/issues/94#note_115754656 | 17:08:41 |
| Mathijs | great | 17:08:57 |
| Nico | In reply to @mathijs:matrix.vgorcum.com
I'm mostly not sure where to push the backup to With the forum, we basically do the same. Every time I upgrade the forum, I download the latest backup. | 17:09:32 |
| Nico | That's not the best way, but it's at least something. | 17:09:45 |
| Mathijs | I'd be inclined to script stopping synapse, dumping the database and backing up and starting synapse back up | 17:10:48 |
| Mathijs | where should the backup go to? | 17:10:57 |
| Nico | Pushing backups from the forum machine to the matrix one and vice versa doesn't help a lot when they're both in the same data center, I guess. | 17:11:16 |
| Mathijs | (actually, that reminds me that I should backup my own synapse db) | 17:11:21 |
| Nico | In reply to @mathijs:matrix.vgorcum.com
I'd be inclined to script stopping synapse, dumping the database and backing up and starting synapse back up Sounds good. | 17:11:36 |
| Mathijs | In reply to @nico:dorfbrunnen.eu
Pushing backups from the forum machine to the matrix one and vice versa doesn't help a lot when they're both in the same data center, I guess. probably | 17:11:38 |
| Nico | In reply to @mathijs:matrix.vgorcum.com
where should the backup go to? For now, to some directory on that machine. Documented in the documentation. | 17:12:18 |
| Mathijs | I personally use duplicati and upload to stack | 17:12:20 |
| * Mathijs creates /backups folder | 17:12:38 |
| Mathijs | (or something) | 17:12:43 |
| Nico | Azure Stack? | 17:13:01 |
| Mathijs | In reply to @mathijs:matrix.vgorcum.com
probably actually, it is a little better than just backing up locally. If one VM falls over for some reason we'd still have the other for backups | 17:13:24 |
| Mathijs | In reply to @nico:dorfbrunnen.eu
Azure Stack? no, transip stack which gives me 1 TB of free storage | 17:14:03 |
