So I worked on this over the last couple of days and fixed several performance issues in the latest 15.4 release, especially when it comes to handling many added connections like in your case. Feel free to try it again, it should handle better now.

So I worked on this over the last couple of days and fixed several performance issues in the latest 15.4 release, especially when it comes to handling many added connections. Feel free to try it again, it should handle better now.

So I worked on the performance over the last couple of days. There were some regressions that I discovered. This should be fixed now in the latest 15.4 release.

I think it’s mainly bad optimization on my part. I will work on that for the next release as best as I can. So hopefully I can fix your issues somewhat until then

Thanks for the info, I see the issue with that many host entries. I will fix that for the next release

The only possibility I see here is that this is a Windows 10 system with an older SSHD if mobaxterm doesn’t work anymore as there were some changes on which SSHD executable XPipe will use for mobaxterm.

About the X11, I am not aware of any changes that could change that behaviour. If no parent connection of the LXC container has that explicitly enabled, it shouldn’t use that.

For both issues, feel free to post on GitHub and Discord and I can help troubleshoot this

You can go to Settings -> Troubleshoot and either take a look at the log files or launch it in debug mode. If you find anything, feel free to post on GitHub or Discord

When you say slow, what part do you refer to? I am always looking to improve on the performance front

I am a bit confused by the feedback on the performance here. Now the performance wasn’t that great previously, but that should have been fixed over time, especially in the latest updates.

Maybe I am missing something when testing. So if you want, feel free to elaborate on where the performance issues occur, I can look into that.

What system did you try it on? I can look into it

Alright, feel free to let me know how it compares to your other tools that you use. That is always a valuable insight for me

Yes, you can use any local editor to edit your remote files

Alright, thanks for your insights from an outsider. It is always a difficult task to accurately judge your own projects if you’re intimately familiar with it. So I will see what I can do about the things you mentioned

Alright, I see your points.

Now that you have spent a lot of time discussing it, even looking at the code, one thing that would be valuable for me would be how accurate your expectations are based on what you read here compared to the actual app. If it is pretty much as expected, then I guess at least my summaries are accurate. If it’s not, then I can still do a better job at that part. Fundamentally changing the project itself is a little bit too late, but at least the communication can be changed on why people could use it. And I’m not trying to gain a new user here as it’s probably not for you, but still would be interesting to me. You can give it five minutes and use the .tar.gz or the .appimage if you don’t want to install anything.

Thanks for taking your time to write this.

I think the main point I’m trying to figure out here is whether this is a communications issue, i.e. how I describe it is not optimal or whether this is a fundamental project issue. Because I think I have a clear vision and target audience, I am part of that audience myself. The thing is, there isn’t one standout feature. The value comes from the combination and integrations of multiple features that work together and allow for a smooth use experience. I can say it has support for SSH, docker, kubernetes, hypervisors, and more but all of that on an individual layer isn’t that unique, it’s the combination that you can use all of them together. But this is difficult to put into words, trying it out for yourself for a few minute usually yields better results.

About the shell commands, that is one of the standout features about it, so it’s on purpose. I know this approach is more difficult and error prone than doing some kind of native library stuff, but it also allows me to run the same commands in remote shells on remote systems.

Yeah I am still trying to figure out how to explain it the best way to convince people to give it a try

For normal SSH this is all accurate, maybe I should have focused on wider topics.

Staying in the realm of SSH, where the integrations of XPipe produce added value is for example when it comes to virtual machines. If you quickly spin up a VM in a hypervisor such as Proxmox or KVM, it’s not that straightforward anymore. If you want to reach a VM running on a remote hypervisor host, you probably have to first use the hypervisor host as a jump server to be able to access the VM and the first place. You have to determine the external IP of the VM (which might be frequently changing), check if any kind of guest agents are available, check whether an SSH server is running (and start it in the VM shell if not). And only then you can type ssh user@host to that VM. XPipe will do that all automatically. So from your perspective, you only click on it and it will perform all these tedious tasks in the background and boot you into a terminal session.

The open core version provides almost all features in the community edition. It is not completely there yet, because in practice some components are difficult to separate or to include in the source since everything is in the same build. E.g. the whole licensing code is present in the community build as you can upgrade the license in-place, but that code is not part of the public source code and in a completely standalone build, this part is still required.

So it’s currently not fully possible to release the core component as is alone, but if you clone it and run in your own development environment, any components that are not included but required are fetched from an existing xpipe installation on that system. So cloning the community repository and running the dev build works fine.

I wouldn’t really say that though. It is aimed to make the whole process require less typing, make it more ergonomic, require less thinking, and speed it up a bit compared to if you’re doing it manually. There are plenty of expert options that you can use to fully customize your connections and your workflow.

Among the active users, there are many experienced professionals who use it because it makes their life easier.

Yeah most of the things listed can be done with any command-line SSH client, XPipe aims to improve the user experience for these tasks and also make them faster / take less time typing. I would argue you can save quite a bit of time if you use it correctly. And there is support for more than just plain SSH.

I would just recommend you to try it out for like 5 minutes. If you still don’t see the point of it, you can just uninstall it and move on