πŸ”οΈ Peak (@peaklabs_dev) header
πŸ”οΈ Peak (@peaklabs_dev) profile picture

πŸ‘¨β€πŸ’» Full-Time Entrepreneur & πŸ‘¨β€πŸ³ Core Developer at coolLabs on @coolifyio. 🚧 Building OSS at https://nitter.cf/t.co/91ji7n8yrq

πŸ”οΈ Peak One
Joined January 2024
Photo by πŸ”οΈ Peak (@peaklabs_dev)Photo by πŸ”οΈ Peak (@peaklabs_dev)Photo by πŸ”οΈ Peak (@peaklabs_dev)Photo by πŸ”οΈ Peak (@peaklabs_dev)Photo by πŸ”οΈ Peak (@peaklabs_dev)Photo by πŸ”οΈ Peak (@peaklabs_dev)Photo by πŸ”οΈ Peak (@peaklabs_dev)Photo by πŸ”οΈ Peak (@peaklabs_dev)Photo by πŸ”οΈ Peak (@peaklabs_dev)Photo by πŸ”οΈ Peak (@peaklabs_dev)
πŸ”οΈ Peak retweeted
All of my hardened images now come with clean, consistent, streamlined labels. Below you can see the labels for the recently released cloudflared fips image If you look closely at the keys, you might spot some more details of the many things coming up πŸ‘€
2
2
11
2,432
πŸ”οΈ Peak retweeted
Keep an eye on this guy. He’s got a huge batch of hardened Docker images lined up for release πŸ‘€
All of my hardened images now come with clean, consistent, streamlined labels. Below you can see the labels for the recently released cloudflared fips image If you look closely at the keys, you might spot some more details of the many things coming up πŸ‘€
1
4
193
πŸ”οΈ Peak retweeted
My SQLite and other Docker images had the correct SBOM attestation but scanners still got it wrong. Turns out syft, Grype and Trivy don't read the attestation at all by default. They build their own packages list by looking inside the image, and there wasn't much for them to find. v0.3.0 of SQLite fixes that. Left is v0.2, right is the now correct v0.3.
2
2
14
729
πŸ”οΈ Peak retweeted
The cleanup has been running for about 10 days. Untagged versions on ghcr are now under 18,000, down from almost 32,000. Over 18,000 manifests deleted so far.
After days of testing, monitoring and more checks than I can count, the cleanup workflow for the Coolify image registries is now running. It will delete all unused manifests in small batches. In total more than 42,000 of about 44,000 manifests can be deleted, and roughly 2.9 TB of data will be freed up (1.6 TB on ghcr and around 1.3 TB on Docker Hub). Ofc only unused images and manifests are deleted. Every released version is kept. About 20 more days to go. Wish me luck 🀞
1
1
10
490
πŸ”οΈ Peak retweeted
It's so cool how much just changing the compression algorithm does. Since v4.6 the Coolify docker image uses zstd instead of gzip for layer compression. A pull on amd64 downloads 184 MB instead of 216 MB, 15% less. In v4.7 I also removed the unused MinIO client (mc), and a pull is now down to 157 MB, 27% less than before v4.6. Same with my SQLite image. v0.2 added features and still went from 1.52 to 1.40 MB, 8% less.
2
2
25
1,042
πŸ”οΈ Peak retweeted
That is why @peaklabs_dev is cooking something
Replying to @heyandras
For anyone at enterprise level, docker hardened images are worth looking at. Otherwise just actually make sure you secure your containers, do the basics like make sure it's not running at root etc. Use something like dgoss to test running, file permissions etc. .
1
1
11
1,043
πŸ”οΈ Peak retweeted
Can't wait for Monday? You can run Coolify v4.7 today. Settings β†’ Updates β†’ Channel β†’ Nightly You get container image vulnerability scanning, forgejo and codeberg support, sftp, ftps and webdav backup storages SSH host key pinning, one-click key rotation and much more.
4
3
1
36
3,428
πŸ”οΈ Peak retweeted
Cybersecurity in 2026
1
3
9
773
πŸ”οΈ Peak retweeted
After days of testing, monitoring and more checks than I can count, the cleanup workflow for the Coolify image registries is now running. It will delete all unused manifests in small batches. In total more than 42,000 of about 44,000 manifests can be deleted, and roughly 2.9 TB of data will be freed up (1.6 TB on ghcr and around 1.3 TB on Docker Hub). Ofc only unused images and manifests are deleted. Every released version is kept. About 20 more days to go. Wish me luck 🀞
2
1
16
1,058
πŸ”οΈ Peak retweeted
Apart from preview, nightly and stable releases, the new release process also builds every pull request as its own image. Want to try a change before it's merged? Just pull the PR image by a PR image tag. Every PR also gets a comment comparing the size of every platform image with the latest release. No more guessing whether a change makes the image bigger or smaller. Below you can see how much smaller v0.2 made my SQLite image.
1
7
472
πŸ”οΈ Peak retweeted
So we are finally opening our new app that we use internally for a few weeks. It is a Linear / Notion / Slack / Discord / Mailing all in one app that you can self-host on a few MB of RAM and own all the data. orbit.so There is also a cloud/hosted version with 7 days of free trial so you can test things out. After that it is just $10/month/workspace. No per seat or similar bs. $10 for your whole team. I will go broke for sure, but you won't :D (I have to at least get back the domain price somehow to get on 0) Same philosophy as any coolLabs apps, no restrictions, no pay-to-feature. Lets Orbit together with your team haha!
172
84
26
1,749
88,172
πŸ”οΈ Peak retweeted
Integrated the new release process fully into Coolify. The stack of 8 PRs with 48 commits, 3,058 additions and 6,636 deletions is now merged. Releasing to all of you with v4.6.0.
1
28
945
πŸ”οΈ Peak retweeted
The finalized release process had its first production run on Friday, shipping v0.2 of my hardened SQLite Docker image. I've been working on, experimenting and thinking about "the release process" on and off for over a year, and I finally found a solution for every issue. The full flow is built, for now with bash scripts (but not for long πŸ‘€). The new flow can do all of the following things and more: β—† Stable releases, maintenance releases for older majors, preview releases, nightly releases and pull request builds β—† Built-in backports, so a fix for something like PHP2Shell can easily reach every release line β—† Automatic stability stage selection and version bump suggestions, based on the branch and the commit messages β—† Extremely secure, clean and modern CI workflows that work across all repositories β—† Build all images once and the image that passed the tests is exactly the image that ships You can see the v0.2 run below, and Coolify will follows with its next release.
2
3
18
1,547
πŸ”οΈ Peak retweeted
Just released v0.2 of my hardened SQLite Docker image. With 63 new commits - yes, way too many for an SQLite Docker image. But it isn't really just about SQLite. Those commits paved the way for a new release process for Coolify and all my current and upcoming repos, and also added a lot of Docker image improvements like reproducible builds, modern OCI-compliant manifests and labels, zstd compression and immutable tags. All of it is coming to Coolify, and it creates the base for one of the several projects I have coming up πŸ‘€
4
3
19
802
πŸ”οΈ Peak retweeted
The biggest reason @coolifyio keeps winning is the team that @heyandras has assembled + the autonomy he has given us! The team is free to be as creative, as flexible, as pushy, or as relaxed as they want to be while having full control over their work! The only condition is doing right by the users, and I think we are!
3
28
1,599
πŸ”οΈ Peak retweeted
First donation is up, just gave $2,000 to @heyandras to support open source alternatives to Codex App and Claude Desktop 🫑 Also pumped that this can help with Coolify, the coolest open source hosting option for people exiting platforms like Vercel
Cutting this off now. Too lazy to filter replies so I'll assume all 737 are cancellations. That's $7,370 I have to donate to open source. What projects should I consider? πŸ‘€
51
15
7
942
213,948
πŸ”οΈ Peak retweeted
2026 Development Log 73 & 74 πŸš€ πŸ‘¨β€πŸ³ Core Coolify Development βœ… Fixed a Postgres cannot be restored error with my new standardized backup implementation by excluding the superuser, which has some other benefits too βœ… Started MySQL and MariaDB backup and restore commands modernization and optimization βœ… For over 3 days now, I have been running compression benchmarks to collect data to support my compression algorithm decisions βœ… Found one issue with how I wanted to do compression, as it uses all cores 100% by default, which is not optimal βœ… Reran some tests with a more accurate size calculation βœ… Fixed 1 dev related issue directly on next βœ… Updated upgrade maintenance email wording and numbered the steps πŸ› οΈ Miscellaneous βœ… Read up on many social posts and made sure I am up to date 🩹 Health ❌ Skipped my walk
1
9
877
πŸ”οΈ Peak retweeted
2026 Development Log 71 & 72 πŸš€ Today I opened 2 PRs for v5 that need to go into v4. One is the maintenance email and holy, it looks so good (fyi the date is not real). πŸ‘¨β€πŸ³ Core Coolify Development βœ… Opened 1 PR that adds inactivity management (users and teams) which will be needed during the v4 to v5 upgrade βœ… Opened 1 PR with super clean email templates and a command to send the v4 to v5 upgrade maintenance notification βœ… Started benchmarking and testing compression and the standardized backup on a real server ❌ Tried to create realistic compression comparisons but failed because my test file was generated poorly (volume too small, all random, then 50% random...) βœ… Merged 2 PRs that fix 2 bugs into next βœ… Provided a lot of support on Discord πŸ”οΈ PeakOSS βœ… Did more research about post-quantum cryptography βœ… Started researching and learning some initial motion graphics for my upcoming product launches πŸ› οΈ Miscellaneous βœ… Read and watched a few videos to get up to speed on the latest news, new Laravel versions, and more 🩹 Health ❌ Skipped my walk
1
1
8
505
πŸ”οΈ Peak retweeted
2026 Development Log 69 & 70 πŸš€ πŸ‘¨β€πŸ³ Core Cooliy Development βœ… Found clean solutions for multiple issues I discovered when testing the new standardized backups and planned solutions for them (adding them tomorrow) βœ… Wanted to fully implement the second backup PR with backup signing but found some blocking issues with signing βœ… Fully thought through and researched v5 databases with encryption, database users, database and app connections, new database backup UI and more (need to write it down soon πŸ˜…) πŸ”οΈ PeakOSS βœ… Did a lot of research about existing file signing tools and checked for ways to improve them βœ… Did a lot of research about cryptography in Rust and Zig βœ… Did a lot of additional research into post-quantum cryptography especially in Rust βœ… Wrote down a complete plan with everything that is still needed and also estimates of how many days that will take to finish v3 of my VS Code extension βœ… Continued planning an announcement for something big happening in a couple of weeks 🩹 Health ❌ Skipped my walk
1
4
382
πŸ”οΈ Peak retweeted
Hello?
25
4
372
18,445