It's worse than that. The license opens with the standard clause:
"Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License."
But then proceeds to modify the license terms. This makes it definitionally -not- Apache 2 and no amount of word-smithing can get you out of that (appendix?).
There's a certain dishonesty in saying, "hey we're open source Apache" and then demanding a source available "something else". It's not even smart dishonesty... You offer the Apache original terms, but then you have to make it sufficiently clear those aren't really the terms enough that any fool can see this isn't the Apache terms after all.
Oof. OP, if you wanted to use terms like this you should have just picked BUSL. These "appendixes" were pretty clearly not written by a lawyer, they're redundant with each other (Appendix A includes the same content as Appendix B, just phrased less formally), and adding appendixes to Apache looks at best naive and at worst devious.
It seems similar to https://swarmlet.dev as well (I’m the author). I’ve since abandoned the project for different reasons. Currently I’m using Dokku, and have been using it for ~8 years. It’s a lovely project and pretty mature. I would recommend Dokku to anyone who wants to do (cheap) self-hosting!
Same here: I've been hosting two dozen services on Dokku for a side-project in the past few years and it's been working flawlessly!
Dokku and a Hetzner server makes hosting very easy
Piku is awesome! I've always thought the PaaS space is wide enough for many players in specific niches, and I love the approach of running processes outside of containers. About the only thing I would change is to utilize systemd (or similar) for spawning processes, but otherwise it's super neat. I've used it myself on a raspberry pi zero :)
I've been using coolify for all my apps for like 6 months or so now. I gotta say it's pretty impressive how well it works and the dev is quite responsive. I hope he can make it financially viable for himself.
It's still a little rough around the edges but quickly getting polished up.
I'm a bit down the kubernetes rabbit hole right now so I'm biased. Wouldn't it be better to have these solutions as kubernetes packages so that you could have the best of both worlds - flexibility and plug-and-play-ness?
Honestly I'm probably ending up reinventing the wheel a lot while going with kubernetes (on my personal projects) piecing together a lot of what these tools would give me with minimal configuration. And it feels like a lot of what I'm currently trying to work on in my side project is basically what I would get from these paas solutions but with the benefit of understanding and being able to tweak the various components better.
I had the same conclusion after evaluating those open source PaaS tools.
It just doesn't feel right for me. For small scale apps it's enough to spin up one or two VMs and run some containers with docker-compose (or just use Vercel/etc for a few bucks). But if it should scale, there is no alternative to kubernetes in the open source world.
I think myself - and folks maintaining other open source projects! - would love to hear feedback about what works/what doesn't. Feel free to reach via email (its in my profile) if you want, or our Discord/Slack.
I typically see users struggle with an initial deploy because their app depends on some variable or service running and that wasn't taken into account. This is pretty much the same as for general CI, where one might go through several commits before CI is running as you expect.
Very unfortunately, detecting these pain points requires work from both platform maintainers _as well as_ framework owners. The reason rails apps deployed so nicely across PaaS services in the past is because the Rails developers spent a ton of time ensuring applications _could_ do 12 Factor, while most PaaS services spent a ton of time working towards those constraints. Consequently, deploying other services that don't conform to this standard is a bit more difficult (though usually still possible).
Hatchbox is pretty cool, but not OSS - also doesn't use Docker IIRC if thats something you were looking for.
There's certainly something to be said about managed services though. For folks that don't mind managing their infra, OSS systems allow customizations and extensions that you wouldn't see from a managed service, but you potentially trade that for reliability guarantees and general maintenance. With Dokku for instance, I see folks go quite a while without upgrading - potentially causing issues when they do, but mostly making it so they miss out on features and bug fixes. For managed services like Hatchbox, you get that for free, but then the system might change underneath at a cadence you're unhappy with.
couple red flags:
1/ fake testimonials
2/ license that says "in case of conflict the terms of appendix will take precedence" followed by an appendix which says "yeah please don't change my code"
seems like open source for marketing's sake and not in any real terms
The name is not borrowed from Dokku, is taken from Docker, since when i was trying to buy the domain Dockploy.com was not available I just removed 1 char lol
Hey! Thank you for your feedback, initially this product was going to be a SaaS, and I just forgot it to remove from the main website, but i change my mind and then make open to everyone, I just need to remove that, thanks!
Database hosting is often the costly and complex part of hosting. I have played with the idea before of setting up a Hetzner VPS with 2CPU/8GB RAM and harden the it and setting up backups and then use it for all my databases. I don't have performance/scalability concerns, but I would be concerned with reliability and potentially security.
Same, but with DO managed Postgres. One place to do backups, monitor and easier to move apps between hosts if needed if they just talk to an external database instance not hosted on the same server.
Remember that post about the $104K Netlify bill? They said they'd introduce means to avoid this, but as of now, I can't find any such feature. I've finished a transition to CF Pages last week, but I still hoped Netlify would follow up on that promise.
Readit News
https://github.com/Dokploy/dokploy/blob/main/LICENSE.MD
https://github.com/Dokploy/dokploy/discussions/3
"Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License."
But then proceeds to modify the license terms. This makes it definitionally -not- Apache 2 and no amount of word-smithing can get you out of that (appendix?).
There's a certain dishonesty in saying, "hey we're open source Apache" and then demanding a source available "something else". It's not even smart dishonesty... You offer the Apache original terms, but then you have to make it sufficiently clear those aren't really the terms enough that any fool can see this isn't the Apache terms after all.
That means just the file "LICENSE.MD" is under that Non-Apache License. The rest of the project is something else.
- Dokku [0]
- CapRover [1]
[0] https://dokku.com/
[1] https://caprover.com/
Piku is awesome! I've always thought the PaaS space is wide enough for many players in specific niches, and I love the approach of running processes outside of containers. About the only thing I would change is to utilize systemd (or similar) for spawning processes, but otherwise it's super neat. I've used it myself on a raspberry pi zero :)
It's still a little rough around the edges but quickly getting polished up.
Honestly I'm probably ending up reinventing the wheel a lot while going with kubernetes (on my personal projects) piecing together a lot of what these tools would give me with minimal configuration. And it feels like a lot of what I'm currently trying to work on in my side project is basically what I would get from these paas solutions but with the benefit of understanding and being able to tweak the various components better.
It just doesn't feel right for me. For small scale apps it's enough to spin up one or two VMs and run some containers with docker-compose (or just use Vercel/etc for a few bucks). But if it should scale, there is no alternative to kubernetes in the open source world.
You can think of it as a much nicer CLI for k8s in that case. But it scales way down to a single machine deployment that is much simpler.
push heroku, done, get back to other things.
https://github.com/porter-dev/porter
and Otomi, "self-hosted DevOps PaaS for Kubernetes"
https://github.com/redkubes/otomi-core
I think myself - and folks maintaining other open source projects! - would love to hear feedback about what works/what doesn't. Feel free to reach via email (its in my profile) if you want, or our Discord/Slack.
I typically see users struggle with an initial deploy because their app depends on some variable or service running and that wasn't taken into account. This is pretty much the same as for general CI, where one might go through several commits before CI is running as you expect.
Very unfortunately, detecting these pain points requires work from both platform maintainers _as well as_ framework owners. The reason rails apps deployed so nicely across PaaS services in the past is because the Rails developers spent a ton of time ensuring applications _could_ do 12 Factor, while most PaaS services spent a ton of time working towards those constraints. Consequently, deploying other services that don't conform to this standard is a bit more difficult (though usually still possible).
Hatchbox is pretty cool, but not OSS - also doesn't use Docker IIRC if thats something you were looking for.
There's certainly something to be said about managed services though. For folks that don't mind managing their infra, OSS systems allow customizations and extensions that you wouldn't see from a managed service, but you potentially trade that for reliability guarantees and general maintenance. With Dokku for instance, I see folks go quite a while without upgrading - potentially causing issues when they do, but mostly making it so they miss out on features and bug fixes. For managed services like Hatchbox, you get that for free, but then the system might change underneath at a cadence you're unhappy with.
seems like open source for marketing's sake and not in any real terms
They’re all either freelancers or have very vague company names (Tech Innovations Inc, Dynamic Web Solutions) and the project looks brand new.
If they are real testimonials then they've presented them in the most fake-looking way possible.