๐ I am excited to announce that I am now officially a Core Developer at
@coolifyio
! ๐ Coolify has become my passion and I'm committed to taking it further than ever imagined. I am excited to shape the future of Coolify together with the community.
It is Monday and I have exciting news! ๐
Over the past weeks/months, I realized that
@coolifyio
is growing on me. ๐
So thanks to the support of the community, sponsors, and cloud users, Coolify now have its first paid core contributor. It's unbelievable, right? It certainly
This week I merged, tested and fixed more than 50 new services for
@coolifyio
contributed by the community. Here is the full list of new services coming to Coolify in the next release (some are already available):
1. Immich
2. Nextcloud with Postgres
3. Nextcloud with MariaDB
4.
Just fixed some env bugs in
@coolifyio
so I can show
@heyandras
that I would be a good hire as a full-time core contributor: (one of the many more PRs planned).
Week 2 - Daily log Tuesday:
Today I was reluctant to share my daily update because my day was not as good as some others. But you have to show up every day, even if you are not at your best. So I did.
- I fixed 3 Redis issues for
@coolifyio
in one of my own PRs that was long
I plan to post every day (except maybe weekends) and do
#buildingpublic
about what I worked on today. Right now this will mostly be
@coolifyio
development updates, but soon I plan to start my own projects. Is that something you guys would be interested in?
Thank you all for the love and incredible support this week! โค๏ธ
We reached 200+ followers ๐ in one week (5 days) which is absolutely incredible ๐คฏ.
I had an amazing and exhausting week developing
@coolifyio
. I merged more than a handful of PRs and added a few, just a few new
Today was an eventful and very productive day. I cannot thank you all enough for all the nice comments and support ๐. I also merged 10+ PRs for
@coolifyio
which will bring some more awesome one click services in the next update.
Another PR review day is almost over. Today I merged more templates for
@coolifyio
, I guess nobody would have guessed that :). One of the most notable new templates is more database options for the
@Nextclouders
one click template. I have already merged well over 30 PRs and we
Week 2 - Daily log Monday:
- I merged and fixed one of the most exciting new service template that will be coming to
@coolifyio
in the next update. It is a one-click deployment template for
@calcom
.
- I also fixed some bugs in existing templates and merged some PRs (in total I
@payloadcms
Payload looks interesting. I am also looking for alternatives to WordPress. Since I am a developer at
@coolifyio
and actively use it myself, is it possible to deploy Payload via docker compose and manage the stuff like I would in WordPress?
Week 2 - Daily log Wednesday:
Today I am back at peak performance. Here is what I did:
- Finished my Redis PR fixing 3 issues for
@coolifyio
.
- Fixed and opened a PR to fix 1 issue with the OTP QR code not being easy to scan and also added the OTP URL as requested by a user.
-
Week 2 - Daily log Thursday:
- I opened a larger PR to give users the ability to disable the 2-step confirmation flow I added in an update. Now users can have more convenience and less security if they want ๐. And for developers like me who work on core
@coolifyio
, it is enabled
Week 2 - Daily Log Friday: This week has been incredibly productive and today was no exception.
In total, I shipped tons of fixes to the next branch, opened 8 PRs, and merged countless PRs from the community. I also resolved and triaged over 40 issues.
And today I did the
@khromov
@heyandras
@coolifyio
The community are our testers, if something does not work the community will most definitely report it and with over 80,000 servers using it I think this will be fine. Maybe we need some tests as well but not sure yet how because each template is so different.
@JamesMikrut
@payloadcms
@coolifyio
Thank you. I see it looks like I always need to build form source (my repo) right? So I cannot use a prebuilt image in a compose file, I have to build my own image.
@YTCodeAntonio
Start with the smalest server your stack allows. For example supabase needs a lot more power than WordPress for example. Then scale up as your server hits 80% or more usage.
@jyriso
@heyandras
@coolifyio
The biggest difference is that Coolify is completely free if you host it yourself and open source and can be hosted on your own VPS while Ploi is closed source.
@jyriso
@heyandras
@coolifyio
I would not recommend a server where stuff is already running because Coolify will need to restart and modify docker so to be sure use a fresh server.
@brendanocwp
That would be super cool. I think it could be very nice and not to hard to do with docker compose, a database, a backend, and for the frontend one could even use a page builder like
@getwebstudio
.
@maietta
@coolifyio
The CDN is currently disabled, it is implemented just commented out. The reason for this is that the CDN gets so much traffic form the 80K+ instances when we pull templates from it that we have a huge bill at the end of the month (we definitely need caching) so we disabled it for
@kandros5591
@heyandras
@coolifyio
I think it helps if you understand the basics of Docker, Compose and Proxies but you could also get started with very little knowledge if you want to host for example WordPress or another one click template is really easy to get started without a lot of prior knowledge and learn
@mriazosama
@coolifyio
@calcom
Take a look at my PR: . You could also fix it with the range in the linked issue, but there are many reasons to fix it like I did with the PR. Boiled down to one step, you need to edit your etc/docker/daemon.json file and add a larger range.
@RayScript
@coolifyio
Yes, I will be working more on issues very soon, I have some stuff in the pipelines that I need to ship first, then we will squash the rest of the bugs. The templates are now finished and the PRs are almost all merged.
@jyriso
@heyandras
@coolifyio
Yes correct, you only need one Coolify VPS and you can then connect a ton of servers to host your resources on with docker in the background.
@ksaitor
@coolifyio
@Nextclouders
I see you have added a comment to the Github discussion, please add any extensions you would like to this discussion so we can track and integrate them.
@XCSme
@heyandras
@coolifyio
Ik this one it is kind of a pain, we already tried like 3 times to fix it but nope. We will be adding mirrors to dockerhub or similar soon, which should fix this as well.
@checkblanco
@coolifyio
Databases should not be accessed via a public URL or domain accessible in the internet as this is not very secure and also most databases do not have an accessible frontend, you could try database management software like PhpMyAdmin to connect to your database.
@AlexKokobane
@heyandras
@coolifyio
Yes, some of them are very complex. They will always be offered one way or another as they are open source. If you want to host Plausible you can do it manually using the compose deploy type. We had to remove Plausible due to trademark issues. If you want to host Plausible
@rajatsx
@heyandras
@coolifyio
@CourseLit
Please add a service request to GitHub so it does not get lost. If this service can be hosted with Docker Compose, you can already host it manually.
@Shpigford
@maybe
Expense tracking for Liftime deals with overview graphs and a calendar. A subscription teacker where we can create montly, weekly, hourly... Subscriptions. let us see all of them in one overview and a calendar view forcast and a dahsboard ui with graphs expenses every year...
@RayScript
@coolifyio
@calcom
Yes a native ARM64 Image would be great. For now you can already run
@calcom
on ARM because it just emulates AMD64, so everything works not native but it works.
@srikat
I just created my account today: and I created it on it is invite only though (by existing users). It is great for open source devs which ofc I am havily focused on.
@RayScript
@coolifyio
Yes ๐. At the moment we are prioritizing bug fixes as we want to release v4 stable very soon. This week I merged all outstanding templates as some of them were setting for 3 months and also to clean up the repo. For now I can add small new features, but bigger features will have
@maietta
@coolifyio
We do something really similar at the moment. We pull a json file that has all the details and yaml content of the service base64 endcoded from the GitHub repo.
@Ryanb58
Yes, you can remove the Postgres part from the services compose UI and add your details to the environment variables UI or deploy a separate Postgres instance on Coolify and add it to a predefined network.
@mitcho000
@coolifyio
Thank you. Coolify uses Docker in the background for pretty much everything, so your Docker skills will come in handy with Coolify.
@XCSme
@heyandras
@coolifyio
Yes, but not if you have S3 enabled. As a specific command is needed for this, Andras tried to put it in the coolify image, but this is only going to be on the main server, so the helper image is needed.