XPipe - A connection hub for all your servers: Status update for the v16 release
from crschnick@sh.itjust.works to selfhosted@lemmy.world on 26 Jun 00:00
https://sh.itjust.works/post/40972139

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.

Hub

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 container state information shown is also improved, always showing the container state in combination with the system information.

Compose

Batch mode

There is now a batch mode available that allows you to select multiple systems via checkboxes and perform actions for the entire batch. This can include starting/stopping, automatically adding available subconnections, or running scripts on all selected systems.

You can toggle the batch mode in the top left corner.

Batch

Password managers

The password manager integrations have been upgraded:

Password Manager

Terminals

The terminal integration comes with many new features:

SSH

Various improvements were made to the SSH implementation:

Other

A note on the open-source model

Since it has come up a few times, in addition to the note in the git repository, I would like to clarify that XPipe is not fully FOSS software. The core that you can find on GitHub is Apache 2.0 licensed, but the distribution you download ships with closed-source extensions. There’s also a licensing system in place with limitations on what kind of systems you can connect to in the community edition as I am trying to make a living out of this. I understand that this is a deal-breaker for some, so I wanted to give a heads-up.

Outlook

If this project sounds interesting to you, you can check it out on GitHub, visit the Website, or check out the Docs for more information.

Enjoy!

#selfhosted

threaded - newest

savvywolf@pawb.social on 26 Jun 00:43 next collapse

Had a quick look through your website and something jumped out at me (about the enterprise edition, I assume that the community edition doesn’t have this clause):

There is not a hard limit for activations per license as we understand the need to run XPipe on many machines per user. There is instead a soft activation/usage limit that is tracked for the license key and uses common usage patterns as a reference.

I may be missing something obvious (it’s a hobby of mine), but I can’t seem to find anywhere what exactly these soft limits are.

crschnick@sh.itjust.works on 26 Jun 01:10 collapse

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.

muntedcrocodile@hilariouschaos.com on 26 Jun 01:35 next collapse

Would be cool if u could launch vscode remote as well as a terminal

ruud@lemmy.world on 26 Jun 05:23 next collapse

This looks very nice. A question, we use Teleport, and it does discover all hosts. But when connecting, I need to configure the username for every host separately. Can’t I set a default somewhere?

crschnick@sh.itjust.works on 26 Jun 06:24 collapse

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

irmadlad@lemmy.world on 26 Jun 14:34 next collapse

There’s also a licensing system in place with limitations on what kind of systems you can connect to in the community edition as I am trying to make a living out of this. I understand that this is a deal-breaker for some, so I wanted to give a heads-up.

Make yo’ paper bro. I have no issue with that.

punkibas@lemmy.zip on 26 Jun 16:48 collapse

I’ve been using this for a while now, that docker compose integration is gonna be a welcome addition, keep up the good work!