Mailcow VM #34

New Issue

cyclane · 2024-01-23T12:58:02Z

cyclane commented

2024-01-23 12:58:02 +00:00

So, Mailcow is currently on a legacy alpine docker container.

Unfortunately, Mailccow doesn't have amazing support for unattended upgrades. So we want to migrate mailcow to a (non-docker) debian container and leave it at that.

Why not debian-docker?

I think I'm going to deprecate this template too in favour of knowing exactly what changes have been applied to a template. In the future we could provision this template with ansible, but considering manually-managed services should be the exception rather than the rule, I think it's fine if we don't.

Provisioning

We can still provision infrastructure and base software (docker) with ansible, just mailcow itself needs to be migrated & managed manually. So I guess this will be a "partially managed" service.

So, Mailcow is currently on a legacy alpine docker container. Unfortunately, Mailccow doesn't have amazing support for unattended upgrades. So we want to migrate mailcow to a (non-docker) debian container and leave it at that. ### Why not debian-docker? I think I'm going to deprecate this template too in favour of knowing exactly what changes have been applied to a template. In the future we _could_ provision this template with ansible, but considering manually-managed services should be the exception rather than the rule, I think it's fine if we don't. ### Provisioning We can still provision infrastructure and base software (docker) with ansible, just mailcow itself needs to be migrated & managed manually. So I guess this will be a "partially managed" service.

cyclane added the

Kind/Feature

Priority

Medium

labels 2024-01-23 12:58:02 +00:00

cyclane added this to the Migrations project 2024-01-23 12:58:03 +00:00

cyclane changed title from ~~Mailcow~~ to Mailcow VM

2024-01-23 12:58:10 +00:00

Sign in to join this conversation.