Milestone M36 - Static IP, Cloudwatch migration and more

Static IP Support for Custom Domains on NeetoDeploy

NeetoDeploy now supports static IP configuration for custom domains. Previously, users were required to point their domain to NeetoDeploy using a CNAME record. However, some users, particularly those setting up apex domains, needed an A record instead. We’ve now provisioned a static IP — 34.233.85.113 — allowing users to point their apex domains directly to this IP for seamless custom domain setup.

Complete Revamp of Logging System

We’ve migrated our logging infrastructure from Loki + S3 to a more robust Fluent Bit + AWS Cloudwatch setup. This overhaul eliminates the bugs, inconsistencies, and performance issues that previously plagued our logging system. Both live streaming and historical logs are now handled by this new setup.

External Access to PostgreSQL Addons

Many customers need to connect their PostgreSQL addons to external tools for analytics and integrations. Until now, this wasn’t feasible due to networking limitations inside our cluster. We’ve implemented a scalable solution by exposing PostgreSQL addons (TCP connections) through Traefik, utilizing our existing load balancer. This enables secure and scalable external access without requiring separate LoadBalancer provisioning per addon.

Scalable Live Log Streaming

Live streaming logs from applications has long been a technical challenge. After multiple POCs, we’ve implemented a polling-based solution that is both scalable and performant. We developed implementations in Ruby and JavaScript, used respectively in our CLI and web-based log viewer.

You can check out the implementation here: GitHub - Cloudwatch Live Logs Streaming

NeetoCI Playwright Testing Enhancements

NeetoCI’s Playwright test execution has been upgraded to use the official Playwright Docker image instead of our default runtime. This change has significantly improved the stability and performance of test runs.