10 ms·

Open-source alternative to Heroku, Vercel, and Netlify

133 points by siumauricio 2y ago

mrbishalsaha 2y ago
[flagged]
iAkashPaul 2y ago
My go to for lightweight deployments is HuggingFace's Spaces, free 2-core CPU, anything else can go to either serverless container images on runpod or baseten.
sixhobbits 2y ago
Would be great to see a comparison to some better known alternatives like - Dokku [0] - CapRover [1] [0] https://dokku.com/ https://dokku.com/ [1] https://caprover.com/ https://caprover.com/
- rcarmo 2y ago
  I should add one to https://piku.github.io https://piku.github.io (spoiler - this doesn't use Docker at all)
  - josegonzalez 2y ago
    Dokku Maintainer here: 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 :)
    - rcarmo 2y ago
      Thanks! systemd would require more coding, because uwsgi does a lot automatically just by watching file creation/modification…
- huodon 2y ago
  + https://coolify.io/ https://coolify.io/
  - raybb 2y ago
    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.
- hcaz 2y ago
  + https://easypanel.io/ https://easypanel.io/
  - udev4096 2y ago
    This seems nice but looks like it's closed source?
- scirob 2y ago
  I'v tried these two and must say "it works out of the box" is only true maybe 50% of the time you try to deploy on them
  - nativeit 2y ago
    I’ve been using Caprover for years, and haven’t experienced anything like your reported rate of failure.
    - febeling 2y ago
      I can vouch for Dokku being equally very reliable and surprise-free to use.
  - josegonzalez 2y ago
    Dokku Maintainer here. 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).
- schappim 2y ago
  + https://hatchbox.io https://hatchbox.io
  - josegonzalez 2y ago
    Dokku Maintainer here: 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.
- woudsma 2y ago
  It seems similar to https://swarmlet.dev 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!
  - pawurb 2y ago
    Same. Dokku has worked seamlessly for me for 6+ years now!
  - AntonyGarand 2y ago
    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
- worldsayshi 2y ago
  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.
  - andix 2y ago
    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.
    - worldsayshi 2y ago
      My hypothesis right now is that if you know Kubernetes there's no "good" reason to not choose Kubernetes even if it's "overkill". You get a lot of flexibility this way but it's potentially a huge upfront cost with many options for shooting yourself in the foot. Understanding how to configure it without getting overwhelmed currently takes a lot of experience. You can run Kubernetes for cheap on a single node and it seems you can configure it so that you only need to care about the configuration when you need flexibility. I think. I get a similar feeling to how it was to set up a react project before you had create-react-app like tools. There's a lack of plug and play options that works for most use cases. Then again I might just be sort of rationalising the amount of time I've spent on it on a personal project that doesn't really require it.
  - colesantiago 2y ago
    unfortunately, many (like me) don't have time for going down k8s rabbit holes, we just want to get back building features. push heroku, done, get back to other things.
- aitchnyu 2y ago
  Also which ones have native support for background workers and cron jobs.
brnt 2y ago
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.
- Takennickname 2y ago
  "We promise to limit our revenue"
- dsamy 2y ago
  have you tried https://github.com/taubyte/tau https://github.com/taubyte/tau? it's easy to deploy and it's comparable to CF.
shafyy 2y ago
What's the best way to simplify self-hosting static sites? Is there some sort of Netlify for self-hosting that also integrates with selected CDNs or similar?
- _benj 2y ago
  I’ve been actually looking for some of these myself. The two that I’ve used are cloudflare pages and bunny storage. Cloudflare integrates with git and even runs builds for multiple static website frameworks (hugo, 11ty, etc) Bunny storage is a bit clunkier when it comes to setting a ci/cd since it has nothing to support it. One can upload via ftp, web browser or API. And after uploading usually purging the cdn cache is needed to apply the changes. I still prefer bunny because cloudflare give pages for “free”, which I don’t trust.
  - fastball 2y ago
    Cloudflare Pages has a free tier but also paid tiers.
  - shafyy 2y ago
    Yeah, I've also experimented with BunnyCDN and KeyCDN. I'd like to stay with an EU provider if possible.
