[Feature Request] Export option allowing importing all configured hosts #122
Comments
|
Have you tried the git vault functionality yet? That one tries to approach of syncing information between systems from a more modern angle. If the git integration does not fit your use case, I can think of also adding a normal export functionality. If you set a vault master passphrase in the settings, it does encrypt the sensitive information. That also applies to the information then stored in the git repository. |
|
I am looking at it now I think that will work. It's more involved for sure. At work we have SecureCRT. We have a master config file that has not only hosts and VMs but commands for troubleshooting our product in their layered button bar feature. I.e. if I am working on a subsystem of the product, I can select from a drop down and get all the relevant troubleshooting commands for that subsystem as buttons that will run those commands or scripts. As it gets updated we can import and merge it as needed. Not need to set up git, a git repo, a git server, etc... Especially in non commercial settings Hopefully something for future consideration. Thank you |
|
Interesting to hear about the actual work setups here. How exactly does the master config get shared in your case? Because I can see some problems here with importing and merging a config with multiple people working on it. That is why I went for using git as a platform, that solves many of these issues better. The git repository is initialized then managed automatically, the only thing you need is a remote git host somewhere. For example, you can create private repositories for free on GitHub, so I also use that for my connection configurations. |
|
Hello,
It's a feature of Secure CRT. The exported file is in XML format.
The master XML file is in a common location. As it gets updated, you can
import it quickly. If I have added entries they are not replaced.
re: Git. I do understand. But again it's just many more steps vs. export
to a file on a shared drive and import it. I have a github account I just
recently set up. I will have to try it out.
The button bar feature is amazing. You can organize into drop down tiers.
For support staff it's a time saver.
https://www.youtube.com/watch?v=qp82UWxGB8I
thank you
don
Don
…On Sun, Dec 24, 2023 at 2:31 PM Christopher Schnick < ***@***.***> wrote:
Interesting to hear about the actual work setups here. How exactly does
the master config get shared in your case? Because I can see some problems
here with importing and merging a config with multiple people working on
it. That is why I went for using git as a platform, that solves many of
these issues better.
The git repository is initialized then managed automatically, the only
thing you need is a remote git host somewhere. For example, you can create
private repositories for free on GitHub, so I also use that for my
connection configurations.
—
Reply to this email directly, view it on GitHub
<#122 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A6Z4V6TXN3KZF62FCKTRRC3YLB7IPAVCNFSM6AAAAABBBLH4MKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYGU4DCMJYGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
That button bar looks like a nice idea, maybe I can also implement that somehow. If you really want to use the shared drive, you can also change the vault location in the xpipe settings to be located somewhere on that share drive, and your information will be available anywhere you can access that shared drive from. It just gets a little bit complicated when multiple people access the shared data in parallel. It is not really an export functionality, so I can maybe think about adding something like this in some way. |
|
I will try that because I am having no luck getting github to work. I have
my SSH keys but it won't log in to github and I can't use password
authentication
In my case there is only myself so no worry about parallel access.
…On Sun, Dec 24, 2023 at 3:55 PM Christopher Schnick < ***@***.***> wrote:
That button bar looks like a nice idea, maybe I can also implement that
somehow.
If you really want to use the shared drive, you can also change the vault
location in the xpipe settings to be located somewhere on that share drive,
and your information will be available anywhere you can access that shared
drive from. It just gets a little bit complicated when multiple people
access the shared data in parallel.
It is not really an export functionality, so I can maybe think about
adding something like this in some way.
—
Reply to this email directly, view it on GitHub
<#122 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A6Z4V6TKLSGLJLNDBVTS77TYLCJEHAVCNFSM6AAAAABBBLH4MKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYGU4TEMJUGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Hm yeah when starting out you will frequently encounter some issues with remote GitHub repositories. Most of the times SSH keys not working is caused by using a HTTP git remote url instead of an SSH-based on that should have the form |
|
Well that didn't work too well. I can't copy the existing into the new
location? It's back to initial state, only the localhost is seen
On Sun, Dec 24, 2023 at 4:32 PM Donald Williams ***@***.***>
wrote:
… I will try that because I am having no luck getting github to work. I
have my SSH keys but it won't log in to github and I can't use password
authentication
In my case there is only myself so no worry about parallel access.
On Sun, Dec 24, 2023 at 3:55 PM Christopher Schnick <
***@***.***> wrote:
> That button bar looks like a nice idea, maybe I can also implement that
> somehow.
>
> If you really want to use the shared drive, you can also change the vault
> location in the xpipe settings to be located somewhere on that share drive,
> and your information will be available anywhere you can access that shared
> drive from. It just gets a little bit complicated when multiple people
> access the shared data in parallel.
>
> It is not really an export functionality, so I can maybe think about
> adding something like this in some way.
>
> —
> Reply to this email directly, view it on GitHub
> <#122 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A6Z4V6TKLSGLJLNDBVTS77TYLCJEHAVCNFSM6AAAAABBBLH4MKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYGU4TEMJUGA>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
Right now you would have to manually copy the data to the new directory when moving it. I could implement an optional dialog to also move the entire data as well though. Right now this functionality to change the directory is primarily there so people can switch between different configs. Assuming that you were using the default directory before, you can copy the contents of |
|
I created #128 for this |
|
I copied all the files in .xpipe
…On Sun, Dec 24, 2023 at 4:54 PM Christopher Schnick < ***@***.***> wrote:
I created #128 <#128> for this
—
Reply to this email directly, view it on GitHub
<#122 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A6Z4V6XNAGFT4IA6IY52HOLYLCQC5AVCNFSM6AAAAABBBLH4MKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYGU4TSNZTGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
OK so I didn't notice xpipe vs. xpipe-ptb but now all the saved settings
are gone on both Windows and Linux
I am back to square one
On Sun, Dec 24, 2023 at 5:05 PM Donald Williams ***@***.***>
wrote:
… I copied all the files in .xpipe
On Sun, Dec 24, 2023 at 4:54 PM Christopher Schnick <
***@***.***> wrote:
> I created #128 <#128> for this
>
> —
> Reply to this email directly, view it on GitHub
> <#122 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A6Z4V6XNAGFT4IA6IY52HOLYLCQC5AVCNFSM6AAAAABBBLH4MKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYGU4TSNZTGY>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
So if you are using the normal version and the PTB, they have different directories as you mentioned in .xpipe and .xpipe-ptb so they don't interfere. The settings and some other user data are always stored in The settings should not be shared as they contain platform specific information, only the storage directory. So if you change the vault directory in the settings menu, it should always refer to the storage directory, not the parent directory I should clarify that somewhere though, I can see how that is confusing. |
|
Thanks. Yeah I am not using both. I removed the normal when installed
the PTB
yeah so i am back to 0. oh well. I think I need to remove it all
clear the configs and start over.
that way I won't cause some weird issue later on
…On Sun, Dec 24, 2023 at 5:19 PM Christopher Schnick < ***@***.***> wrote:
So if you are using the normal version and the PTB, they have different
directories as you mentioned in .xpipe and .xpipe-ptb so they don't
interfere. The settings and some other user data are always stored in
<home>/.xpipe or <home>/.xpipe-ptb, they can't be moved. The only part
that can be moved is the connection configuration storage in
<home>/.xpipe/storage.
The settings should not be shared as they contain platform specific
information, only the storage directory. So if you change the vault
directory in the settings menu, it should always refer to the storage
directory, not the parent directory .xpipe itself.
I should clarify that somewhere though, I can see how that is confusing.
—
Reply to this email directly, view it on GitHub
<#122 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A6Z4V6SHEUIB7VYZSI7LV2LYLCS5VAVCNFSM6AAAAABBBLH4MKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYGYYDEOJRGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I'm sorry for the problems this has caused you, I will definitely use this as a motivation to make the process more robust. |
|
No worries! I don't have hundred of servers or vms. not a big deal. I
may set up my own GIT server Give that a try.
thanks for the replies and the support.
…On Sun, Dec 24, 2023 at 6:06 PM Christopher Schnick < ***@***.***> wrote:
I'm sorry for the problems this has caused you, I will definitely use this
as a motivation to make the process more robust.
—
Reply to this email directly, view it on GitHub
<#122 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A6Z4V6WN7V2A7HPCRHJNNDDYLCYRBAVCNFSM6AAAAABBBLH4MKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYGYYDQOJTGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
So I set up GITEA in a container and it's working with the 1st system.
Hopefully I can try it on the Windows system next.
don
On Sun, Dec 24, 2023 at 7:25 PM Donald Williams ***@***.***>
wrote:
… No worries! I don't have hundred of servers or vms. not a big deal. I
may set up my own GIT server Give that a try.
thanks for the replies and the support.
On Sun, Dec 24, 2023 at 6:06 PM Christopher Schnick <
***@***.***> wrote:
> I'm sorry for the problems this has caused you, I will definitely use
> this as a motivation to make the process more robust.
>
> —
> Reply to this email directly, view it on GitHub
> <#122 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A6Z4V6WN7V2A7HPCRHJNNDDYLCYRBAVCNFSM6AAAAABBBLH4MKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYGYYDQOJTGA>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
I am not sure if it's working as designed but only entries in the "Default' are stored to the GIT repository. The "All Connections" hosts are not imported from the GIT repo. I had to move all the connections to default first. I don't knwo how some were default and some were "all" Possibly the non default entries were the ones I cloned? |
|
If you click on the settings button on the category or right click it (i.e. the one's other than Default that you want to share), there should be an option to enable or disable sharing. This is so that you don't share everything automatically so you can also have private connections as well. |
|
Ahh great thanks.
…On Mon, Dec 25, 2023 at 9:11 AM Christopher Schnick < ***@***.***> wrote:
If you click on the settings entry on the category or right click it (i.e.
the one's other than Default that you want to share), there should be an
option to enable or disable sharing.
This is so that you don't share everything automatically so you can also
have private connections as well.
—
Reply to this email directly, view it on GitHub
<#122 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A6Z4V6WMY4H27A7LXKLJKRLYLGCRDAVCNFSM6AAAAABBBLH4MKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRZGAYDCNJZGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I guess we can close this? While having a normal export option would be simpler for a lot of people, this would introduce new problems and I would have to support git and the import/export functionality. I think going forward focusing on git is the better option. |
|
yes go ahead. Maybe something to consider later on.
thank you
…On Fri, Jan 5, 2024 at 5:55 AM Christopher Schnick ***@***.***> wrote:
Closed #122 <#122> as completed.
—
Reply to this email directly, view it on GitHub
<#122 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/A6Z4V6S6VLIZL755547XXKDYM7LYVAVCNFSM6AAAAABBBLH4MKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGQYDAMBQGI2DIMY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
With Putty for example I can copy the config files and easily add them or sync them between systems.
This would go a long way to making it easier to deploy at companies.
ideally the export file would be encrypted with a password
Thanks for this tool. I just started using it today at home.
The text was updated successfully, but these errors were encountered: