Giters

asbru-cm / asbru-cm

Ásbrú Connection Manager is a user interface that helps organizing remote terminal sessions and automating repetitive tasks.

Home Page:https://www.asbru-cm.net/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

using a shared directory for a team, need the $HOME variable

liprox opened this issue · comments

commented

Hi,

in addition to this issue:
"Operation not permitted" when using a shared directory (smb/cifs) as config-dir #909

Asbru-cm writes the absolute path to the home directory in the asbru.yml configuration file with the name of the user who is logged in.
For example for user mike:
First "mike" start asbru-cm, and starting from a samba share:
asbru-cm --config-dir=/srv/samba-share/asbru/

just now the pahtes are changing to /home/mike/ ...
For example:
... session logs folder: /home/mike/.config/asbru/session_logs ...
countless times, or per created connection, and:
log file: '/home/mike/.config/asbru/tmp/asbru_PID{10795}_n4.txt'

If I want to use asbru-cm in a team and together via a Samba share, it doesn't work perfect that way.

For me there are two maybe better solutions:
1: asbru.yml has to work with the username independent $HOME variable, or
2: automatically created user directories, directly created in the Samba share

EDIT:
But the way I see it now, it's not really a problem

regards,
liprox

commented

Thanks for suggestion, it would indeed be better to avoid absolute path that depends on the user in the configuration file.

Another way to fix this would be to make session log folder and log file relative to the configuration file.

Any comment or additional suggestion will be welcome.

commented

Hi @gfrenoy
In this case I think that it would be enough if the user has a way to select from where the configuration file should be loaded.
I consider it a bit secondary, but it might be useful (e.g- for audit purposes) if the session logs could be written to one shared directory as well, but that should be kept configurable from the user point of view unless the centrally managed Asbru configuration administrator locks it. In this last case, the session log file names should be changed to avoid collisions when two or more different users open a session to the same exact host at the same exact time. I'm not sure how prepared is the Asbru code to deal with read//write permissions or network latency effects when reading the configuration file from a remote location or writing the the session log files to a remote location, but this is something that would probably require some attention.
Cheers.

commented

I would to use asbru profile (or maybe only the connection file) on two different pcs, for example synchronizing the profile (file) with tools like syncthing or dropbox in a designated path. Could this use case fall in the previous of two different users? Or it's needed some other particular step ?

commented

HI,

We have been working with asbru-cm almost every day for about a year. Using the above setting and a shared network path. Our launch parameter on Debian, KDE (bullseye and bookworm):
env GDK_BACKEND=x11 asbru-cm --config-dir=/srv/share/asbru
We mainly work with ssh keys and enter the required password with only-key hardware tokens.
That's for us a very great and useful solution ...
As a Fan ;-) please do not forget:
https://liberapay.com/asbru-cm/donate

regards