cyclane/kovalhome
1
1
Fork 0
Code Issues 7 Pull Requests 1 Actions Packages Projects 3 Releases Activity

Mailcow VM #34

New Issue
Open
opened 2024-01-23 12:58:02 +00:00 by cyclane · 0 comments
cyclane commented 2024-01-23 12:58:02 +00:00
Owner
Copy Link

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.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Kind/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Spike
Research issues and pull requests
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Kind/Feature
Priority
Medium
Milestone
No items
No Milestone
Projects
Clear projects
No project Migrations
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cyclane/kovalhome#34
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?