github.com GitHub - xpipe-io/xpipe: Your entire server infrastructure at your fingertips
Your entire server infrastructure at your fingertips - xpipe-io/xpipe
Posts
21
Comments
112
Joined
2 yr. ago
Nope, an application like this can't work as a flatpak as the sandbox prevents almost all shell functionality and makes the application unusable. Yes, the AppImages are basically the best solution for immutable operating systems.
I think in the end you still have to exercise some trust. There are things like audits, but these are costly and not an option in the current stage. Maybe in the future. Best I can do is to provide transparency by open-sourcing large parts of the codebase and providing detailed security information like https://docs.xpipe.io/reference/security.
As someone who sometimes sells to the german public sector, it is true that they would prefer a good open source solution if it was available. But me being a german vendor makes up for it, as they still prefer this a lot more over any US-based vendors.
In general about the key handling, XPipe doesn't read any kind of keys itself, it only forwards them to the local OpenSSH client. It is essentially a wrapper around in existing ssh client, and doesn't implement anything related to key handling itself.
I think if you have a specialized tools with openstack, XPipe probably can't compete with that in that area. But it can make your life easier in a lot of other areas and common tasks when it comes to accessing many servers.
About the FOSS requirement, I know that this is a dealbreaker for some. That is a tradeoff when going the commercial route
Right now, you have to set the user separately. But I will think about fixing this for next release, there already is a way to configure a default identity for new connections, but it does not apply to teleport yet
Yes, the community edition doesn't have any limitation.
For paid plans, it's relative to the average usage and activations across all licenses. E.g. if you, as an enterprise, purchase licenses for 5 users, but have a usage like other customers with 20 users, I might inquire about how you are using it. If it is a special case where you install and use it on many servers and VMs in parallel, this can be taken into account and the limits can be adapted. But in general, the license limits are permissive and do not interfere with your usage.
XPipe - A connection hub for all your servers: Status update for the v16 release
Today I can share a major development status update of XPipe, a connection hub that allows you to access your entire server infrastructure from your local desktop. It can make your life easier when working with any kind of servers by eliminating all the commonly tedious tasks that come up when interacting with remote systems, either from the terminal or from a graphical interface. XPipe comes with integrations for SSH, docker and other containers, various hypervisors, and more without requiring setup on your remote systems. You can also keep using your favourite text/code editors, terminals, password managers, shells, command-line tools, and more with it.
Docker compose
This release introduces support for docker compose. Containers in compose projects are grouped together and can be managed
XPipe - A connection hub for all your servers: Status update for the v16 release
Today I can share a major development status update of XPipe, a connection hub that allows you to access your entire server infrastructure from your local desktop. It can make your life easier when working with any kind of servers by eliminating all the commonly tedious tasks that come up when interacting with remote systems, either from the terminal or from a graphical interface. XPipe comes with integrations for SSH, docker and other containers, various hypervisors, and more without requiring setup on your remote systems. You can also keep using your favourite text/code editors, terminals, password managers, shells, command-line tools, and more with it.
Docker compose
This release introduces support for docker compose. Containers in compose projects are grouped together and can be managed all at the same time via compose project entries.
The containe
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
XPipe - A connection hub for all your servers: Status update for the v15 release
XPipe - A connection hub for all your servers: Status update for the v15 release
Today I can share a major development status update of XPipe, a new connection hub that allows you to access your entire server infrastructure from your local desktop. It can make your life easier when working with any kind of servers by eliminating all the commonly tedious tasks that come up when interacting with remote systems, either from the terminal or from a graphical interface. XPipe comes with integrations for SSH, docker and other containers, various hypervisors, and more without requiring setup on your remote systems. You can also keep using your favourite text/code editors, terminals, password managers, shells, command-line tools, and more with it.
Tailscale SSH support
You can now connect to devices in your tailnet via Tailscale SSH and your locally installed ta
XPipe - A connection hub for all your servers: Status update for the v15 release
Today I can share a major development status update of XPipe, a new connection hub that allows you to access your entire server infrastructure from your local desktop. It can make your life easier when working with any kind of servers by eliminating all the commonly tedious tasks that come up when interacting with remote systems, either from the terminal or from a graphical interface. XPipe comes with integrations for SSH, docker and other containers, various hypervisors, and more without requiring setup on your remote systems. You can also keep using your favourite text/code editors, terminals, password managers, shells, command-line tools, and more with it.
Tailscale SSH support
You can now connect to devices in your tailnet via Tailscale SSH and your locally installed tailscale command-l
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.
XPipe - A connection hub for all your servers: Status update for the v14 release
I'm proud to share a major development status update of XPipe, a new connection hub that allows you to access your entire server infrastructure from your local desktop. XPipe 14 is the biggest rework so far and provides an improved user experience, better team features, performance and memory improvements, and fixes to many existing bugs and limitations.
If you haven't seen it before, XPipe works on top of your installed command-line programs and does not require any setup on your remote systems. It integrates with your tools such as your favourite text/code editors, terminals, shells, command-line tools and more. Here is what it looks like:
XPipe - A connection hub for all your servers: Status update for the v14 release
I'm proud to share a major development status update of XPipe, a new connection hub that allows you to access your entire server infrastructure from your local desktop. XPipe 14 is the biggest rework so far and provides an improved user experience, better team features, performance and memory improvements, and fixes to many existing bugs and limitations.
If you haven't seen it before, XPipe works on top of your installed command-line programs and does not require any setup on your remote systems. It integrates with your tools such as your favourite text/code editors, terminals, shells, command-line tools and more. Here is what it looks like:
Reusable identities + Team vaults
You can now create reusable identities for connections instead of having to enter aut
XPipe - A connection hub for all your servers: Status update for the v13 release
I'm proud to share a major development status update of XPipe, a new connection hub that allows you to access your entire server infrastructure from your local desktop. It works on top of your installed command-line programs and does not require any setup on your remote systems. XPipe integrates with your tools such as your favourite text/code editors, terminals, shells, command-line tools and more.
Here is how it looks like if you haven't seen it before:
VMs
- There is now support for KVM/QEMU virtual machines that can be accessed via the libvirt CLI tools
virsh. This includes support for other driver URLs as well aside from KVM and QEMU. This integration is available starting from the homelab plan and can be used for free for two weeks after this release using
XPipe - A connection hub for all your servers: Status update for the v13 release
I'm proud to share a major development status update of XPipe, a new connection hub that allows you to access your entire server infrastructure from your local desktop. It works on top of your installed command-line programs and does not require any setup on your remote systems. XPipe integrates with your tools such as your favourite text/code editors, terminals, shells, command-line tools and more.
Here is how it looks like if you haven't seen it before:
VMs
- There is now support for KVM/QEMU virtual machines that can be accessed via the libvirt CLI tools
virsh. This includes support for other driver URLs as well aside from KVM and QEMU. This integration is available starting from the homelab plan and can be used for free for two weeks after this release using the new release preview - You can now override a VM IP if you're using an advanced networking se
XPipe - A connection hub for all your servers - Status update for the v12 release - Now with selfhst icons!
I'm proud to share a major development status update of XPipe, a new connection hub that allows you to access your entire server infrastructure from your local desktop. It works on top of your installed command-line programs and does not require any setup on your remote systems. XPipe integrates with your tools such as your favourite text/code editors, terminals, shells, command-line tools and more.
Here is how it looks like if you haven't seen it before:
Icons
A big new feature, which is probably going to be interesting for the selfhosted crowd here, is the addition of custom icons for services. A huge shoutout to https://github.com/selfhst/icons, without them this would have not been possible. Essentially, you can now set icons for any connection to better organize individual ones. For example, if you connect to an opnsense or immich system, you can now mar
XPipe - A connection hub for all your servers - Status update for the v11 release
I'm proud to share a major development status update of XPipe, a new connection hub that allows you to access your entire server infrastructure from your local desktop. It works on top of your installed command-line programs and does not require any setup on your remote systems. XPipe integrates with your tools such as your favourite text/code editors, terminals, shells, command-line tools and more.
Here is how it looks like if you haven't seen it before:
More terminal integrations
There is now support to use the following terminals:
- Termius
- MobaXterm
- Xshell
- SecureCRT
These work via a local SSH bridge that is managed by XPipe. That way you can keep using your existing SSH terminal solution with the added functionality of XPipe.
Pricing model updates
I received plenty of user feedback, so I changed the
XPipe 10 comes with web service port-forwarding, markdown notes, better proxmox support, a new HTTP API, and more
I'm proud to share a major development status update of XPipe, a new connection hub that allows you to access your entire server infrastructure from your local desktop. It works on top of your installed command-line programs and does not require any setup on your remote systems. So if you normally use CLI tools like ssh, docker, kubectl, etc. to connect to your servers, it will automatically integrate with them.
Here is how it looks like if you haven't seen it before:
Local forwarding for services
Many systems run a variety of different services such as web services and others. There is now support to detect, forward, and open the services. For example, if you are running a web service on a remote container, you can automatically forward the service port via SSH tunnels, allowing you to access these services from
XPipe 10 comes with web service port-forwarding, markdown notes, better proxmox support, a new HTTP API, and more
I'm proud to share a major development status update of XPipe, a new connection hub that allows you to access your entire server infrastructure from your local desktop. It works on top of your installed command-line programs and does not require any setup on your remote systems. So if you normally use CLI tools like ssh, docker, kubectl, etc. to connect to your servers, it will automatically integrate with them.
Here is how it looks like if you haven't seen it before:
Local forwarding for services
Many systems run a variety of different services such as web services and others. There is now support to detect, forward, and open the services. For example, if you are running a web service on a remote container, you can automatically forward the service port via SSH tunnels, allowing you to access these services from
XPipe 9 comes with VNC, RDP, and SSH X11 support, a better SSH integration, terminal improvements, and many bug fixes
Hello there,
I'm proud to share a major development status update of XPipe, a connection hub and remote file manager that allows you to access your entire server infrastructure from your local machine. It works on top of your installed command-line programs and does not require any setup on your remote systems. So if you normally use CLI tools like ssh, docker, kubectl, etc. to connect to your servers, you can just use XPipe on top of that.
Here is how it looks like if you haven't seen it before:
Coherent desktops
XPipe now comes with support for remote desktop connections. VNC connections are fully handled over SSH and can therefore be established on top of any existing SSH connection you have
XPipe 9 comes with VNC, RDP, and SSH X11 support, a better SSH integration, terminal improvements, and many bug fixes
Hello there,
I'm proud to share a major development status update of XPipe, a connection hub and remote file manager that allows you to access your entire server infrastructure from your local machine. It works on top of your installed command-line programs and does not require any setup on your remote systems. So if you normally use CLI tools like ssh, docker, kubectl, etc. to connect to your servers, you can just use XPipe on top of that.
Here is how it looks like if you haven't seen it before:
Coherent desktops
XPipe now comes with support for remote desktop connections. VNC connections are fully handled over SSH and can therefore be established on top of any existing SSH connection you have
XPipe status update: A new fast terminal launcher, a better file browser, performance improvements, and many bug fixes
I'm proud to share a development status update of XPipe, a shell connection hub and remote file manager that allows you to access your entire server infrastructure from your local machine. It works on top of your installed command-line programs and does not require any setup on your remote systems. So if you normally use CLI tools like ssh, docker, kubectl, etc. to connect to your servers, you can just use XPipe on top of that.
Here is how it looks like if you haven't seen it before:
Since the last status update some months ago, a lot of things have changed thanks to the community sharing a lot of feedback and reporting issues. Overall, the project is now in a much more stable state as all the accumulated issues have been fixed. Furthermore, many feature requests have been implemented.
XPipe 8 is this biggest upda
XPipe status update: A new fast terminal launcher, a better file browser, performance improvements, and many bug fixes
I'm proud to share a development status update of XPipe, a shell connection hub and remote file manager that allows you to access your entire server infrastructure from your local machine. It works on top of your installed command-line programs and does not require any setup on your remote systems. So if you normally use CLI tools like ssh, docker, kubectl, etc. to connect to your servers, you can just use XPipe on top of that.
Here is how it looks like if you haven't seen it before:
Since the last status update some months ago, a lot of things have changed thanks to the community sharing a lot of feedback and reporting issues. Overall, the project is now in a much more stable state as all the accumulated issues have been fixed. Furthermore, many feature requests have been implemented.
XPipe 8 is this biggest upda
XPipe status update: New scripting system, advanced SSH support, performance improvements, and many bug fixes
I'm proud to share a status update of XPipe, a shell connection hub and remote file manager that allows you to access your entire server infrastructure from your local machine. It works on top of your installed command-line programs and does not require any setup on your remote systems. So if you normally use CLI tools like ssh, docker, kubectl, etc. to connect to your servers, you can just use XPipe on top of that.
Since the last status update some months ago, a lot of things have changed thanks to the community sharing a lot of feedback and reporting issues. Overall, the project is now in a much more stable state as all the accumulated issues have been fixed. Furthermore, many feature requests have been implemented.
Large connection sets
A lot of work went into improving the application for large use cases when you're managing hundreds of connections. This includes hierarchical organization feat
XPipe status update: New scripting system, advanced SSH support, performance improvements, and many bug fixes
I'm proud to share a status update of XPipe, a shell connection hub and remote file manager that allows you to access your entire server infrastructure from your local machine. It works on top of your installed command-line programs and does not require any setup on your remote systems. So if you normally use CLI tools like ssh, docker, kubectl, etc. to connect to your servers, you can just use XPipe on top of that.
Since the last status update some months ago, a lot of things have changed thanks to the community sharing a lot of feedback and reporting issues. Overall, the project is now in a much more stable state as all the accumulated issues have been fixed. Furthermore, many feature requests have been implemented.
Large connection sets
A lot of work went into improving the application for large use cases when you're managing hundreds of connections. This includes hierarchical organization feat
Status update for XPipe, a new type of shell connection hub and remote file manager
Hello Linux community,
I'm proud to present to you XPipe, a new type of shell connection hub and remote file manager that allows you to access your entire sever infrastructure from your local machine through your installed command-line programs. This approach makes it much more flexible as it doesn't have to deal with file system APIs, protocols, or libraries at all, everything is delegated to your own CLI tools. So if you normally use CLI tools like ssh, docker, kubectl, etc. to connect to your servers, you can just use XPipe on top of that without any set up required on your servers.
Since the first announcement around one month ago, a lot of things have changed thanks to the community sharing a lot of feedback and reporting issues. Overall, the project is now in a much more stable state as all the accumulated issues have been fixed. Furthermore, many feature requests have been implemented. This inclu
XPipe status update: SSH tunnel and config support, many new features, and lots of bug fixes
Hello selfhosted community,
I just wanted to give you a short update on XPipe, a new type of shell connection hub and remote file manager that allows you to access your entire sever infrastructure from your local machine through your installed command-line programs.
Since I last posted about it here around one month ago, a lot of things have changed thanks to the community sharing a lot of feedback and reporting issues. Overall, the project is now in a much more stable state as all the accumulated issues have been fixed. Furthermore, many feature requests have been implemented. This includes for example:
- SSH tunnel support (Local, Remote, and Dynamic)
- Automatic import from your SSH configs
- Podman support
- Support for other Linux environments on Windows such as Cygwin or MSYS2
- Fish support
- Support for more terminals and editors such as Alacritty, Kitty, and more
Here are some screenshots:
![Conne