Add command to move an app to a different server #586

New Issue

p4u1 · 2025-08-11T10:19:38Z

p4u1 commented

2025-08-11 10:19:38 +00:00

It should be simple and easy to move an app from one server to another.
The command should use the existing backup / restore infrastructure where possible.

Cli interface:

abra app move <domain> <server>

Internal steps when moving app1 from serverA to serverB:

undeploy app1 from serverA (to ensure no new data is added while moving the app)
copy volumes and secrets from serverA to serverB
deploy app1 to serverB

It should be simple and easy to move an app from one server to another. The command should use the existing backup / restore infrastructure where possible. Cli interface: ``` abra app move <domain> <server> ``` Internal steps when moving app1 from serverA to serverB: - undeploy app1 from serverA (to ensure no new data is added while moving the app) - copy volumes and secrets from serverA to serverB - deploy app1 to serverB

❤️ 3

p4u1 added the

enhancement

label 2025-08-11 10:19:38 +00:00

decentral1se commented

2025-08-11 12:52:01 +00:00

I can understand the need for this and also I've ran into this multiple times. We used to always try to put these kind of features into abra but at some point we realised it's very hard to maintain. This seems like one of those features. There are many devils in many of these details for this implementation. I would like to see a more concrete proposal for how this will work with the multiple use cases before an implementation arrives. I would have a preference to not support abra app move if not using backup-bot-two to focus on one workflow? I'm not sure, I'd have to see more details. Thanks for opening!

I can understand the need for this and also I've ran into this multiple times. We used to always try to put these kind of features into `abra` but at some point we realised it's very hard to maintain. This seems like one of those features. There are many devils in many of these details for this implementation. I would like to see a more concrete proposal for how this will work with the multiple use cases before an implementation arrives. I would have a preference to not support `abra app move` if not using `backup-bot-two` to focus on one workflow? I'm not sure, I'd have to see more details. Thanks for opening!

p4u1 commented

2025-08-11 14:13:28 +00:00

@decentral1se I understand the hesitation for adding this feature, but I would argue, that this should be a core feature, because I guess many have the same problem, as coopcloud is centered around having multiple servers that are seperated from each other.

Let me think some more about a concrete implementation proposal

@decentral1se I understand the hesitation for adding this feature, but I would argue, that this should be a core feature, because I guess many have the same problem, as coopcloud is centered around having multiple servers that are seperated from each other. Let me think some more about a concrete implementation proposal

👍 1

p4u1 commented

2025-08-12 15:44:29 +00:00

I'm interested in how others do this currently!
@3wordchant @decentral1se @moritz and others :)

I'm interested in how others do this currently! @3wordchant @decentral1se @moritz and others :)

p4u1 referenced this issue

2025-08-18 12:34:09 +00:00

feat: Adds abra app move #605

decentral1se added this to the Abra "next" project 2025-08-25 10:55:53 +00:00

decentral1se moved this to In Progress in Abra "next" on 2025-08-25 10:56:06 +00:00

p4u1 was assigned by decentral1se

2025-08-27 14:01:30 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/abra#586