677 karma · joined May 26, 2012
You can also use the built-in webhook from inside CapRover control panel but it requires you to log in via your GitHub account in Cap (I created a secondary CI account for this).
Installing a GitHub app comes with challenges, it basically gives Coolify access to your account should they want it, since they control the app and not you. This is bad from a privacy perspective.
CapRover has dark mode. :-) But yes the design is more utilitarian in Cap and not as nice to look at.
Also I think the way you create different kinds of resources are confusing in Coolify, like what is a "Git Source" or "Destination", all I want is to run my container. It's very different from Herokus/Caps interface and not in a good way.
Also why can't I just deploy from an image? In CapRover I often spin up a container, like `redis-commander` or `wordpress` and then just configure its env vars and volume mounts. In Coolify it seems you have to connect a GitHub repo which is not a desirable workflow for me.
Tangentially I was looking at Render.com the other day and they also don't support zero downtime deployments if you have a mounted volume, so it's not very uncommon even on cloud platforms.
As for restarts, I didn't have that problem yet, I believe CapRover adds `restart: always` to all the running containers so they should automatically boot. You might want to check out the logs of the containers that don't restart or just always hard restart the server after a Docker update.
(Top left connect icon > Emulator > Bangle JS 2)
Just don't expect the ecosystem to be very polished.
These would all work out of the box.
The only plugins that would not work are:
1. Plugins that register their own database tables (however there already exists prior art such as https://github.com/aaemnnosttv/wp-sqlite-db for handling these cases)
2. Plugins that do direct queries against the standard database schema (broadly either for invalid (bad code) or performance (valid but slim use case) reasons)
Also, WordPress would of course keep the old query functions around and they would likely add a tag to the plugin repository so authors can mark plugins as supporting thes new ORM features.
Great idea in my opinion!
Our contract in Sweden is NordPool market price + 0,006 USD/kWh. Typical electricity prices in Sweden is anything from 0,001 USD/kWh to 0.5 USD/kWh, it varies widely day by day. This is what enables people to be able to save by using electricity when it's almost free.
https://community.ui.com/questions/BUG-USG-PPPoE-or-Static-I...
https://www.nordpoolgroup.com/en/Market-data1/Dayahead/Area-...
- Live in the "walls" (barracks) - Sneak out during curfew to do tasks and build things to open up more areas, and also for food - You nurture a relationship with the other prisoners and new ones arrive often
Check it out!
* https://github.com/crownframework/svelte-error-boundary * https://github.com/denisstasyev/svelte-error-boundary
They only protect from component initialization errors but it's better than nothing. I think Svelte v4 will have more coherent error handling.