Move command improvements #697

New Issue

ammaratef45 · 2025-10-15T23:48:23Z

ammaratef45 commented

2025-10-15 23:48:23 +00:00

Finally got to test the command and here are some improvements I would suggest

Add `rm` as a shorthand for the command

A low hanging fruit but could be nice since I'm used to move and mv to be synonyms.

If secrets already exist as part of previously failed move, prompt for keeping them, deleting and replacing them, or aborting

Having to redeploy the app before trying again was enough headache, having to do that one more time because I forgot to clean up secrets was a bit much imo

Check if the user running the command has passwordless sudo enabled, warn them if not

The tar command is not running interactively, either we do that or use some trick to figure out if the user is allowed to run sudo without being prompted for a password and prompt them to do so if not the case

Server renaming

So I was moving the app between ips rather than between domains, I had to change my ssh config and dns records then run server add again on the old server after renaming its directory

Here are the steps for a little clarity:
1- change server's directory name under ~/.abra/servers from server.example to old.server.example
2- add .ssh/config entries for the new server and update the entry for the old one
3- run abra server add old.server.example to update the docker metadata
4- run abra server add server.example to add the new server with the old domain

Finally got to test the command and here are some improvements I would suggest # Add `rm` as a shorthand for the command A low hanging fruit but could be nice since I'm used to `move` and `mv` to be synonyms. # If secrets already exist as part of previously failed move, prompt for keeping them, deleting and replacing them, or aborting Having to redeploy the app before trying again was enough headache, having to do that one more time because I forgot to clean up secrets was a bit much imo # Check if the user running the command has passwordless sudo enabled, warn them if not The tar command is not running interactively, either we do that or use some trick to figure out if the user is allowed to run sudo without being prompted for a password and prompt them to do so if not the case # Server renaming So I was moving the app between ips rather than between domains, I had to change my ssh config and dns records then run server add again on the old server after renaming its directory Here are the steps for a little clarity: 1- change server's directory name under `~/.abra/servers` from `server.example` to `old.server.example` 2- add `.ssh/config` entries for the new server and update the entry for the old one 3- run `abra server add old.server.example` to update the docker metadata 4- run `abra server add server.example` to add the new server with the old domain

🚀 1

decentral1se added the

enhancement

label 2025-10-17 17:42:50 +00:00

decentral1se commented

2025-11-02 10:50:07 +00:00

#709

https://git.coopcloud.tech/toolshed/abra/pulls/709

❤️ 1

Sign in to join this conversation.