Thanks for adding this.
The core problem of most of the PaaS is the dependency on Swarm (serious workload can't be run on swarm from my experience, disaster recovery too tough).
Working towards building an orchestrator.
2 karma · joined January 26, 2022
The core problem of most of the PaaS is the dependency on Swarm (serious workload can't be run on swarm from my experience, disaster recovery too tough).
Working towards building an orchestrator.
My focus is to build a PAAS which will have a great GUI to interact. So that anyone with little less knowledge of linux can even deploy apps with swiftwave.
Whenever we deploy in Heroku, Render or Railway to deploy app, we don't need to think much about underlying stuffs. I want to create similar kind of experience with Swiftwave.
Swiftwave handles many stuff other than lifecycle of app. It handles
> Application Deployment from git/image registry/uploaded code + Application Monitoring + Web SSH console for application + Webhook to trigger re-deployment of apps
> It uses docker swarm, so easily deploy apps across cluster also. Swiftwave completely support all the stuffs to work across cluster.
> Managed Ingress (HAProxy for TCP/HTTP/HTTPS, Custom built udp proxy)
> Domain + SSL Management (With Let's encrypt integration with auto-renewal support)
> Persistent Volume Management (Check size, Backup [local+s3], Restore of volume)
> Server Management ( Easy Onboarding + Server Monitoring + Web SSH Console for server )
> It has also a integrated app-store to install app at single click.
You may check the website to learn about all the features - https://swiftwave.org/
The license was initially written after checking various existing solutions like this (you can check caprover's license)
We are changing it because,
- I just came to know, Apache doesn't allow the modification in the license. Although there are many popular projects which is using that. So, I thought initially, It may be allowed.
- I don't want to move to GPL/AGPL for a small restriction which is only on the paid features of Swiftwave (which even doesn't exist, I don't know if someday any paid features will come or not).
- If there will be any paid feature in future, that can be in a different variant than the open source one. (Same way like docker or HAProxy) So we can keep Swiftwave as Open Source in Apache 2.0 and keep all the features available for free.