- calvinmorrison 2y ago
  Using github or some other host that allows you to host static sites for free.
- fastball 2y ago
  Setup a github action that compiles the static site and uploads it to a server with nginx/caddy/etc? If you want it super self-hosted, then self-host gitlab and use their CI/CD instead of Github Actions.
  - shafyy 2y ago
    Yes, that's one possibility I was also considering, thanks!
xray2 2y ago
Can we get some screenshots of the dashboard? I tend to judge book by their covers
- norman784 2y ago
  There's a link to their website[0] in the repo with a few screenshots and a video. [0] https://dokploy.com/ https://dokploy.com/
nnnnico 2y ago
Is it common for open source projects to start clean with a single commit containing all the code instead of keeping the history? If author/OP are around, what is the reason for this? I can imagine one trying to hide iterations of shitty code or even copies of third parties which is reasonable I guess ( and I personally wouldn't care as a user/contributor to the project)
- WhatsName 2y ago
  Yes, I do the same. When I develop stuff, I tend to move quick and break things, which might involve swearing in git commit messages or just being plain stupid. I also have a habit of commiting sensitive information like host names, passwords or API-keys to private github repos, thinking not much about it. If you take your scratch project to opensource, you typically don't have the time to make sure not only the current version, but also every intermediate result is free of flaws someone else might dig up. So: mv private opensource; git init; git remote add ...; git push An artist also wouldn't hang every draft drawing beside his gallery piece...
  - imiric 2y ago
    That is a terrible practice. The point of a commit history is to see the development progress, document why a change was done, and in the future be able to reference or revert a change. If you squash all of it before making it public you rob yourself and any future contributors of those abilities. I also "move quickly and break things" when prototyping, but always go back and clean things up so that each change is atomic and well documented. In practice, this is not a perfect process, but being disciplined about this is worth it. Otherwise, you might as well not use version control at all. This is also my argument against squashing PRs into a single commit (unless it's really a single isolated change). Sure, it's convenient to do so, and you end up with a "clean" history, but having granular changes is worth the time and effort, and it's something you should strive to do in general.
    - 2024throwaway 2y ago
      Open source maintainers don’t owe you the ability to see development process before the project was open sourced. Squashing PRs is correct. Why would you need to see the hundred commits that lead to one working set of changes. The final changes are all that matter.
oefrha 2y ago
Somewhat tangential, is there anything like this that can dump a bunch of nginx configs and not take over port 80 & 443? I’ve been thinking it doesn’t hurt to have a nice GUI admin interface, one fewer deployment script to write for every little project, one click rollback, etc., but I already got a pretty beefy server where most things are run from, so I don’t want something to manage nginx for me and push out every service I already have running for years. Admittedly I haven’t looked very hard in this space.
- udev4096 2y ago
  Nginx Proxy Manager is a good one if you are looking for GUI of nginx
  - oefrha 2y ago
    Thanks, but I’m more interested in the automated deployment aspect, nginx itself I’m too familiar with ;)
    - udev4096 2y ago
      Have you checked the deployment tools mentioned in this thread? Such as dokku, piku and coolify
      - oefrha 2y ago
        Yes, I think they take over 443.
        Zekio 2y ago
        to my knowledge if you stop the nginx proxy it doesn't take over 443 in dokku at least, no idea if it is persisted over reboots though
        oefrha 2y ago
        Thanks, it seems dokku does allow bringing in outside nginx vhosts, something I must have overlooked the last time I checked. I'll have to take a deeper look.
danpalmer 2y ago
Nice project, but I'm interested in why the decision was made to flatten all commits for publishing? It makes it harder to understand the codebase, harder to contribute, and suggests a lack of commitment to the open-source model. Is the plan to develop in the open from now on, or to drop releases developed in private in large flattened commits like this?
- mhitza 2y ago
  > suggests a lack of commitment to the open-source model. I literally chuckled when I read your comment. It sounds reasonable to flatten commits before a release, as I, and others, who are hacking on code litter their history with "fix this" / "fix that" / "asjhdasjd" / "f**". Open source model doesn't mean version control transparency. Open source model could also be development done in a private fork, and release commits dumped into a public repository.
  - verve_rat 2y ago
    Yeah, open source could mean code distributed in zip bundles. Git history is an orthogonal concern.
    - danpalmer 2y ago
      I said "open source model" rather than just open source. While open source is only about the licence, I think publishing on GitHub typically implies a further model of accepting contributions, developing in the open, and being a part of that ecosystem. In my experience this is how open source projects tend to thrive in the last 15 years or so. Projects that are open source but don't accept contributions and just dump a zip on a website somewhere once a year are a very different thing and lose some of the benefits.
  - 255kb 2y ago
    I concur, my first commit was a big one, squashed to avoid showing my shitty history, after coding an MVP for 3 months. I initially had no intention to open-source, so I was caring at all about my commit history. I still had one or two questions like "is it even your code?".
throwaway984393 2y ago
[dead]
l5870uoo9y 2y ago
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.
- acedTrex 2y ago
  I pay for a single RDS instance with daily backups and just shove all my dbs into that.
  - dewey 2y ago
    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.
T3RMINATED 2y ago
[dead]
ssddanbrown 2y ago
I wouldn't consider this open source, the license [1] appears to put very non-open terms on the use, modification and distribution of the project. [1] https://github.com/Dokploy/dokploy/blob/be56ba046cb3b2b8676d5f8020cf56844d601730/LICENSE.MD https://github.com/Dokploy/dokploy/blob/be56ba046cb3b2b8676d...
- input_sh 2y ago
  OSI would: https://opensource.org/license/apache-2-0 https://opensource.org/license/apache-2-0 Edit: I'm wrong, see below.
  - 255kb 2y ago
    It's Apache 2.0 + custom clauses excluding any commercial/for-profit usage.
    - input_sh 2y ago
      My mistake, I should've paid more attention.
  - mhitza 2y ago
    The Apache License is, however the additional terms the author has made to the license make it not open source; because the additional terms supersede the Apache License. It looks like Apache Licensed but its the BSL (ElasticSearch, Redis, Mongodb license path) in disguise. Author should have used AGPL if he wanted to make a product that isn't easily/eagerly SaaSified.
  - megadal 2y ago
    It probably was open source before the license was modified to prevent commercial use, which is not open source.
  - ssddanbrown 2y ago
    I've added extra explanation in a discussion I've opened on the project: https://github.com/Dokploy/dokploy/discussions/3 https://github.com/Dokploy/dokploy/discussions/3
tennis_80 2y ago
Are the testimonials real? They’re all either freelancers or have very vague company names (Tech Innovations Inc, Dynamic Web Solutions) and the project looks brand new.
- jsheard 2y ago
  Vague company names and abbreviated surnames and random Memoji avatars for all of them. If they are real testimonials then they've presented them in the most fake-looking way possible.
- siumauricio 2y ago
  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!
  - networked 2y ago
    If they were fake, "I had fake testimonials because I was going to charge customers for my product" is something you don't want to suggest.
sebys7 2y ago
As others have also said, the first thought when I saw 8 commits was "Oh, seems like a toy project". Only after surfing a bit around the code I saw it's more serious. Is your intention to also transform this into a platform like Vercel/Heroku?
heap_perms 2y ago
The word "Open-Source" is misleading and should be removed from the title.
ognarb 2y ago
This is not open source, just take a look at the license. https://github.com/Dokploy/dokploy/blob/main/LICENSE.MD https://github.com/Dokploy/dokploy/blob/main/LICENSE.MD
- BSDobelix 2y ago
  >>you may not use this file except in compliance with the License. That means just the file "LICENSE.MD" is under that Non-Apache License. The rest of the project is something else.
- sbuttgereit 2y ago
  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.
- japhyr 2y ago
  ssddanbrown opened a discussion on the repo laying out the reasons why this is not an open source project. https://github.com/Dokploy/dokploy/discussions/3 https://github.com/Dokploy/dokploy/discussions/3
- lolinder 2y ago
  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.
djha-skin 2y ago
Looks pretty sweet, as long as there was a way to integrate it with nginx ingress controller somehow I'd say this is very interesting indeed.
jatins 2y ago
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
- megadal 2y ago
  Also the name seems borrowed from Dokku, an actually open source product in much the same domain.
  - siumauricio 2y ago
    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
    - megadal 2y ago
      Yes, but surely you can see the similarities in both name and use case. By itself it seems innocuous but coupled with the blatant misuse of the term "Open-source", fake reviews and rather strange commit history, you can maybe understand why one might assume some malintent, or at least, somewhat shady intent.
      - siumauricio 2y ago
        Respect your opinion, 1. This will depend on each person who wants to interpret it that way. 2. About fake reviews, please review the others comment, I talked about this, this project initially was going to be a SaaS but at the last minute I decided to make it free, I already removed the testimonials. 3. Strange story commit, let me ask you a question, have you ever created some open source project? have you already checked the source code to say something is strange? check the others comment again this initially was going to be a SaaS i didn't have plans to release this for free, at the last minute i released and that's all, what's the purpose on see bad commits/code i have around 600 commits in another repository, I think it's a pleasure effect to see those commits or something because I see that people get excited, we DO NOT collect any tracking information or anything strange, you can review the code for yourself, I just want to have a clean repository that's all 4. About the license: This project was generally made for people who want to host their personal projects, mpvs or for agencies that want to do quick deployments on a simple vps server, maybe I'm wrong but 98% of people will use it personally and not a way to resell this same software without changing anything, so this probably won't affect you, as I say to almost no one, if you think you can take advantage of this project by selling it, let me know and I'll give you the permission you want, it's just asking, but People today criticize to get attention and it is valid. greetings! you can check the docs commit at the last minute i added the open source term before https://github.com/Dokploy/docs/commit/456db4922538d8e4e8a12c7732020e3fef0d2fa8 https://github.com/Dokploy/docs/commit/456db4922538d8e4e8a12... after https://github.com/Dokploy/docs/commit/e386b356550857a7282f9d5899c487e146a55c7a https://github.com/Dokploy/docs/commit/e386b356550857a7282f9...
dsamy 2y ago
Not really open source, plus it does not scale beyond one VM! tau (https://github.com/taubyte/tau https://github.com/taubyte/tau) is a real alternative, to cloudflare & vercel and others, that is open source and actually scales -> https://taubyte.com/blog/be-competitive-in-few-minutes/ https://taubyte.com/blog/be-competitive-in-few-minutes/

133 points by siumauricio 2y ago

[flagged]

My go to for lightweight deployments is HuggingFace's Spaces, free 2-core CPU, anything else can go to either serverless container images on runpod or baseten.

sixhobbits 2y ago

Would be great to see a comparison to some better known alternatives like - Dokku [0] - CapRover [1] [0] https://dokku.com/ https://dokku.com/ [1] https://caprover.com/ https://caprover.com/

rcarmo 2y ago
I should add one to https://piku.github.io https://piku.github.io (spoiler - this doesn't use Docker at all)
- josegonzalez 2y ago
  Dokku Maintainer here: 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 :)
  - rcarmo 2y ago
    Thanks! systemd would require more coding, because uwsgi does a lot automatically just by watching file creation/modification…
huodon 2y ago
+ https://coolify.io/ https://coolify.io/
- raybb 2y ago
  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.
hcaz 2y ago
+ https://easypanel.io/ https://easypanel.io/
- udev4096 2y ago
  This seems nice but looks like it's closed source?
scirob 2y ago
I'v tried these two and must say "it works out of the box" is only true maybe 50% of the time you try to deploy on them
- nativeit 2y ago
  I’ve been using Caprover for years, and haven’t experienced anything like your reported rate of failure.
  - febeling 2y ago
    I can vouch for Dokku being equally very reliable and surprise-free to use.
- josegonzalez 2y ago
  Dokku Maintainer here. 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).
