FTPloy VS ShellHub

• Automated Deployment
  FTPloy automates the deployment process directly from your Git repository, reducing the time and effort required for manual deployments.
• Integration with Git Repositories
  It integrates seamlessly with popular Git platforms like GitHub and Bitbucket, allowing for a smooth deployment workflow from version control.
• Easy to Use Interface
  FTPloy offers an intuitive user interface that makes it easy for users to set up and manage deployments without requiring extensive technical knowledge.
• Support for Multiple Environments
  You can deploy to multiple environments, such as development, staging, and production, making it flexible for different stages of your development cycle.
• Notification System
  FTPloy provides notifications for deployment successes or failures, allowing teams to stay informed about the status of their deployments.

Possible disadvantages

• Limited Hosting Options
  FTPloy primarily uses FTP for deployments, which may not be compatible with all types of hosting solutions that prefer more modern deployment methods.
• Security Concerns
  FTP, being less secure than other protocols like SFTP or SSH, might expose your deployment to security vulnerabilities.
• Lack of Advanced Features
  Compared to more comprehensive CI/CD tools, FTPloy might lack advanced features that larger teams or projects might require, such as detailed build pipelines or complex automation scripts.
• Dependency on Internet Connection
  As an online service, FTPloy requires a stable internet connection for deployment operations, which could be a limitation in areas with poor connectivity.
• Potential for Errors with FTP
  Since FTP is used, there might be higher chances of encountering transfer errors or incomplete deployments, especially with large file sizes.

• Centralized Management
  ShellHub offers centralized management for all your SSH devices, making it easier to manage multiple devices from a single interface.
• Access Control
  With ShellHub, administrators can set up role-based access control, allowing for granular permissions and improved security over who can access which devices.
• Web-based Terminal
  ShellHub provides a web-based terminal that allows users to access SSH devices through a browser, eliminating the need for a local SSH client.
• Cloud and On-premises Deployment
  Users have the flexibility to deploy ShellHub in the cloud or on-premises, which can be tailored to their specific infrastructure needs and compliance requirements.
• Audit Logging
  ShellHub includes audit logging features that help in tracking and monitoring user activity for better compliance and auditing purposes.

Possible disadvantages

• Complexity for Small Networks
  For smaller networks or fewer devices, ShellHub might be overkill and introduce unnecessary complexity compared to simpler SSH management solutions.
• Resource Intensive
  Deploying and running ShellHub can be resource-intensive, requiring sufficient hardware and potentially leading to higher operational costs.
• Learning Curve
  Users may encounter a learning curve when initially setting up and configuring ShellHub, especially if they are new to centralized device management systems.
• Dependency on Web Interface
  Relying on the web-based interface may be a disadvantage in environments where network reliability is an issue or where minimalist solutions are preferred.
• Potential Security Risks
  As with any centralized management system, there is a potential risk that a compromised ShellHub deployment could lead to broader access issues across managed devices.

Tracking FTPloy since Mar 2021.

• Tutorial: How to access Raspberry Pi remotely from anywhere

  And we finished. Now You can access your RPI in an easy, fast, and safe way. If you have any doubts, feel free to check our documentation or contact us at contact@shellhub.io. - Source: dev.to / about 4 years ago