You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This latest release introduces a new feature called Quick Connect that provides users with a convenient and efficient way to connect to their remote devices. With Quick Connect, users can quickly list and connect to their remote devices without the need to navigate to the Devices page in the ShellHub interface, scroll through the device list, and click a Connect button.
To open the Quick Connect dialog:
Press Ctrl+K
Click the Quick Connect button in the sidebar.
By opening the Quick Connect dialog window, users can easily search for available remote devices by hostname. This feature simplifies the connection process, allowing users to quickly locate the desired device from a long list of options.
Once the user finds the desired device, they can connect to it by simply pressing Enter or clicking a button. This feature is particularly useful for users who regularly need to connect to multiple remote devices and require a streamlined and efficient connection process.
In addition, the Quick Connect feature caters to command-line enthusiasts by enabling them to copy the device's SSHID by pressing Ctrl+C for use directly on the command line.
We would appreciate your feedback on the new Quick Connect feature. If you have any comments or suggestions on how we can improve it, please don't hesitate to share your thoughts on our discussion forum. Additionally, if you encounter any issues or bugs while using Quick Connect, please report them on our issue tracker so that we can address them promptly.
Improvements
Performance and resource usage
In previous releases, when the autossl option was enabled to generate Let's Encrypt certificates, an autossl container based on OpenResty would be deployed alongside the other containers, listening on ports 80 and 443 to receive HTTP and HTTPS traffic. All traffic arriving at the autossl container would be forwarded to the gateway container (which is also based on OpenResty) and only then forwarded to the final microservice. This approach led to a high overhead with two instances of OpenResty running, which consumed a significant amount of resources in cases with more than 10,000 devices. Moreover, the autossl container used an OpenResty plugin to generate Let's Encrypt certificates that had not been maintained for the past two years.
In this release, we have removed the autossl container, and requests now directly reach the gateway container. The gateway container now supports HTTPS using Certbot to manage Let's Encrypt certificates. This change has reduced CPU and memory usage by almost half and improved response times.
If you receive the "Found orphan containers" warning when starting the ShellHub instance, don't worry. This is because the autossl container has been removed from the Docker Compose configuration. You can simply ignore the warning or, the next time you start the instance, use the --remove-orphans option in the docker-compose up command.
