Cleaver high level product road map

Wow! It’s already been about 5 months since @ashokgelal and I began working on taking Cleaver to the cloud. Looking at our backlog, we’ve completed just over 50 stories/issues and the progress we’ve made has been very productive and I believe Cleaver cloud beta has already passed the desktop version in terms of functionality and value delivered to users. :partly_sunny::fire:

Here is what we’ve completed thus far:

  • Create a Version Control Profile and hook up your GitHub account
  • Integrate with several cloud providers: DigitalOcean, AWS, Vultr, Linode, Hetzner
  • Connect to your custom cloud provider
  • Provision a server with Ubuntu 20.04, PHP 7.2/7.3/7.4, JRE, JDK, NodeJS, MySQL, MariaDB
  • Add and manage SSH keys
  • Add and manage databases and db users
  • Add and manage cron jobs
  • Add and manage process monitors
  • Add additional services post provision
  • Stop / Start / Restart services
  • Configure PHP and nginx settings
  • Add Laravel / Alpas / WordPress / NodeJS / PHP / Static HTML sites
  • Add and manage redirects
  • Set up web apps -> from simple single server to multi-server architectures
  • Push-to-deploy
  • Deployment log
  • Add and manage custom web hooks
  • Deployment notification Slack integration
  • Create a dark mode version of Cleaver
  • Building out new front-end website (cleaver.cloud)
  • Ability to import Cleaver desktop to the cloud
  • Added this new forum
  • And I’m sure many more that I am missing :sweat_smile:

Where are we going next? We’ll likely move to open beta for Cleaver and then will work on subscriptions. But, besides the more boring operational stuff, here is what we plan on working on next for Cleaver (in a relative order with higher priorities towards the top of the list):

  • Domain management (so you don’t have to go to a bunch of random places to manage smaller things such as a-records)
  • Additional WordPress and PHP configs (we want to make sure users can easily add and use popular plugins and handle common use-cases)
  • Support additional VC provider integration (namely, BitBucket and GitLab)
  • Support additional database types (PostgreSQL)
  • Additional nginx improvements
  • Add a dashboard so you can view your setups at a high level
  • Some additional TBA surprises
  • Sprinkle in many additional improvements and bug squashing

Of course, priorities may change but that’s what the plan is for the near future!

What do you think? We’d love to get your feedback so we know what is important to you, what’s not that important, and if there is anything we missed that you’d like to see.

:pray: Thank you!

3 Likes

These are some features that i wish to see in the future

  • automatic patches and security updates (as option, digital ocean has this on kubernetes)
  • Server backups(use spatie laravel-backup-server )
  • Database backups
  • Custom nginx directives
  • Server monitor(probably will be in the new dashboard)
  • Server health checks Notifications(integrated with the server monitor)
  • Load Balancers
  • Cache setup
  • Custom firewall rules

I hope some of these features get to cleaver…
Thanks :sunglasses: :sunglasses: :sunglasses:

4 Likes

Love it! I’m sure we can accommodate most if not all of those. :wink:

2 Likes

It would be nice if Cleaver supported Docker. Even just installing docker would be a good first step. Containerized web apps would be even better.

1 Like
  • Malware Scanning (ClamAV, fail2ban, opensource and free options: www.clamav.net/ and www.imunify360.com/antivirus)
  • Self-Healing for Services.
  • Upgrade or uninstall and replace a PHP version with a newer one or older one.
  • Automated Backups to a specific Amazon S3/Wasabi cloud storage for each server/app.
  • Support Wordpress Multisite
1 Like