schappim 2y ago
+ https://hatchbox.io https://hatchbox.io
- josegonzalez 2y ago
  Dokku Maintainer here: 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.
woudsma 2y ago
It seems similar to https://swarmlet.dev 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!
- pawurb 2y ago
  Same. Dokku has worked seamlessly for me for 6+ years now!
- AntonyGarand 2y ago
  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
worldsayshi 2y ago
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.
- andix 2y ago
  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.
  - worldsayshi 2y ago
    My hypothesis right now is that if you know Kubernetes there's no "good" reason to not choose Kubernetes even if it's "overkill". You get a lot of flexibility this way but it's potentially a huge upfront cost with many options for shooting yourself in the foot. Understanding how to configure it without getting overwhelmed currently takes a lot of experience. You can run Kubernetes for cheap on a single node and it seems you can configure it so that you only need to care about the configuration when you need flexibility. I think. I get a similar feeling to how it was to set up a react project before you had create-react-app like tools. There's a lack of plug and play options that works for most use cases. Then again I might just be sort of rationalising the amount of time I've spent on it on a personal project that doesn't really require it.
- colesantiago 2y ago
  unfortunately, many (like me) don't have time for going down k8s rabbit holes, we just want to get back building features. push heroku, done, get back to other things.
aitchnyu 2y ago
Also which ones have native support for background workers and cron jobs.

brnt 2y ago

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.

Takennickname 2y ago
"We promise to limit our revenue"
dsamy 2y ago
have you tried https://github.com/taubyte/tau https://github.com/taubyte/tau? it's easy to deploy and it's comparable to CF.

shafyy 2y ago

What's the best way to simplify self-hosting static sites? Is there some sort of Netlify for self-hosting that also integrates with selected CDNs or similar?

_benj 2y ago
I’ve been actually looking for some of these myself. The two that I’ve used are cloudflare pages and bunny storage. Cloudflare integrates with git and even runs builds for multiple static website frameworks (hugo, 11ty, etc) Bunny storage is a bit clunkier when it comes to setting a ci/cd since it has nothing to support it. One can upload via ftp, web browser or API. And after uploading usually purging the cdn cache is needed to apply the changes. I still prefer bunny because cloudflare give pages for “free”, which I don’t trust.
- fastball 2y ago
  Cloudflare Pages has a free tier but also paid tiers.
- shafyy 2y ago
  Yeah, I've also experimented with BunnyCDN and KeyCDN. I'd like to stay with an EU provider if possible.
calvinmorrison 2y ago
Using github or some other host that allows you to host static sites for free.
fastball 2y ago
Setup a github action that compiles the static site and uploads it to a server with nginx/caddy/etc? If you want it super self-hosted, then self-host gitlab and use their CI/CD instead of Github Actions.
- shafyy 2y ago
  Yes, that's one possibility I was also considering, thanks!

xray2 2y ago

Can we get some screenshots of the dashboard? I tend to judge book by their covers

norman784 2y ago
There's a link to their website[0] in the repo with a few screenshots and a video. [0] https://dokploy.com/ https://dokploy.com/

nnnnico 2y ago

Is it common for open source projects to start clean with a single commit containing all the code instead of keeping the history? If author/OP are around, what is the reason for this? I can imagine one trying to hide iterations of shitty code or even copies of third parties which is reasonable I guess ( and I personally wouldn't care as a user/contributor to the project)

WhatsName 2y ago
Yes, I do the same. When I develop stuff, I tend to move quick and break things, which might involve swearing in git commit messages or just being plain stupid. I also have a habit of commiting sensitive information like host names, passwords or API-keys to private github repos, thinking not much about it. If you take your scratch project to opensource, you typically don't have the time to make sure not only the current version, but also every intermediate result is free of flaws someone else might dig up. So: mv private opensource; git init; git remote add ...; git push An artist also wouldn't hang every draft drawing beside his gallery piece...
- imiric 2y ago
  That is a terrible practice. The point of a commit history is to see the development progress, document why a change was done, and in the future be able to reference or revert a change. If you squash all of it before making it public you rob yourself and any future contributors of those abilities. I also "move quickly and break things" when prototyping, but always go back and clean things up so that each change is atomic and well documented. In practice, this is not a perfect process, but being disciplined about this is worth it. Otherwise, you might as well not use version control at all. This is also my argument against squashing PRs into a single commit (unless it's really a single isolated change). Sure, it's convenient to do so, and you end up with a "clean" history, but having granular changes is worth the time and effort, and it's something you should strive to do in general.
  - 2024throwaway 2y ago
    Open source maintainers don’t owe you the ability to see development process before the project was open sourced. Squashing PRs is correct. Why would you need to see the hundred commits that lead to one working set of changes. The final changes are all that matter.

oefrha 2y ago

Somewhat tangential, is there anything like this that can dump a bunch of nginx configs and not take over port 80 & 443? I’ve been thinking it doesn’t hurt to have a nice GUI admin interface, one fewer deployment script to write for every little project, one click rollback, etc., but I already got a pretty beefy server where most things are run from, so I don’t want something to manage nginx for me and push out every service I already have running for years. Admittedly I haven’t looked very hard in this space.

udev4096 2y ago
Nginx Proxy Manager is a good one if you are looking for GUI of nginx
- oefrha 2y ago
  Thanks, but I’m more interested in the automated deployment aspect, nginx itself I’m too familiar with ;)
  - udev4096 2y ago
    Have you checked the deployment tools mentioned in this thread? Such as dokku, piku and coolify
    - oefrha 2y ago
      Yes, I think they take over 443.
      - Zekio 2y ago
        to my knowledge if you stop the nginx proxy it doesn't take over 443 in dokku at least, no idea if it is persisted over reboots though
        oefrha 2y ago
        Thanks, it seems dokku does allow bringing in outside nginx vhosts, something I must have overlooked the last time I checked. I'll have to take a deeper look.

danpalmer 2y ago

Nice project, but I'm interested in why the decision was made to flatten all commits for publishing? It makes it harder to understand the codebase, harder to contribute, and suggests a lack of commitment to the open-source model. Is the plan to develop in the open from now on, or to drop releases developed in private in large flattened commits like this?

mhitza 2y ago
> suggests a lack of commitment to the open-source model. I literally chuckled when I read your comment. It sounds reasonable to flatten commits before a release, as I, and others, who are hacking on code litter their history with "fix this" / "fix that" / "asjhdasjd" / "f**". Open source model doesn't mean version control transparency. Open source model could also be development done in a private fork, and release commits dumped into a public repository.
- verve_rat 2y ago
  Yeah, open source could mean code distributed in zip bundles. Git history is an orthogonal concern.
  - danpalmer 2y ago
    I said "open source model" rather than just open source. While open source is only about the licence, I think publishing on GitHub typically implies a further model of accepting contributions, developing in the open, and being a part of that ecosystem. In my experience this is how open source projects tend to thrive in the last 15 years or so. Projects that are open source but don't accept contributions and just dump a zip on a website somewhere once a year are a very different thing and lose some of the benefits.
- 255kb 2y ago
  I concur, my first commit was a big one, squashed to avoid showing my shitty history, after coding an MVP for 3 months. I initially had no intention to open-source, so I was caring at all about my commit history. I still had one or two questions like "is it even your code?".

throwaway984393 2y ago

[dead]

l5870uoo9y 2y ago

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.

acedTrex 2y ago
I pay for a single RDS instance with daily backups and just shove all my dbs into that.
- dewey 2y ago
  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.

T3RMINATED 2y ago

[dead]

ssddanbrown 2y ago

I wouldn't consider this open source, the license [1] appears to put very non-open terms on the use, modification and distribution of the project. [1] https://github.com/Dokploy/dokploy/blob/be56ba046cb3b2b8676d5f8020cf56844d601730/LICENSE.MD https://github.com/Dokploy/dokploy/blob/be56ba046cb3b2b8676d...

input_sh 2y ago
OSI would: https://opensource.org/license/apache-2-0 https://opensource.org/license/apache-2-0 Edit: I'm wrong, see below.
- 255kb 2y ago
  It's Apache 2.0 + custom clauses excluding any commercial/for-profit usage.
  - input_sh 2y ago
    My mistake, I should've paid more attention.
- mhitza 2y ago
  The Apache License is, however the additional terms the author has made to the license make it not open source; because the additional terms supersede the Apache License. It looks like Apache Licensed but its the BSL (ElasticSearch, Redis, Mongodb license path) in disguise. Author should have used AGPL if he wanted to make a product that isn't easily/eagerly SaaSified.
- megadal 2y ago
  It probably was open source before the license was modified to prevent commercial use, which is not open source.
- ssddanbrown 2y ago
  I've added extra explanation in a discussion I've opened on the project: https://github.com/Dokploy/dokploy/discussions/3 https://github.com/Dokploy/dokploy/discussions/3

tennis_80 2y ago

Are the testimonials real? They’re all either freelancers or have very vague company names (Tech Innovations Inc, Dynamic Web Solutions) and the project looks brand new.

jsheard 2y ago
Vague company names and abbreviated surnames and random Memoji avatars for all of them. If they are real testimonials then they've presented them in the most fake-looking way possible.
siumauricio 2y ago
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!
- networked 2y ago
  If they were fake, "I had fake testimonials because I was going to charge customers for my product" is something you don't want to suggest.

sebys7 2y ago

As others have also said, the first thought when I saw 8 commits was "Oh, seems like a toy project". Only after surfing a bit around the code I saw it's more serious. Is your intention to also transform this into a platform like Vercel/Heroku?

heap_perms 2y ago

The word "Open-Source" is misleading and should be removed from the title.

ognarb 2y ago

This is not open source, just take a look at the license. https://github.com/Dokploy/dokploy/blob/main/LICENSE.MD https://github.com/Dokploy/dokploy/blob/main/LICENSE.MD

BSDobelix 2y ago
>>you may not use this file except in compliance with the License. That means just the file "LICENSE.MD" is under that Non-Apache License. The rest of the project is something else.
sbuttgereit 2y ago
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.
japhyr 2y ago
ssddanbrown opened a discussion on the repo laying out the reasons why this is not an open source project. https://github.com/Dokploy/dokploy/discussions/3 https://github.com/Dokploy/dokploy/discussions/3
lolinder 2y ago
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.

djha-skin 2y ago

Looks pretty sweet, as long as there was a way to integrate it with nginx ingress controller somehow I'd say this is very interesting indeed.

jatins 2y ago

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

megadal 2y ago
Also the name seems borrowed from Dokku, an actually open source product in much the same domain.
- siumauricio 2y ago
  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
  - megadal 2y ago
    Yes, but surely you can see the similarities in both name and use case. By itself it seems innocuous but coupled with the blatant misuse of the term "Open-source", fake reviews and rather strange commit history, you can maybe understand why one might assume some malintent, or at least, somewhat shady intent.
    - siumauricio 2y ago
      Respect your opinion, 1. This will depend on each person who wants to interpret it that way. 2. About fake reviews, please review the others comment, I talked about this, this project initially was going to be a SaaS but at the last minute I decided to make it free, I already removed the testimonials. 3. Strange story commit, let me ask you a question, have you ever created some open source project? have you already checked the source code to say something is strange? check the others comment again this initially was going to be a SaaS i didn't have plans to release this for free, at the last minute i released and that's all, what's the purpose on see bad commits/code i have around 600 commits in another repository, I think it's a pleasure effect to see those commits or something because I see that people get excited, we DO NOT collect any tracking information or anything strange, you can review the code for yourself, I just want to have a clean repository that's all 4. About the license: This project was generally made for people who want to host their personal projects, mpvs or for agencies that want to do quick deployments on a simple vps server, maybe I'm wrong but 98% of people will use it personally and not a way to resell this same software without changing anything, so this probably won't affect you, as I say to almost no one, if you think you can take advantage of this project by selling it, let me know and I'll give you the permission you want, it's just asking, but People today criticize to get attention and it is valid. greetings! you can check the docs commit at the last minute i added the open source term before https://github.com/Dokploy/docs/commit/456db4922538d8e4e8a12c7732020e3fef0d2fa8 https://github.com/Dokploy/docs/commit/456db4922538d8e4e8a12... after https://github.com/Dokploy/docs/commit/e386b356550857a7282f9d5899c487e146a55c7a https://github.com/Dokploy/docs/commit/e386b356550857a7282f9...

dsamy 2y ago

Not really open source, plus it does not scale beyond one VM! tau (https://github.com/taubyte/tau https://github.com/taubyte/tau) is a real alternative, to cloudflare & vercel and others, that is open source and actually scales -> https://taubyte.com/blog/be-competitive-in-few-minutes/ https://taubyte.com/blog/be-competitive-in-few-minutes/