Your entire server infrastructure at your fingertips
APACHE-2.0 License
Bot releases are visible (Hide)
Published by crschnick 8 months ago
One common feedback that some users shared was that it could be quite cumbersome to access a specific nested connection as one would have to possibly expand several connections first. Expanded connections would then also take up a lot of space, leading to a lot of scrolling.
There is now a quick access button available for connections that enables you to quickly choose a connection in the hierarchy without having to expand any connection views.
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "8.2"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 8.2
Automated VirusTotal analysis of all artifacts:
Published by crschnick 8 months ago
The last few versions of XPipe from 1.7.16 to 8.0.1 all had a self-updater on Windows that was not working properly. This was caused by a newly introduced JDK bug. This is now fixed from 8.1 onwards.
To upgrade to 8.1+, you have to do it manually by downloading and installing it from https://github.com/xpipe-io/xpipe/releases. There shouldn't be any more problems with 8.1+ after that.
When upgrading XPipe versions across many systems, one problem could have been the git vault format being updated on one system and being pulled on another a system that is running an older version. This could have led to data corruption. From now on, there will be a warning shown when the versions do not match up. From there you can choose to temporarily disable the git vault during a session until you upgrade to the matching version on that system as well.
This check however only works from 8.1 onwards. Older git vaults do not contain version information. So if this happens to you while updating from a previous version, e.g. 1.7.16, you should be able to reset the git repository to a previous ref.
You can now search for IPs and hostnames in addition to the connection names to filter your connection list. The connection display when a filter is active has also been improved.
There was a regression in transfer speed in 8.0 causing transfers of large files being very slow. This is now fixed.
There is now a new action available in the file browser for directories on Windows systems that allows you to open that directory in a WSL session. This makes it easier to quickly use Linux tools in a certain directory you're currently in when on Windows.
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "8.1"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 8.1
Automated VirusTotal analysis of all artifacts:
Published by crschnick 8 months ago
This is this biggest update yet and includes many changes that are necessary going forward to allow for many future features to come. These new implementations take everything into account learned so far and are more intuitive and robust. Especially when considering the long-term timeline, these changes will come in handy.
The versioning scheme has also been changed to simplify version numbers. So we are going straight from 1.7 to 8.0!
Note that on Windows the automatic updater still has a few issues with race conditions if you are upgrading from 1.7.16. If the automatic update fails, you can still install 8.0 manually by downloading and installing it from https://github.com/xpipe-io/xpipe/releases.
The terminal launcher functionality got completely reworked with the goal to make it more flexible and improve the terminal startup performance. You will quickly notice the new implementation whenever you launch any connection in your terminal.
There is now support to directly query all VMs and containers located on a Proxmox system via the pct
and qm
tools. The containers can be accessed directly as any other containers while the VMs can be accessed via SSH. In case no SSH server is running in a vm, you can also choose to start one with XPipe.
This feature will be available in the professional version, but is also available in the free professional edition preview after release.
Any new professional features, such as the Proxmox support, will be available for free for a couple of weeks after their initial release. There is now a new dialog available to allow you to quickly set up the XPipe professional preview plan.
This allows anyone interested in playing around with new features to do so without limitation and no commitment.
The git installation on Windows comes with its own posix environment, which some people use to make use of standard Linux functionalities on Windows if they have not moved to WSL yet. This update brings full support to add this shell environment as well via the automatic detection functionality.
The file browser has been reworked in terms of performance and reliability. File transfers of many files or now faster and any errors that can occur are now handled better.
In terms of the interface, there is also now a progress indicator for files being transferred. For any file conflicts, there is now a new dialog to choose how to resolve any conflict when copying or moving files.
There are also a couple more changes included:
This update adds support to also add connections from other kubeconfig files.
Furthermore, you can also choose to use any namespace you want. This is useful in cases where you have not set up a context for every namespace you have.
The Kubernetes support is also now available in the pro preview after release.
This update comes with a complete rework of the settings menu. Many options have been added and existing ones have been improved, with a focus on providing more control over security settings. Make sure to give them a read to discover new options.
There has been a big focus on providing finer-grained control over security settings, which can be especially useful in enterprise contexts.
Previously all settings were stored on a per-system basis. This caused some problems with git vaults, as all relevant settings that should persist across systems were not synced. From now on, all options that should be the same on all synced systems are automatically included in the git vault.
This update comes with a newly created system for handling authentication that is better suited for arbitrary authentication prompts. This allows for better support for things like 2FA and other keyboard interactive authentications schemes. The sudo elevation authentication also has been reworked to be more intuitive and mirror the behavior of the system in regard to password prompts.
You also now have finer control over the caching behaviour of passwords and the sudo behaviour via additional settings.
You can now run a temporary docker container using a specified image that will get automatically removed once it is stopped. The container will keep running even if the image does not have any command specified that will run.
This can be useful if you quickly want to set up a certain environment by using a certain container image, e.g. a simple ubuntu
image. You can then enter the container as normal in XPipe, perform your operations, and stop the container once it's no longer needed. It is then removed automatically.
Up until now, connecting to fish shells or various dumb shells you typically find in devices like routers and links, did not work as there was no proper support for them. The shell handling implementation has now been rewritten to support fish login shells (after some timeout).
The implementation also now supports dumb shells that can be reached via ssh for example, but support still has to be implemented manually. Since I currently don't own any typical hardware like various routers and links, e.g. from cisco, I did not have the ability yet to do this. So if you own any hardware you would like to see supported, open an issue and share the typical output that is printed upon connection, and it can easily be supported.
For now, it should work with MikroTik routers at least.
Due to some confusion, XPipe will no longer use the system tray in macOS as an option when minimizing. It will instead conform to the usual macOS app handling that allows to reopen the window by clicking on the dock icon.
Some Windows admins disable cmd on their systems for security reasons. Previously this would have caused XPipe to not function on these systems as it relied on cmd. From now on, it can also dynamically fall back to PowerShell if needed without utilizing cmd at all.
One common problem in the past has been to fact that Microsoft ships relatively outdated OpenSSH versions on Windows, which do not support newer features like FIDO2 keys. Due to the permissive license of OpenSSH and its Windows fork, XPipe can bundle the latest OpenSSH versions on Windows. There is now an option the settings menu to use the latest bundled OpenSSH version.
All dependencies have been upgraded to the latest version, coming with a few fixes and some new features. In particular, the JavaFX version has been bumped, which now allows for native system theme observation and the usage of accent colors. Around 10 dependency libraries have been removed as they are no longer necessary.
The timeout model has been reworked. It is now set to a fixed amount of 30s while any active password prompts do no longer count towards it, meaning you can take your time when typing your passwords. An increased timeout value also allows for better handling of third party authentication schemes that XPipe has no control over, e.g. ones that will open a website in your browser for authentication.
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "8.0.1"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 8.0.1
Automated VirusTotal analysis of all artifacts:
Published by crschnick 8 months ago
This is this biggest update yet and includes many changes that are necessary going forward to allow for many future features to come. These new implementations take everything into account learned so far and are more intuitive and robust. Especially when considering the long-term timeline, these changes will come in handy.
The versioning scheme has also been changed to simplify version numbers. So we are going straight from 1.7 to 8.0!
Note that on Windows the automatic updater still has a few issues with race conditions if you are upgrading from 1.7.16. If the automatic update fails, you can still install 8.0 manually by downloading and installing it from https://github.com/xpipe-io/xpipe/releases.
The terminal launcher functionality got completely reworked with the goal to make it more flexible and improve the terminal startup performance. You will quickly notice the new implementation whenever you launch any connection in your terminal.
There is now support to directly query all VMs and containers located on a Proxmox system via the pct
and qm
tools. The containers can be accessed directly as any other containers while the VMs can be accessed via SSH. In case no SSH server is running in a vm, you can also choose to start one with XPipe.
This feature will be available in the professional version, but is also available in the free professional edition preview after release.
Any new professional features, such as the Proxmox support, will be available for free for a couple of weeks after their initial release. There is now a new dialog available to allow you to quickly set up the XPipe professional preview plan.
This allows anyone interested in playing around with new features to do so without limitation and no commitment.
The git installation on Windows comes with its own posix environment, which some people use to make use of standard Linux functionalities on Windows if they have not moved to WSL yet. This update brings full support to add this shell environment as well via the automatic detection functionality.
The file browser has been reworked in terms of performance and reliability. File transfers of many files or now faster and any errors that can occur are now handled better.
In terms of the interface, there is also now a progress indicator for files being transferred. For any file conflicts, there is now a new dialog to choose how to resolve any conflict when copying or moving files.
There are also a couple more changes included:
This update adds support to also add connections from other kubeconfig files.
Furthermore, you can also choose to use any namespace you want. This is useful in cases where you have not set up a context for every namespace you have.
The Kubernetes support is also now available in the pro preview after release.
This update comes with a complete rework of the settings menu. Many options have been added and existing ones have been improved, with a focus on providing more control over security settings. Make sure to give them a read to discover new options.
There has been a big focus on providing finer-grained control over security settings, which can be especially useful in enterprise contexts.
Previously all settings were stored on a per-system basis. This caused some problems with git vaults, as all relevant settings that should persist across systems were not synced. From now on, all options that should be the same on all synced systems are automatically included in the git vault.
This update comes with a newly created system for handling authentication that is better suited for arbitrary authentication prompts. This allows for better support for things like 2FA and other keyboard interactive authentications schemes. The sudo elevation authentication also has been reworked to be more intuitive and mirror the behavior of the system in regard to password prompts.
You also now have finer control over the caching behaviour of passwords and the sudo behaviour via additional settings.
You can now run a temporary docker container using a specified image that will get automatically removed once it is stopped. The container will keep running even if the image does not have any command specified that will run.
This can be useful if you quickly want to set up a certain environment by using a certain container image, e.g. a simple ubuntu
image. You can then enter the container as normal in XPipe, perform your operations, and stop the container once it's no longer needed. It is then removed automatically.
Up until now, connecting to fish shells or various dumb shells you typically find in devices like routers and links, did not work as there was no proper support for them. The shell handling implementation has now been rewritten to support fish login shells (after some timeout).
The implementation also now supports dumb shells that can be reached via ssh for example, but support still has to be implemented manually. Since I currently don't own any typical hardware like various routers and links, e.g. from cisco, I did not have the ability yet to do this. So if you own any hardware you would like to see supported, open an issue and share the typical output that is printed upon connection, and it can easily be supported.
For now, it should work with MikroTik routers at least.
Due to some confusion, XPipe will no longer use the system tray in macOS as an option when minimizing. It will instead conform to the usual macOS app handling that allows to reopen the window by clicking on the dock icon.
Some Windows admins disable cmd on their systems for security reasons. Previously this would have caused XPipe to not function on these systems as it relied on cmd. From now on, it can also dynamically fall back to PowerShell if needed without utilizing cmd at all.
One common problem in the past has been to fact that Microsoft ships relatively outdated OpenSSH versions on Windows, which do not support newer features like FIDO2 keys. Due to the permissive license of OpenSSH and its Windows fork, XPipe can bundle the latest OpenSSH versions on Windows. There is now an option the settings menu to use the latest bundled OpenSSH version.
All dependencies have been upgraded to the latest version, coming with a few fixes and some new features. In particular, the JavaFX version has been bumped, which now allows for native system theme observation and the usage of accent colors. Around 10 dependency libraries have been removed as they are no longer necessary.
The timeout model has been reworked. It is now set to a fixed amount of 30s while any active password prompts do no longer count towards it, meaning you can take your time when typing your passwords. An increased timeout value also allows for better handling of third party authentication schemes that XPipe has no control over, e.g. ones that will open a website in your browser for authentication.
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Published by crschnick 9 months ago
Over time, there have always been a few complaints about SSH connection timeout errors and slow SSH connection startup. These especially popped up in the latest release even though no obvious code was changed.
As it turns out, increasing the value for ConnectTimeout
in SSH does not actually only change the timeout after which an error is thrown, it is also used by some servers as a guideline for their response time. E.g. if you specify a 10s timeout, some servers will always take 10s to respond. This is of course not mentioned in any of the spec but is more of an implementation choice.
In the latest release this caused more errors as the timeout was set higher. It should also have affected many SSH connections basically since the release of XPipe. I don't know how many people have been affected by this, it heavily depends on which ssh server and configuration your server runs. It happens for example on my proxmox instances and my AWS EC2 instances. If your connections now start up much faster than before, then you are probably affected by it.
This release should fix all of these issues simply by not specifying a connect timeout at all. Great work there. If you are using ConnectTimeout
in your SSH configs, just remove it as it makes everything slower without having the effect of a timeout.
I would like to exchange a few words with whoever thought: A newly connected SSH client specified a 10s connect timeout? That means we can sit around idle for 9 seconds. That is a great idea.
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "1.7.16"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 1.7.16
Automated VirusTotal analysis of all artifacts:
Published by crschnick 9 months ago
xpipe open
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "1.7.15"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 1.7.15
Automated VirusTotal analysis of all artifacts:
Published by crschnick 9 months ago
This is just a small hotfix update to fix a few important issues:
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "1.7.14"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 1.7.14
Automated VirusTotal analysis of all artifacts:
Published by crschnick 10 months ago
Add remote host
-> SSH Config
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "1.7.13"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 1.7.13
Automated VirusTotal analysis of all artifacts:
Published by crschnick 10 months ago
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "1.7.12"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 1.7.12
Automated VirusTotal analysis of all artifacts:
Published by crschnick 10 months ago
For anyone interested in giving any new professional features a try without having to commit to buying a full license,
there is now a special preview mode available: Simply enter the license key D18D1C9F-D3CB-49CA-A909-FF385DECD948
and get full access to newly released professional features for two weeks after their initial release date. In fact, you can try it out right now to get access to the new SSH authentication features.
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "1.7.11"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 1.7.11
Automated VirusTotal analysis of all artifacts:
Published by crschnick 11 months ago
The git storage functionality has been in a bad state, hopefully this update will change that.
First of all, several bugs and inconsistencies have been fixed.
Furthermore, the authentication options have been greatly expanded.
You can now supply both HTTP and SSH git URLs. If any input is required like a username/password/passphrase, XPipe will show a prompt.
If you chose to use an SSH git URL, you can also set key-based authentication options just as for other ssh connections.
Lastly, there is now a general data directory as well in which you can put any additional files like SSH keys that you want to include in the repository. You can then refer to them just as normal within XPipe but their file paths are automatically adapted on any system you clone the repository to. You can open this data directory from the settings menu.
It is recommended to start with a remote git repository from scratch though to properly fix previous issues.
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "1.7.10"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 1.7.10
Automated VirusTotal analysis of all artifacts:
Published by crschnick 11 months ago
The git storage functionality has been in a bad state, hopefully this update will change that.
First of all, several bugs and inconsistencies have been fixed.
Furthermore, the authentication options have been greatly expanded.
You can now supply both HTTP and SSH git URLs. If any input is required like a username/password/passphrase, XPipe will show a prompt.
If you chose to use an SSH git URL, you can also set key-based authentication options just as for other ssh connections.
Lastly, there is now a general data directory as well in which you can put any additional files like SSH keys that you want to include in the repository. You can then refer to them just as normal within XPipe but their file paths are automatically adapted on any system you clone the repository to. You can open this data directory from the settings menu.
It is recommended to start with a remote git repository from scratch though to properly fix previous issues.
Please make sure to report any issue you can find. This helps the development a lot.
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "1.7.9"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 1.7.9
Automated VirusTotal analysis of all artifacts:
Published by crschnick 11 months ago
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "1.7.8"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 1.7.8
Automated VirusTotal analysis of all artifacts:
Published by crschnick 11 months ago
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "1.7.7"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 1.7.7
Automated VirusTotal analysis of all artifacts:
Published by crschnick 11 months ago
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "1.7.6"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 1.7.6
Automated VirusTotal analysis of all artifacts:
Published by crschnick 11 months ago
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "1.7.5"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 1.7.5
Automated VirusTotal analysis of all artifacts:
Published by crschnick 11 months ago
This update introduces an experimental implementation to support VMware virtual machines in VMware Player, Workstation, and Fusion installations.
The support includes actions like listing, starting, stopping, and pausing VMs plus opening a shell session or file browser session via SSH.
Note that the initial connection to a VM, which runs some setup, can take a long time.
It seems like the VMware CLI it is very slow in that regard, maybe I can find some improvements.
If everything works out well with this first attempt at VM support, it can be expanded to other hypervisors.
Up until now, the git storage functionality has only been available with a professional license.
However, due to the complex nature of git repositories, this feature had some inevitable rough edges
and did not live up to the robustness of a professional product.
As a result, I am moving this feature into the community edition.
Some parts of the UI have been reworked to achieve a more consistent appearance.
Furthermore, it has also been improved in regard to accessibility and its interaction with screen readers.
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "1.7.4"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 1.7.4
Automated VirusTotal analysis of all artifacts:
Published by crschnick 12 months ago
The entire website at https://xpipe.io has been redone, so you can check it out if you want and share your feedback on it.
Furthermore, XPipe is now also available in the Microsoft Store
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "1.7.3"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 1.7.3
Automated VirusTotal analysis of all artifacts:
Published by crschnick 12 months ago
Note that the automatic updater is broken in version 1.6.0. It will freeze the application and not perform the update. So do not try to click the install button in XPipe!
You have to install it manually from https://github.com/xpipe-io/xpipe/releases/tag/1.7.2. You can easily do this as uninstalling the old version does not delete any user data. Installing a newer version of XPipe also automatically uninstalls any old ones, so you don't have to manually uninstall it.
This update introduces a new toggle available for all scripts that if enabled, will automatically copy these scripts to the target system and put them into the PATH when launching a new terminal session. This allows you to easily call your scripts on any system without any setup.
After taking feedback and examples of other applications into consideration, I restructured the professional edition pricing.
There is now the option for a one-time payment, which will give you permanent access to all current professional features plus all that are released in the next year.
This one-time payment also makes it possible accept a lot more payment methods than before.
XPipe 1.7 comes with a new scripting system, you now can take your environment everywhere.
The idea is to create modular and reusable init scripts in XPipe that will be run on login but are independent of your profile files.
You can set certain scripts to be executed for every connection, allowing you to create a consistent environment across all remote systems.
As of now, there is only one set of scripts for enabling starship in your shell connections as a proof of concept.
However, you can contribute custom scripts here and here.
The second big change is a rework of the state system.
This merges the process of validating/refreshing with the process of establishing a connection, allowing for a much faster creation and launch of new connections.
It also enables a custom display and instant updates of the information displayed for a connection.
You will definitely notice this change when you connect to a system.
The entire storage and UI handling of connections has been reworked to improve performance.
Especially if you're dealing with a large amount of connections, this will be noticeable.
You can now assign colors to connections for organizational purposes to help in situations when many connections are opened in the file browser and terminals at the same time.
These colors will be shown to identify tabs everywhere within XPipe and also outside of XPipe, for example in terminals.
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "1.7.2"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 1.7.2
Automated VirusTotal analysis of all artifacts:
Published by crschnick almost 1 year ago
Note that the automatic updater is broken in version 1.6.0. It will freeze the application and not perform the update. So do not try to click the install button in XPipe!
You have to install it manually from https://github.com/xpipe-io/xpipe/releases/tag/1.7.1. You can easily do this as uninstalling the old version does not delete any user data. Installing a newer version of XPipe also automatically uninstalls any old ones, so you don't have to manually uninstall it.
XPipe 1.7 comes with a new scripting system, you now can take your environment everywhere.
The idea is to create modular and reusable init scripts in XPipe that will be run on login but are independent of your profile files.
You can set certain scripts to be executed for every connection, allowing you to create a consistent environment across all remote systems.
As of now, there is only one set of scripts for enabling starship in your shell connections as a proof of concept.
However, you can contribute custom scripts here and here.
The second big change is a rework of the state system.
This merges the process of validating/refreshing with the process of establishing a connection, allowing for a much faster creation and launch of new connections.
It also enables a custom display and instant updates of the information displayed for a connection.
You will definitely notice this change when you connect to a system.
The entire storage and UI handling of connections has been reworked to improve performance.
Especially if you're dealing with a large amount of connections, this will be noticeable.
You can now assign colors to connections for organizational purposes to help in situations when many connections are opened in the file browser and terminals at the same time.
These colors will be shown to identify tabs everywhere within XPipe and also outside of XPipe, for example in terminals.
Installers are the easiest way to get started and they come with an automatic updater functionality. They can also be used to upgrade an existing installation to a newer version. The following installers are available:
If you don't like installers, you can also use portable versions that are packaged as an archive. The following portable versions are available:
Install XPipe by pasting the installation command into your terminal. This will perform the full setup automatically.
powershell -ExecutionPolicy Bypass -Command iwr "https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.ps1" -OutFile "$env:TEMP\get-xpipe.ps1" ";" "&" "$env:TEMP\get-xpipe.ps1" -XPipeVersion "1.7.1"
bash <(curl -sL https://raw.githubusercontent.com/xpipe-io/xpipe/master/get-xpipe.sh) -v 1.7.1
Automated VirusTotal analysis of all artifacts: